Why it matters

Some problems don’t have an answer waiting to be found — they have a fight about what the problem even is. Homelessness, climate change, healthcare reform: each looks like a thing to be solved, but the moment you write down what “solved” means, you’ve taken a side. Whose suffering counts, on what timescale, at whose expense — those are not details to settle on the way to the solution; they are the dispute. Treat such a problem like a hard puzzle with a hidden answer and you’ll burn years optimizing the wrong thing, because the people who framed it differently were never going to accept your answer in the first place. This mode is for recognizing when you’re in that situation and changing how you work — from solving to managing.

For example: a city wants to “fix homelessness.” Downtown businesses define the problem as visible disorder, so success means fewer encampments. Service providers define it as a gap in care, so success means fewer deaths. Housing advocates define it as scarcity, so success means units built. Each framing implies a different “solution,” each solution helps one group and harms another, and there is no neutral metric that ranks them — because the metric you pick is itself a vote for one framing. The mistake is to pick one quietly and call it “the plan.” The work is to hold all the framings up at once, show where they agree (act there), show where they irreconcilably conflict (choose openly, and own the choice as a political one), and never pretend the conflict was a technical question you happened to resolve.

  • What it reveals. That the problem has no single correct formulation — and that the choice of formulation is the actual political dispute, hidden inside what looks like a search for the right answer.
  • How it changes the read. You stop asking “what is the solution?” and start asking “whose framing is this solution serving, what does it do to everyone else, and which conflicts here can’t be engineered away?”
  • When to foreground it. When stakeholders disagree about what the problem is (not just which fix to pick), when every intervention you’ve tried made things worse somewhere else, and when there’s no agreed test for “done.”
  • What you’d miss without it. That your tidy plan quietly encodes one group’s values as if they were the obvious facts of the case — and that the second-order harms it creates are not bugs but the predictable cost of the framing you didn’t notice you’d chosen.
  • Where it misleads. Calling a problem “wicked” can become an excuse for paralysis — a way to say it’s all too complex and do nothing — and it can be slapped on a merely-hard problem that actually does have a stable definition and a findable cause, where the label just adds fog.

Realtime examples

See real, dated analyses where this mode held several incompatible framings of a live public problem open at once → Wicked Problems on Main Street Independent

How to invoke it in Ora

You’re facing a problem where the people involved don’t even agree on what the problem is, where every fix you’ve tried created a new problem somewhere else, and where there’s no obvious test that would tell you it was solved.

Describe the situation concretely and ask:

“[This situation] is a wicked problem. Every solution we try makes it worse somewhere else: [name the spillovers]. Stakeholders disagree about what the problem even is. Where do we start?”

The phrases wicked problem, makes it worse somewhere else, and stakeholders disagree about what the problem even is are what route you here. Bring three things: the situation in enough concrete detail that the competing framings can be inferred; an honest list of what’s been tried and how each attempt backfired; and a sketch of who the stakeholders are and where their disagreement runs deepest — the political topology, not just the symptoms. The more of the disagreement you surface, the less the mode has to guess.

One boundary worth knowing. This is a heavy, multi-part analysis built to hold complexity, not resolve it — expect a long, structured output and ten-plus minutes, not a quick verdict. If you actually need a recommendation for a specific decision-maker, route to a decision mode instead; if the framing is settled and you only need to trace why one failure keeps recurring, that’s a root-cause job. This mode produces the groundwork that deliberation starts from; it does not do the deliberating for you.

How it works

The whole idea rests on one distinction, and it’s worth getting exactly right. In 1973 two Berkeley planning professors, Horst Rittel and Melvin Webber, published a paper with a title that sounds dry — “Dilemmas in a General Theory of Planning” — and inside it named something everyone in their field had felt but couldn’t articulate. The engineering and science that had worked so well on technical problems kept failing on social ones, and not because the social problems were merely harder. They were a different kind of thing. Rittel and Webber called the well-behaved kind tame and the other kind wicked — wicked not in the sense of evil, but in the sense of vicious, like a problem that fights back.

Start with the tame ones, because they’re what our instincts are built for. A chess endgame is tame: ferociously hard, maybe, but the board is fully specified, the rules are fixed, the goal (“checkmate”) is agreed, and you can tell unambiguously when you’ve won. A long calculation, a circuit that needs debugging, getting a rover to land on Mars — all tame. They can be brutally difficult. What makes them tame is that the problem itself sits still while you work on it: there’s a definitive statement of what you’re trying to do, a clear test for whether you’ve done it, and you can try an approach, see it fail, and try another without the failure being catastrophic or irreversible.

