Decision Clarity

Why it matters

When a board, a council, or any group sits down to “make a decision,” the hardest part is usually not weighing the options — it is that nobody has said, out loud and precisely, what is actually being decided, who actually gets to decide it, and whose interests genuinely hang on the outcome. Most decisions arrive muddled: the real question is buried under a vaguer one, the decision-maker’s actual authority is fuzzier than it sounds, and the parties who will live with the result are half-named at best. Decision Clarity is the discipline of fixing all of that before anyone argues about which option is better — naming the real question, the real decision-maker, and the real stakes and interests, so that whatever choice gets made is made with eyes open.

For example: a school board “decides whether to go to year-round school.” Stated that way it sounds like a yes/no on a calendar. Clarify it and the real question narrows — it is a vote on calendar structure only, not on funding, pay, or curriculum, which are separate authorities. The real decision-maker is the board, which has sole statutory power to set the calendar but cannot touch teacher contracts or conjure new state money. And the real stakes belong to parties the agenda never lists by interest: teachers who will accept redistributed days only if total pay holds, families whose summer childcare and jobs depend on the break, taxpayers and local employers who bear costs but sit unorganized and unheard. None of that is an answer. But until it is on the table, every “pro” and “con” is being argued in a fog.

What it reveals. The true shape of a decision a third party must make — the actual question being decided, who holds the authority (and its real limits), and which interests and stakeholders genuinely hang on the outcome — stripped of the vaguer framing the decision arrived wrapped in.
How it changes the read. You stop asking “which option is best?” and start asking “what exactly is being decided, by whom, for whom, and what truly hangs on it?” — and the options often look different once that frame is honest.
When to foreground it. A consequential decision facing someone else — a board, a council, a committee — where the framing is muddled, the stakeholders pull in different directions, and the job is to brief the decision-maker so they choose with eyes open, not to choose for them.
What you’d miss without it. That the question on the agenda is rarely the question actually at stake; that some affected parties are unorganized and silent yet bear the largest costs; and that “balance” can be a dishonest word laid over a conflict of interests that cannot be split down the middle.
Where it misleads. It is cartography, not a verdict — pushed past its job it starts quietly recommending, which buries exactly the value choice it was meant to expose; and if the decision is genuinely simple, mapping its stakes and interests at length manufactures gravity that isn’t there.

Realtime examples

See real, dated analyses where this mode mapped the real question, stakes, and interests behind a decision in the news → Decision Clarity on Main Street Independent

How to invoke it in Ora

You have a consequential decision facing a third party — a board, a council, a committee — and you want it made legible before anyone weighs options: the real question, the real decision-maker and the limits of their authority, and the interests and stakeholders genuinely at stake. The point is to brief whoever holds the decision, not to have the mode pick for them.

Name the decision concretely and ask:

“Decision clarity document for the board: should [body] do [thing]? Brief the decision-maker, not exploratory analysis.”

The phrases decision clarity, brief the decision-maker, and should [body] do [X] are what route you here. Bring the decision as specifically as you can — “should the city accept the $400M incentive package — a 20-year tax abatement, $80M in transit, 8,000 jobs promised at $90K” lands far better than “should the city take the deal” — and name the stakeholders if you know them, and your own stance if you are one of them rather than a neutral analyst.

Two boundaries worth knowing. If you hold the decision and want an integrated recommendation across options — probabilities, constraints, stakeholders, failure modes, all weighed into a ranked answer — that is decision-architecture, not this mode; Decision Clarity deliberately stops short of picking. And if the question is narrowly who benefits from this arrangement, the cui-bono mode traces the beneficiary flow directly. This mode lays the groundwork a real decision starts from; it does not make the call.

How it works

Picture a city council with a developer’s offer on the table: a new headquarters, thousands of jobs, in exchange for twenty years of property-tax breaks and a pile of public money for transit. Someone moves to “discuss whether to accept the deal,” and within minutes the room is arguing about jobs numbers and tax rates. That argument is premature — because the council has not yet established the three things that actually determine what a good choice even looks like. Decision Clarity is the move that establishes them first.

