What is a wicked problem? A wicked problem is a social or planning problem so complex, interconnected, and contested that it has no definitive formulation and no final solution — a term coined by Horst Rittel and Melvin Webber in 1973.
A wicked problem is ill-defined: how you frame it already shapes what counts as a solution, and different stakeholders legitimately define it differently. It has no stopping rule (there is no point at which it is 'solved'), its solutions are good-or-bad rather than true-or-false, and every intervention is a one-shot operation whose consequences you cannot fully test in advance — so trial-and-error is unsafe and every attempt matters. Horst Rittel and Melvin Webber coined the term in their 1973 paper 'Dilemmas in a General Theory of Planning' and set out ten defining properties. Classic examples include climate change, homelessness, healthcare policy, and organizational strategy. Wicked problems defeat the linear 'define, analyze, solve' approach that works on tame problems; progress instead comes from building shared understanding across stakeholders, mapping the dialogue and issues (as in dialogue mapping and IBIS), deliberating in a structured way, and keeping the reasoning visible. Argumentree supports this by structuring the competing arguments, capturing the reasoning behind each, surfacing where a group stands, and letting the map be revisited as understanding evolves.
What Is a Wicked Problem?
A wicked problem is a complex, ill-defined problem that has no clear definition, no stopping rule, and no true-or-false solution — where every attempt to solve it changes the problem itself. The term was coined by Horst Rittel and Melvin Webber in 1973 to describe the messy, contested problems of social planning and policy.
Last updated: 2026-07-04
In short
A wicked problem is a problem that is ill-defined, has no stopping rule, has only good-or-bad (never true-or-false) solutions, is essentially unique, and where every intervention has lasting consequences — so you can't safely trial-and-error your way to an answer. Coined by Rittel and Webber (1973), the term names problems like climate change, homelessness, and healthcare policy that resist the linear 'define, analyze, solve' approach which works on tame problems.
The ten characteristics of a wicked problem
- 1
No definitive formulation
There is no single, agreed statement of what the problem is. How you frame it already shapes what counts as a solution.
- 2
No stopping rule
There's no point at which the problem is 'done.' You stop because you run out of time, money, or patience — not because it's solved.
- 3
Solutions are good-or-bad, not true-or-false
There's no objective test that marks an answer correct. Stakeholders judge a solution as better or worse, from different values.
- 4
No immediate or ultimate test of a solution
You can't fully test a solution in advance; its consequences ripple out over time and can't all be foreseen.
- 5
Every solution is a one-shot operation
There's no safe trial and error. Every intervention changes the situation and leaves a mark, so every attempt counts significantly.
- 6
No enumerable set of solutions
There is no exhaustive list of possible responses to pick from; which options even get considered is itself a matter of judgment.
- 7
Essentially unique
Every wicked problem is one of a kind. Lessons from a past case never transfer cleanly, because the context always differs.
- 8
A symptom of another problem
Every wicked problem is entangled with others. Addressing it at one level can worsen the deeper problem it is a symptom of.
- 9
Explanations shape the solution
The problem can be explained in many ways, and the explanation you choose determines the kind of resolution you look for.
- 10
The planner has no right to be wrong
Unlike a scientist testing a hypothesis, whoever intervenes is accountable for the real-world consequences of getting it wrong.
Rittel and Webber laid out these ten properties in their 1973 paper. The through-line: a wicked problem can't be cleanly defined, can't be finally solved, and can't be worked on well unless the reasoning — and the disagreement — is made explicit.
Why traditional problem-solving fails on wicked problems
Wicked problems — climate change, homelessness, healthcare policy, organizational strategy — defeat the linear 'define, analyze, solve' playbook for three connected reasons:
The problem won't hold still
Linear methods begin by defining the problem, but a wicked problem resists a single definition — the framing is itself contested, and it shifts as you work on it. You never get the fixed target the method assumes.
You can't safely iterate
Tame problems let you test, fail, and try again. Wicked problems are one-shot: every intervention changes the real situation and has lasting consequences, so there's no cost-free trial and error to converge on an answer.
Disagreement is the substance, not noise
Linear optimization hunts for the one objectively correct answer. On a wicked problem, competing values and framings are the substance of the problem — different stakeholders define it differently, and that can't be optimized away.
How Argumentree helps teams work on wicked problems
You can't 'solve' a wicked problem the way you solve an equation, but you can make real progress on it. The approaches that help share a common thread: building shared understanding across stakeholders, mapping the dialogue and the underlying issues (as in dialogue mapping and IBIS), deliberating in a structured way, and keeping the reasoning visible so a group can see where it stands and why. Argumentree is built around exactly this:
Structure the competing arguments
Each proposed framing and option is worked through as a hierarchical pro/con argument tree, so the many legitimate viewpoints are laid out side by side instead of being collapsed into one 'right' answer.
Capture the reasoning
Every argument, objection, and trade-off is recorded with its rationale, so the group's thinking is preserved as a durable artifact rather than lost in scattered chat threads and meetings.
Surface where the group stands
Multi-dimensional ratings show which arguments a group finds strong and where it genuinely disagrees, making contested framings visible instead of hidden behind a premature consensus.
Revisit as understanding evolves
Because wicked problems have no stopping rule and shift over time, the argument map stays live: you can return, fold in what you've learned, and update the picture as the situation changes.
Argumentree doesn't claim to 'solve' wicked problems — nothing does. What it offers is a way for a group to reason about one together and keep that reasoning structured, visible, and durable as understanding evolves.
Explore further
What is dialogue mapping?
How a group's conversation is mapped in real time into an IBIS structure of questions, ideas, and arguments — a core technique for wicked problems.
What is collaborative decision-making?
How a group reaches a decision together, transparently, when no single person holds the whole picture.
What is decision-making?
The foundations of how individuals and groups reach a choice — and where the reasoning tends to get lost.
Argumentree for public policy
Structuring open, contested deliberation on public issues — the natural home of wicked problems.
Frequently asked questions
What is a wicked problem?
A wicked problem is a complex, ill-defined problem with no definitive formulation, no stopping rule, and no true-or-false solution — only better-or-worse ones judged from different values. Every attempt to address it changes the problem and has lasting consequences, so it can't be solved by safe trial and error the way a well-defined 'tame' problem can.
Who coined the term wicked problem?
The term was coined by design theorist Horst Rittel and urban planner Melvin Webber. They introduced it formally in their 1973 paper 'Dilemmas in a General Theory of Planning,' published in the journal Policy Sciences, where they set out ten properties that distinguish wicked problems from tame ones.
What are examples of wicked problems?
Classic examples come from social planning and policy: climate change, homelessness, poverty, healthcare and drug policy, pandemic response, and education reform. They also appear inside organizations — questions like long-term strategy, culture change, or how to reorganize a company have the same wicked character: contested definitions, no clean solution, and consequences you can't fully test in advance.
What's the difference between a wicked problem and a tame problem?
A tame problem is well-defined and has a clear stopping point and a testable solution — even if it's genuinely hard, like a complex engineering or mathematics problem. A wicked problem is ill-defined and contested: there's no agreed formulation, no test that proves a solution correct, no safe way to iterate, and no final 'solved' state. Tame problems can be solved; wicked problems can only be managed and improved.
Can wicked problems be solved?
Not in the sense of a final, provably correct solution — that's what makes them wicked. But you can make genuine progress on them. Progress comes from building shared understanding among stakeholders, deliberating in a structured way, and keeping the competing reasoning visible so a group can weigh trade-offs and revisit them as the situation evolves — rather than searching for one right answer that doesn't exist.
References & further reading
Rittel, H. W. J., & Webber, M. M. (1973). Dilemmas in a General Theory of Planning. Policy Sciences, 4(2), 155–169.
The foundational paper that named 'wicked problems' and set out the ten defining properties. Cited by name; consult the journal Policy Sciences for the authoritative text.
Conklin, J. (2006). Dialogue Mapping: Building Shared Understanding of Wicked Problems. Wiley.
Extends the concept into practice, introducing dialogue mapping and the IBIS notation as ways for a group to make progress on wicked problems. Cited by name.
Australian Public Service Commission (2007). Tackling Wicked Problems: A Public Policy Perspective.
A widely cited government report applying the wicked-problem framing to public policy. Cited by name; refer to the APSC for the current version.
"Wicked problem" — encyclopedia overview
A general-reference summary of the concept, its origin with Rittel and Webber, the ten characteristics, and common examples. Useful as an accessible starting point.
View source →Make progress on your hardest problems
Structure the competing arguments, capture the reasoning behind each, and keep a living map your team can revisit as understanding evolves — so the messiest problems stay workable together.
Start free