Wicked problems break every one of those guarantees, and Rittel and Webber spelled out how. There is no definitive formulation — you cannot even state a wicked problem without already presuming a solution, because the way you describe it (homelessness as disorder versus as a housing shortage) smuggles in the answer. There is no stopping rule: nothing tells you the problem is solved, only that you’ve run out of money, patience, or time. Solutions are not true-or-false but better-or-worse, judged along contested values where reasonable people rank the values differently. Every attempt is consequential — you can’t run a wicked problem as trial-and-error, because every “trial” is a real intervention in real lives that changes the situation and can’t be cleanly undone; there’s no reset button. There is no enumerable set of options — you can’t list all the possible moves the way you can in chess. Every wicked problem is essentially unique — the deep structure that made the last city’s homelessness crisis what it was (its zoning, its climate, its politics) doesn’t transfer. And every wicked problem is a symptom of another problem one level up: homelessness is downstream of housing markets, mental-health funding, and federal policy a city doesn’t control, so you can always reframe it as a symptom of something larger, and where you choose to cut is, again, a judgment.

Sit with the consequence of all that, because it’s the part our problem-solving instincts resist. If there’s no agreed statement of the problem and no agreed test for the answer, then the choice of how to frame the problem is not a preliminary step on the way to solving it — the framing is the whole ballgame. When the downtown business association and the harm-reduction clinic “disagree about homelessness,” they are not two parties with different solutions to a shared problem. They hold different problems, and each problem’s framing quietly nominates winners and losers before any solution is on the table. That’s why these problems feel intractable: people argue about solutions while the real disagreement, the one about framing, stays underground. Rittel and Webber’s sharpest point is that this makes wicked problems irreducibly political, and that dressing them up as technical — handing them to experts to “solve objectively” — doesn’t remove the politics, it just hides whose values won.

So the discipline flips. You stop hunting for the solution, because by definition there isn’t one to find. Instead you surface every serious framing and state it at its strongest, so no one’s problem gets strawmanned out of the room. You map who holds each framing and what each one wins or loses, so the value-conflict is on the table instead of under it. You find where the framings actually agree — and you act there first, because that’s where progress is cheap and uncontested. Where they genuinely conflict, you stop pretending a metric will adjudicate it; you choose openly and name the choice as the political act it is. And because every move is irreversible, you bias toward interventions you can adjust as you learn, and you trace the second-order effects — the way a shelter that calms downtown today seeds the neighborhood opposition that defunds it next year. The goal is never to cure a wicked problem. It is to manage it honestly, with the people who have a stake in it, without lying to yourself that the hard part was a puzzle you’d already cracked.

Framework & implementation

This section uses Ora’s own terms for the parts of an analysis, so that if you open the actual mode file they line up. Each is glossed in plain language on first use.

Pipeline execution

Wicked Problems is a molecular mode in the interest-and-power territory — the heaviest operation there, built from several other modes rather than run as one pass. It executes at Gear 4, Ora’s most thorough setting: a Depth analyst and a Breadth analyst work the situation in parallel and then critique each other (cross-adversarial evaluation) before a consolidator integrates the result.

The mode runs as a composite. It fires a competing-hypotheses fragment to surface the rival framings of the problem; a full cui-bono pass (Latin “who benefits”) to trace whose interests each framing serves; a steelman-construction fragment that builds the strongest honest case for the leading framings; a full systems-dynamics-causal pass that maps the feedback loops keeping the problem stuck; a full scenario-planning pass projecting how things unfold under different framing-and-intervention pairs; and a red-team-assessment fragment (an adversarial stress-test) that attacks the most plausible interventions to find where they break. Three synthesis stages then weave the pieces together: framing-reconciliation (where framings cohere versus where they irreducibly conflict), dynamic-projection (how the problem evolves under each framing-and-scenario pair), and intervention-stress-test (where each candidate intervention fails). The load-bearing rule throughout is the refusal to collapse to a single dominant frame early — the multi-frame structure is preserved end to end, because flattening it would erase exactly the political dispute the mode exists to expose.

Output contract

