S.P.A.D.E

Organizations rarely lack opinions when a consequential choice arrives. They lack a shared account of what is known, what must be assumed, and what would make one option preferable. Setting, People, Alternatives, Decide, Explain [S.P.A.D.E.] provides a sequence for framing and communicating decisions. Teams can use it to clarify context and ownership before debating options, then leave a decision record others can execute. This article turns Setting, People, Alternatives, Decide, Explain [S.P.A.D.E.] into a working management discipline: define the choice, inspect the model, and connect analysis to an accountable action.

How the model works

Setting, People, Alternatives, Decide, Explain [S.P.A.D.E.] is a decision workflow that assigns roles and creates a trace from context to communication. The sequence is useful because teams often debate alternatives before agreeing on the decision to be made or the people whose input is required. Its distinctive contribution is role clarity: a decider owns the call, while advisers provide evidence and affected parties inform implementation. The acronym is a process aid, not evidence that the analysis is sound. It still needs a clear objective, credible alternatives, and a method for handling uncertainty.

Before a cross-functional decision, write the setting in one paragraph, name the accountable decider, list advisers and implementers, and generate at least one credible alternative to the sponsor's preference. Define what evidence closes the decision and how the rationale will be explained. The public-sector DWP case on unpaid carers shows departments mapping objectives and tensions together before designing support; that is a useful illustration of why the people and context steps matter. Keep the process proportionate and publish the rationale to those who must act on it. 1

Public-sector case or practice

A published Department for Work and Pensions case on support for unpaid carers describes cross-department teams mapping objectives before considering the service journey. It shows how participation can surface competing mandates before an implementation plan hardens. This case documents a public-service practice, not evidence that the institution used the named theory. Its transferable lesson is to surface the relevant people, incentives, and evidence before implementation. A leadership team should preserve that context when adapting the approach to its own decision.

to a workshop to map respective departmental objectives 2

Define the question this model answers

A useful starting point is to specify the decision rather than announce a broad ambition. A team choosing whether to expand a service, for example, needs to know the choice date, the available options, the consequences that matter, and who has authority to commit. Without that frame, analysis tends to answer a nearby question that is easier to measure. Setting, People, Alternatives, Decide, Explain [S.P.A.D.E.] is valuable when it forces the group to expose this boundary and agree on what the method can and cannot settle.

A city team uses S.P.A.D.E. to decide how to improve access to a service. It defines the setting, names the accountable decider and advisers, generates alternatives before evaluating them, records the decision, and explains the rationale to implementers. The sequence is useful only if roles and decision rights are explicit.

For Setting, People, Alternatives, Decide, Explain [S.P.A.D.E.], the key operational measure is not whether participants completed a form. It is whether the framework changed a choice, improved the information gathered, or clarified the conditions for action. If it did none of these, simplify it. If it did, preserve the reasoning in a format that downstream teams can use without reconstructing the debate from memory. The Local Government Association asks public decision-makers to explain reasonable alternatives and why the selected option serves residents, a useful governance discipline beyond the public sector 3.

Identify the assumptions that matter

The first management test is whether the inputs represent evidence or convention. Organizations inherit targets, forecasts, and labels that can look factual after repeated use. A decision team should identify how each input was produced, who owns it, and how stale it may be. When uncertainty matters, show a plausible range and explain which part of the recommendation changes across that range. That practice makes Setting, People, Alternatives, Decide, Explain [S.P.A.D.E.] a way to discipline attention rather than a device for laundering assumptions into a confident answer.

A practical safeguard is to run a counterfactual review before the meeting closes. Ask what evidence would make the preferred option look wrong, what the strongest rejected alternative would require, and which stakeholder would detect early signs of failure. Those questions do not create certainty; they reveal where the recommendation depends on a fragile premise. A decision owner can then set a modest pilot, a contingency, or a monitoring threshold in proportion to the exposure.

For Setting, People, Alternatives, Decide, Explain [S.P.A.D.E.], the key operational measure is not whether participants completed a form. It is whether the framework changed a choice, improved the information gathered, or clarified the conditions for action. If it did none of these, simplify it. If it did, preserve the reasoning in a format that downstream teams can use without reconstructing the debate from memory.

Compare consequences in the model

A second test concerns incentives. People who supply estimates may benefit from a particular outcome, while the people who bear implementation costs may enter too late. The decision owner should ask whose information is missing and whether participants face asymmetric rewards for optimism, caution, or delay. This is not a reason to distrust every estimate. It is a reason to preserve provenance and compare claims against independent signals before they determine a large commitment.

Use disagreement as evidence

The method also changes the conversation by giving disagreement a shape. Instead of asking whether someone supports a proposal, ask which premise, consequence, or priority they dispute. That distinction often reveals that colleagues share a goal but disagree about the likelihood of a constraint or the acceptable cost of a downside. A structured disagreement can be resolved with targeted analysis; a vague disagreement usually produces another presentation and another meeting.

Decide whether more evidence is worth its cost

A useful application has an explicit stopping point. Analysis has a cost, and additional information is valuable only if it can change the choice enough to justify its price or delay. Teams should identify the next piece of evidence, its expected timing, and the decision it could alter. If no plausible result would change the action, the request for more data is not decision support. This is where Setting, People, Alternatives, Decide, Explain [S.P.A.D.E.] can help leaders protect attention and maintain a credible pace. National Aeronautics and Space Administration [NASA]’s systems-engineering guidance recommends reducing uncertainty when it could alter the ranking of alternatives 4.

Connect the recommendation to delivery

Implementation belongs inside the reasoning. A recommendation that assumes a capability the organization does not have is not an attractive option with a minor execution issue; it is a different option with different costs and odds of success. Put owners, dependencies, and observable milestones beside the proposed action. Then distinguish a failure of the underlying idea from a failure to deliver the conditions the idea required.

Review the decision and update the method

The decision record should be short enough to use and specific enough to audit. Capture the question, alternatives considered, evidence relied upon, unresolved assumptions, rationale, owner, and review trigger. Avoid recording only the selected option, since that erases the comparison that made it reasonable at the time. A future team can then learn whether a forecast missed, an objective changed, or execution departed from the plan. The Illinois Institute of Technology’s decision-quality framework offers a complementary pre-commitment review 5.

• 1Decision theory
• 2Public design evidence review: case study bank
• 3Good practice guidance on principles of effective decision-making
• 46.8 decision analysis
• 5Decision quality framework