What is a Wicked Problem and its 10 Characteristics?
As Laurence J. Peter once said, "Some problems are so complex that you have to be highly intelligent and well informed just to be undecided about them." This describes a wicked problem perfectly. Just understanding a wicked problem can be an immense challenge.
One former Prime Minister described it this way, "If a problem has no solution, it may not be a problem, but a fact - not to be solved, but to be coped with over time." This perfectly describes the novel characteristics of a wicked problem.
A Wicked Problem is usually large and complex and is not easily solvable. But it goes far beyond that. A wicked problem does not include small issues that are easily solved, unless they relate to a larger problem set. This means that solving the small issues may have unintended and possible negative effects or unknown effects on the larger, overall problem.
As such, we're talking about the big issues when we talk about wicked problems, where our attempts to solve them can create even more problems and issues, as we try to solve them.
The secondary problems created from our attempt to solve a wicked problem is known as unintended consequences or second-order and third-order effects. You must watch out for the emergence or possibility or various unintended consequences, as you try to solve a wicked problem.
An example of this could be, for instance, taking medicine for one issue and then having side-effects which cause other issues. Then, when you try to take medicine for these secondary issues, they cause even more issues.
Next thing you know, you're now taking 10 medicines and they are all working together in a very negative way, and all stem from your original attempt to solve the problem with only one medicine. Now you have a wicked problem on your hands.
The 10 Characteristics of a Wicked Problem
Wicked problems have been historically said to be comprised of 10 key characteristics. These 10 characteristics are what make solving wicked problems so difficult.
It is very important to get to know these characteristics and understand them so we can determine what may be a waste of time versus what may not when we attempt to solve these huge, wicked problems.
Regarding the 10 Characteristics of Wicked Problems, what follows is my interpretation and explanation, in my own words, from what I understand these wicked problems to be, based on researching the various sources and my experiences in the cyber domain and the real world, and with credits to: httpd://en.wikipedia.org/wiki/Wicked_problem, as well as the original authors of Wicked Problems, Horst Rittel and Melvin Webber, two professors from UC Berkeley, in their 1973 paper entitled "Dilemmas in a General Theory of Planning."
Note that I follow the original 10 from Rittel and Webber for the most part, again as I have come to understand them, and based on my own experiences. However, at times, these have seemed to blend a bit together, and therefore some overlap may have occurred in the 10 I list below, but with explanation how they tie together to a degree, which seems only natural.
Also, remember these things regarding wicked problems are not definitive in and of themselves; they are only descriptive elements open to some interpretation and re-explanation.
Consider these as general guidelines and characteristics, rather than carved-in-stone, so I believe some variance is acceptable. The most important thing is that in the end, you understand the general nature of wicked problems to help you begin to tackle them more effectively, despite their challenges!
1. A wicked problem is very difficult to frame, define and describe. Nonetheless, as in Einstein's quote above, we must take an extraordinarily vast amount of time to understand them and define them as well as ask the right questions first and foremost - if we are to begin to tackle them.
It's very hard to capture the full scope and extent of a wicked problem because they are complex and may change or transform when you try to solve them.
Wicked problems are therefore always changing and transforming, and even morphing. This means these problems require constant framing and re-framing to try to understand and keep up with them and their new issues
This re-framing also happens because of the second and third-order effects that create new problems. The reason for this is because many solutions which are proposed or attempted might only treat symptoms rather than find and fix root-cause issues causes.
So step one to counter this negative tendency if a wicked problem to create more problems is to stop trying to treat only the symptoms and think only short-term. Instead, by going after root causes and thinking more long-term, we can more likely avoid unintended consequences and additional problems from developing.
We do have to be careful in how we also approach the problem solving, because unintended consequences are a partner of Murphy's Law, and will always try to surface.
This is easier than it sounds because wicked problems may be a tangled web of several big issues with several root causes. These wicked problems might be a conglomeration of multiple problems interwoven with each other in a complex way, versus one-off issues.
Wicked problems can become quite a tangled web, where one solution for a root cause could solve the problem that only causes another problem or set of problems.
This weaving of multiple root causes and cause-effects for other problems being spawned, could also have the potential of affecting other root issues while solving only one issue, thereby making things worse than better. For instance, using a military solution to invade a country might solve one problem, but could also create many more, making things no better than before, overall.
2. Another characteristic of a wicked problem is that you can't truly begin to understand it, without trying to first solve it. This is because once you’re in it knee-deep and perhaps neck-deep; you truly can have an appreciation and understanding that is not obtained by mere theory and observation or second-hand information.
This means one is further enlightened to the problem or issues involved, when trying to solve it. For instance, when you have a car issue, you might not understand it unless a mechanic shows you visually where the issue is and what a faulty part looks like, and why it must be replaced.
More depths of our senses are involved, not just hearing or reading about it. This is also another lesson in how wicked problems need to be approached and solved. There should be a full range of senses and depth involved, rather than just a theoretical approach. This requires an experience-based, hands-on approach.
3. Wicked problems are not solvable from a "finally solved, once-and-for-all" perspective. They tend to persist (the no-stopping rule of a wicked problem) and they tend to also change and transform, as you try to solve them. The result if this is a wicked problem will tend to get worse in some respects, while seemingly better in others. In the end, it must be seen from a give-and-take process of trade-offs.
This also means there is no such thing as a "solved-and-done" approach to a wicked problem. There are only solutions for the time, and these may need to be re-worked and/or possibly scrapped and re-done repeatedly.
Also, wicked problems are a moving target, and they are persistent, adaptive, and dynamic - they change often and can transform and transfigure and morph into another problem just when you thought you fixed it. Ever have a problem like that? I have!
In simple things, I have been in situations where I fixed one thing on my computer, and then caused another issue. There is a constant series of trade-offs and dynamics at play with such things, and solutions are harder than they seem, even in simple things. So imagine what solutions must try to be for the hard, complex and wicked!
As such, wicked problems epitomize Murphy's Law in a worst-case scenario kind of way. Humans make this so, by the way. This is why we should focus on human side solutions, rather than just technical ones. More on that later.
This also means wicked problems must involve a continuous control method to keep it in check, rather than a once-and-for-all method to solve.
The Department of defense recognized this in the 1070's with what they called a "Net Assessment" or a strategy where things are scoped 20-30 years into the future to determine what the issues might become, as a means to try to plan and prevent "today" in a preventative fashion for what’s possible in the landscape "tomorrow".
Think of this as taking big data and predictive analytics into the long-range analysis of the future rather than just moment-by-moment.
Our solution model for a wicked problem must be cyclical, repeatable, iterative, self-correcting, adapting, improving and re-scoping one that can focus on and align with the short, medium and long-term.
4. There is no great "true-or-false" solution for a wicked problem. This means that even after testing, we most likely will not discover some definitive, highly effective way to test or solve it. Instead, we have to solve it using a "good enough" approach in varying degrees, rather than with an all-or-nothing approach.
This also means there is no immediate or ultimate test to solving a wicked problem, you just have to try things and think in terms of degrees of risk, and stick with what works best rather than what works entirely and completely. A lot of expectation management is required, for you and your bosses, so the nature of the problem and solutions are known and understood as iterative rather than permanent.
5. Those who try to solve wicked problems are fully accountable and do not enjoy the privilege of making mistakes. A wicked problem must use a hands-on approach rather than an over-focus on theory, but this causes a dilemma.
Those who solve wicked problems may create un-doable actions, from where there is no return, and they are therefore fully accountable without the benefit of any consequence. Their decisions will create impacts and effects, some good, some bad. This also means any certifications and training should focus on hands-on approach rather than just concepts without this hands-on approach.
This is where things such as design thinking can help us rapidly develop prototypes for possible solutions and options, versus long streams of solutions that cannot be tested early and often. Probably better to say options rather than solutions, as well, since these wicked problems are not completely solvable.
6. Trying to solve a wicked problem may be a one-shot deal that requires a large gamble and the solution is also probably very risky because it may not work. Consider all of the attempted solutions in cybersecurity, for example, with Antivirus.
While this "solution" helps to block known viruses, it also itself becomes a vulnerability, as a system that can be subverted especially in light of antivirus’s root-level access. That itself becomes a vulnerability while seeming to be a solution.
Or consider how a web browser plug-in or extension might block against unwanted advertisements, but itself may be susceptible to other forms of hacking that make the browser vulnerable in other ways, perhaps even more so that the risk of visiting sites with the ads.
Wicked problems are also hard to enumerate and nail down definitively with solutions in a one-for-one issue-and-solution approach. This means that you cannot always map things in a one-for-one way, in a clear engineering or scientific way.
This is because the wicked problems are not a 0 or 1, they are not true or false, they are not linear. Instead, they are many shades of gray, and solutions or attempts to solve them are either better or worse, in varying degrees, rather than strictly right or wrong, or good or bad.
The realm of wicked problems requires "art" just as much as, if not more than "science", for trying to solve these wicked problems. This is why tools and concepts such as design thinking are used, as ways to insert the "art" into otherwise inadequate science-only approaches to attempt to solve problems.
7. There is no definite or immediate solution to a wicked problem. Every wicked problem is in a unique class or type of its own problem, and therefore requires new innovation and creativity without necessarily being able to port over specific solutions that work from one area to another.
However, this doesn't mean we should "throw the baby out with the bathwater" so-to-speak. That is probably what happens though, and some useful elements we could have used go with it.
This is unfortunate, because what we could do is use precedents and other lessons and concepts and principles of something close or similar, to at least give us something somewhat useful, versus nothing at all.
The nature of wicked problems does make this difficult, especially if the problem or issue is very unique, which leads to my next point.
8. Every wicked problem is unique, not able to be fully broken down, and there is no definite formula. This means every wicked problem has its own distinctive nature and problem set, in its own right, and again is completely new, with little precedent to help us. It also means we cannot ever fully grasp or comprehend every aspect or enumerate every detail of the problem.
This makes the solution process continuously iterative and requires flexibility in our thought processes and an open mind for creative solution attempts as well as an increase in the tolerance for trial-and-error and failures. It’s hard to get buy-in for this, from management, further exacerbating the problem.
Nonetheless, we must try to find something we can use, and some principles which we can test. Here is an example where the 80-20 Rule and 80-20 Thinking cam come into play.
You can read more about that at one of my other articles "What You Need to Know about General Rules and the 80-20 Rule" where I talk about the usefulness of these tools for problem-solving.
Using the 80-20 rule, we can, therefore (hopefully) assume that we have enumerated either 80% of the problem, or better yet, at least 20% of the most important aspects and areas for a problem to focus on.
9. Every wicked problem is a symptom of another problem. This means that there will likely always be second and third-order effects and unintended consequences, by inserting solutions somewhere, due to this interconnectedness.
This happens because one wicked problem may also be interconnected or related to other wicked problem, as these can come in loosely coupled clusters, it seems. They might make each other worse, like a tangled ball yarn, but then combine as multiple balls of yarn that one can't possibly begin to untangle.
So there may need to be a re-look at what the objectives are to determine what is and is not worthwhile, and what the trade-offs are from a primary and also from secondary and third-order effects.
Effects-mapping needs to be a process employed to do this, where one seeks to think of and map as many primary, secondary, and third-order effects as possible via a mind-map, and then clusters them in ways to look at possible solutions versus their trade-off. However, the last point about wicked problems also makes this difficult.
10. Theory or explanations for causes of wicked problems vary, making solutions difficult from a people perspective. Different perspectives might also explain and see wicked problems differently, further making their solvability difficult, due to things such as viewpoint disagreement or dispute, based on various perspectives, biases, and agendas.
This means that teams who try to get together and solve wicked problems are inherently biased against the ability to do so.
That doesn't mean they should give up or not try. Instead, it means they should recognize their strengths and weaknesses and the knowns and unknowns, and set up their processes to account for all of these things.
Also, rather than try, we should follow the advice of Yoda, to Do or Do Not, There is No Try! #Solutions #ProblemSolving