The first thing to nail down is the real question — what is actually being decided, with its true boundaries. “Should we accept the deal” sounds like one question; it is usually several tangled together. Is the council deciding the tax abatement, or also the transit spend, or also the zoning, or also a precedent for the next developer? Drawing the boundary precisely — this vote is on the incentive package only; zoning is a separate authority on a separate timeline — does more to clarify the decision than any amount of debate about the merits. A surprising share of bad decisions are really two different decisions argued as one, where people who agree about the actual question discover they were fighting about the parts beside it.

The second is the real decision-maker, and the real edges of their power. The council holds the vote — but does it actually control the things the deal assumes? It cannot bind a future council, cannot force the state’s hand on funding, cannot rewrite the developer’s terms unilaterally. Naming whose decision it genuinely is, and where that authority stops, kills a whole class of phantom options — the ones that quietly assume a power the decision-maker does not have. A choice that depends on authority you lack is not a choice; it is a wish.

The third, and the heart of it, is the real stakes and the real interests — who is genuinely affected, what each party actually wants underneath what they say, and what truly hangs on the outcome for them. This is where the interest-and-power lens does its work. The developer wants the subsidy; current residents want the jobs but not the displaced rents; the unorganized — the renters who will be priced out, the small businesses that will absorb the congestion — bear real costs while having no seat and no voice. The discipline here is to separate a stated position (“we support growth”) from the underlying interest (“we need the tax base to hold”), and to name the parties the official framing leaves out precisely because they are unorganized. Two interests that genuinely cannot both be satisfied get marked as exactly that — a real conflict, not a misunderstanding that more data would dissolve. Calling such a conflict “a balance to be struck” is the polite lie this mode exists to refuse.

Here is the line that matters most, and it is what separates Decision Clarity from its heavier cousins: it stops before scoring the options. It does not tell the council to take the deal or walk away. The instant an analysis ranks the choices and crowns a winner, it has smuggled in a value judgment — this interest matters more than that one — and hidden it inside what looks like a neutral recommendation. That judgment belongs to the decision-maker, who is accountable for it, not to the analyst. So the output is a map, not a verdict: here is the real question, here is who decides and how far their power reaches, here are the stakeholders and what each truly stands to gain or lose, here are the genuine tradeoffs and which parties no option can satisfy. The map makes the decision honest. Walking the map — choosing — stays the decision-maker’s to do.

That boundary is also the cleanest way to tell this mode from the ones next door. If the question is which option wins once we weigh everything — and the person asking holds the decision and wants a recommendation — that is full option-scoring: decision-architecture, or a multi-criteria comparison. If the question is the narrow forensic one, who benefits from this arrangement, that is cui-bono. Decision Clarity is the upstream move that makes any of those worth doing: get the question, the decision-maker, and the stakes right, and an honest choice becomes possible. Get them wrong, and the most rigorous option-scoring in the world just answers the wrong question precisely.

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

Decision Clarity is a mode in the interest-and-power territory — a single, decision-shaped pass that produces a briefing for whoever holds the decision, rather than a recommendation. It runs at Gear 4, Ora’s most thorough setting: a Depth analyst and a Breadth analyst work the decision in parallel and then critique each other (cross-adversarial evaluation) before a consolidator integrates the result — depth pressing on the real interests and authority limits, breadth making sure no affected party or framing is missed.

The pass works the decision in stages. It maps the problem space — recording the competing definitions different stakeholders hold of what is even being decided, without picking between them, so the real question is established before any option is judged. It classifies the value conflicts into fundamental (two interests that cannot both be fully honored, no matter how much information arrives) versus resolvable (a gap better information or negotiation could close) — the discipline that refuses to dress a genuine conflict up as a misunderstanding. It models the consequence landscape across the parties and time horizons, with explicit attention to who benefits and who bears the cost (it draws on the cui-bono mode here, the distributional “who gains” analysis). And it makes the tradeoffs transparent: for each path on the table, it states plainly what that path prioritizes, what it subordinates, and which stakeholders it cannot satisfy — then runs Red Team passes (an adversarial “argue the other side” stance) speaking for each subordinated group, so the cost of a path is voiced, not glossed.

