海角大神

I am a geek. (Some prefer the term 鈥渘erd,鈥� but I鈥檒l stick with geek.) I have always been a geek.

At 6, I wanted to be a mathematician. Not a princess or an astronaut 鈥� a mathematician.

As a geek, an engineer, a technologist, I love difficult problems. When you鈥檙e building a new computer architecture or developing an algorithm, the reward is making tangible advances toward a solution, marking quantifiable steps toward an unambiguous benchmark of progress.

But today, we face many problems that don鈥檛 fit that mold. They are difficult to define. The metrics of success are unclear.

They are complex in a way that, at first glance, prohibits finding a solution at all. Meet 鈥渨icked problems.鈥�

Cybersecurity is one example. Proactively anticipating and planning for emerging epidemics is another. Understanding the impact of climate change and development of mitigation and adaptation strategies is yet another.

To get a sense for the prickly and interconnected nature of these problems, consider our last example, climate change.

鈥淐limate change may exacerbate water scarcity and lead to sharp increases in food costs. The pressures caused by climate change will influence resource competition while placing additional burdens on economies, societies, and governance institutions around the world. These effects are threat multipliers,鈥� reads the 2014 Quadrennial Defense Review.

And, really, that鈥檚 not even half the problem.

"Our current infrastructure is increasingly challenged by transformations in energy supply, markets, and patterns of end use; issues of aging and capacity; impacts of climate change; and cyber and physical threats. Any vulnerability in this infrastructure may be exacerbated by the increasing interdependencies of energy systems with water, telecommunications, transportation, and emergency response systems,鈥� reads President Obama鈥檚 introduction to the 2015 Quadrennial Energy Review.

These don鈥檛 sound like nicely defined engineering problems. They are messy, interconnected, and require addressing and considering many conflicting objectives.

These are the 鈥渨icked problems.鈥�

Defined by ten properties laid out in a 1973 paper, wicked problems differ from their tame cousins in several key ways:

• They can鈥檛 be definitively pinned down and defined, making even agreeing on what constitutes the boundaries of the problem hard to discern
• The problems themselves can be considered symptoms of another problem, further hazing our ability to approach them clearly
• Solutions to wicked problems aren鈥檛 best understood as true (effective) or false (ineffective), but as good (moving society forward) or bad (doing more harm than good)

You can see why our authors, while incredibly forward-looking, were themselves somewhat discouraged by this line of wicked thinking.

鈥淭he search for scientific bases for confronting problems of social policy,鈥� begins the first sentence of the paper鈥檚 abstract, 鈥渋s bound to fail, because of the nature of these problems.鈥�

If those who named the issue thought the task at hand to be 鈥渂ound to fail,鈥� perhaps you鈥檇 be inclined to walk away, too.

But we love difficult problems. Us geeks (and nerds), we can鈥檛 walk away.

So what do we do?

We have to work together, uniting sometimes disparate groups of experts to tackle small parts of a wicked problem. Together, we carve out pieces we can make measurable progress on.

For example, computational scientists working with political scientists to understand the root causes of political instability. It is about economists working with chemical engineers to understand feasibility of carbon dioxide sequestration approaches. It鈥檚 about trade researchers working with agricultural experts to connect food riots in Egypt to a drought in China.

(At ASU, we are actually working on that last one through a project aimed at understanding the impact of climate on trade networks. Can we anticipate other such events?)

Next, we have to embrace complexity.

There鈥檚 a concept from the foundational thinking of wicked problems that argues that 鈥渢he planner has no right to be wrong.鈥�

What does that mean? Unlike when applying traditional scientific method, you can鈥檛 implement a full solution, test it out, and then try again.

For example, you can鈥檛 test out the full interdependencies in the food, energy, water nexus. Following one hypothesis all the way to its conclusion could be disastrous in a species-ending way.

The planner, or the tester, has no right to be wrong.

While this seems daunting at first blush, I actually think this aspect of wicked problems is fabulous. This means progress, if we are to make any, must occur step-by-step.

In embracing complexity, we admit that we can鈥檛 tackle the problem with one elegant move.

Scientists and engineers must engage on wicked problems with policy makers, humanitarians and experts from other disciplines to develop tools for decision making that transform science and engineering into action and policy.

We can鈥檛 solve the whole puzzle, in other words, but we can put together a few pieces at a time.

At ASU Global Security Initiative, we have embraced the wicked problem. I hope you will too.

Nadya Bliss is director of the Global Security Initiative at Arizona State University. Follow Dr. Bliss on Twitter聽@nadyabliss聽and the Global Security Initiative聽@asu_gsi.