The deliverable is a fixed set of sections, so the analysis is auditable rather than a persuasive essay: Problem with wickedness characteristics (the problem stated, with each Rittel–Webber property that actually applies named and justified, and the ones that don’t explicitly set aside); Reconciled framing (each competing framing steelmanned, with the stakeholders who hold it, and the tensions between framings named rather than dissolved); Stakeholder-interest map (who wants the problem solved, shifted, or kept, and where the power sits); Dynamic projection (the reinforcing and balancing feedback loops, tagged with system-leverage points); Scenario projections (how the situation plays out under each dominant framing, and who wins or loses in each); Candidate intervention catalog (each option mapped to the framing it serves and the leverage point it targets, with red-team findings on how it breaks); Residual tensions (the conflicts that are never resolved, each traced to the specific wickedness property that makes it irreducible); and a Confidence map. The point of the contract is that “tame” answers — a single recommendation, a clean ranking — are structurally impossible to emit; the format forces the honest, multi-frame picture.

Origin and evidence

The mode is built directly on Horst Rittel and Melvin Webber’s 1973 paper, “Dilemmas in a General Theory of Planning”, which named the class of wicked problems and laid out the properties — no definitive formulation, no stopping rule, no true-or-false solutions, no reset on consequential moves, no enumerable option set, essential uniqueness, and each problem as a symptom of another — that distinguish them from tame problems (well-defined, with an agreed test for “solved”). The practical complement comes from Jeff Conklin’s Dialogue Mapping (2006), which took Rittel’s later work on argumentation and turned it into a working method: because a wicked problem can’t be defined in advance, you build shared understanding by mapping the questions, ideas, and arguments of the actual stakeholders as the conversation unfolds — collective sense-making in place of a fixed problem statement. Together they supply the mode’s two commitments: name the wickedness honestly, and hold the rival framings open rather than forcing a premature answer.

Applications and common uses

  • Contested public policy. Homelessness, opioid deaths, housing supply, rural hospital closures — problems where stakeholders disagree on the definition and every fix has spillovers.
  • Platform and information governance. Content moderation and AI-driven misinformation, where stricter and looser rules each generate their own backlash and there’s no neutral setting.
  • Organizational strategy under deep disagreement. Reorganizations or strategy fights where the leadership team doesn’t actually share a definition of the problem they’re solving.
  • Environmental and resource conflicts. Land use, water rights, climate adaptation — long-horizon problems with irreversible moves and incommensurable values across parties.
  • Cross-jurisdiction problems. Situations a single actor can’t fully control because the problem is a symptom of a larger system (federal policy, regional markets) it doesn’t govern.

Failure modes and when not to use it

  • Mislabeling a tame problem as wicked. A merely-hard problem with a stable definition and a findable cause does not become wicked just because it’s big; the label then adds fog and licenses overcomplication. The first job is to test whether the wickedness properties genuinely apply.
  • The wicked-problem excuse for paralysis. “It’s irreducibly complex” can become a reason to do nothing. The mode guards against this by finding the coherent region where framings agree and action can proceed, so complexity is no longer a blanket alibi for inaction.
  • Frame-flattening under pressure. The temptation is to collapse to the loudest or most powerful framing and present it as “the” problem; that erases the dispute the mode exists to expose. The fixed multi-frame output contract is the guard.

When not to reach for it. When you’re tracing why one specific failure keeps recurring and the problem is well-defined, that’s a backward causal trace — route to root-cause-analysis. When the framing is already settled and the real question is which option to pick from a structured set, that’s a choice — route to a decision-architecture mode. And when the difficulty is a feedback dynamic you need to diagnose in isolation rather than a contested framing, the systems-dynamics-causal mode on its own is lighter and sufficient.

  • Boundary Critique — the critical-stance counterpart in the same territory: the mode for interrogating where you’ve drawn the edge of a problem and who that boundary leaves out — the same “the framing is the politics” insight, turned on the framing itself.
  • Wicked Futures — the future-facing sibling for when the wicked problem is about what’s coming rather than what’s here: holding rival framings open across scenarios instead of across present stakeholders.
  • Constraint Mapping — the lighter move for when the difficulty is a thicket of real constraints to lay out and reconcile, not a contested definition — useful as a pre-step to see whether a problem is wicked or merely tightly bound.
  • Cui Bono — the “who benefits” lens this mode loads as a component: trace whose interests each framing of the problem quietly serves, which is half of seeing why the disagreement is really about power.