The mode’s reasoning tools ride in its ANALYTICAL PERSPECTIVES block — the lenses it loads as it works. The interest-and-power lenses are load-bearing: stakeholder mapping (who is affected and how much weight they carry), and the position-versus-interest discipline that separates what a party says it wants from what it actually needs — the move that keeps the map honest about real stakes.

Output contract

The deliverable is a decision-maker’s briefing, shaped so the structure of the choice is legible rather than narrated. It states the decision at hand (the real question, with its true boundaries drawn), the decision-maker’s context (who holds the authority and exactly where that authority stops), a stakeholder map with positions (each party, where they stand, their concrete underlying interest, and their real concern — including the unorganized parties the official framing omits), an interest-and-power summary (who is organized and heard, who bears costs while voiceless, where the genuine conflicts sit), a scenario range (how the plausible futures differ under each path), and an explicit tradeoff statement per path (what it prioritizes, what it subordinates, whom it cannot satisfy). What the contract deliberately withholds is a ranked “best option”: the value choice — which interests to honor over which — is left, named and exposed, for the decision-maker to make.

Origin and evidence

The mode braids two traditions. From decision analysis — Ronald Howard’s field, set out with Ali Abbas in Foundations of Decision Analysis (2008) — it takes the insistence that the framing of a decision (what is being decided, by whom, under what constraints) is prior to, and more consequential than, the arithmetic of choosing; a decision badly framed cannot be rescued by careful weighing. From the interest-based tradition of Roger Fisher and William Ury’s Getting to Yes (1981) it takes the central discipline of this territory: separate people’s stated positions from their underlying interests, because the real stakes — and the real room for an honest choice — live in the interests, not the announced demands. The mode’s refusal to collapse a genuine value conflict into a solvable misunderstanding echoes the long line of thought on “wicked problems” — Horst Rittel and Melvin Webber’s Dilemmas in a General Theory of Planning (Policy Sciences, 1973; doi:10.1007/bf01405730) — where contested definitions and irreconcilable values are features of the problem, not defects in the analysis.

Applications and common uses

Board and council decisions. The native use: a governing body facing a consequential vote where the real question, the limits of its authority, and the affected interests need to be made legible before the vote.
Public-policy and civic choices. Incentive packages, facility closures, zoning and regulatory choices — decisions where unorganized parties bear real costs while having no seat at the table.
Organizational structure decisions. Reorganizations, mandate shifts, and resource reallocations where competing internal interests pull against each other and “alignment” hides a genuine conflict.
Briefing a decision-maker you are not. Any case where your job is to lay out a choice honestly for someone else to make — staff to principal, advisor to client — without putting your thumb on the scale.
Decisions where “balance” feels dishonest. When every option harms someone real, the mode names whom, rather than papering the conflict over.

Failure modes and when not to use it

Drifting into recommendation. The strongest pull is to end with “so you should…” — which buries the value choice the mode exists to expose. The discipline is to stop at the map and leave the call to the decision-maker.
Treating a fundamental conflict as resolvable. The seductive error is to imply more information or cleverer wording could satisfy everyone. The fundamental-versus-resolvable classification is the guard: a real conflict is named as real, and the decision-maker designs around it rather than wishing it away.
Missing the unorganized. A stakeholder map that lists only the parties who showed up reproduces the original blind spot. The mode deliberately names the affected-but-voiceless.

When not to reach for it. When you hold the decision and want the options actually weighed and ranked — probabilities, constraints, failure modes integrated into a recommendation — route to decision-architecture; for a straightforward weighing of options against several criteria, multi-criteria-decision fits. When the question is the narrow forensic one — who benefits from an arrangement — that is cui-bono. And when the decision is genuinely simple, with an obvious question and no real conflict of interests, running the full briefing manufactures complexity instead of revealing it.

Decision Architecture — the sibling for when you hold the decision and want the options weighed into an integrated recommendation, not just mapped — the boundary this mode hands off across.
Cui Bono — the narrower forensic move pulled in when the live question is who benefits from an arrangement and who quietly bears its cost.
Stakeholder Mapping — the companion that inventories the affected parties and weighs their power, legitimacy, and urgency — the raw material this mode’s stakeholder section is built from.
Multi-Criteria Decision — the structured option-scoring mode for ranking choices against several explicit criteria, once the real question and stakes are already settled.