Decision Participants

Decisions fail when the wrong people are in the room — or the right people arrive too late.

This guidance covers how to identify who should participate in a decision, what capacity they should hold, and how to involve them without degrading the decision process into consensus theater or unchecked stakeholder sprawl.

Identifying the right SMEs

A subject-matter expert is someone whose domain knowledge materially changes the quality of the decision. That is a higher bar than "someone who has an opinion" or "someone who would be upset if excluded."

An SME belongs in a decision when:

• their domain expertise addresses a specific gap in the framing or analysis
• they have direct experience with the constraints or failure modes at stake
• the decision cannot be evaluated without their technical, regulatory, or operational knowledge

An SME does not belong in a decision solely because:

• they hold a senior title
• they were involved in a similar decision previously
• they have expressed interest in the topic

Internal users vs external contacts

Internal users are members of the organization who can authenticate into the system and participate directly. External contacts — tracked through the organization's relationship registry — are people outside the org whose expertise or authority matters to the decision.

Use external contacts when:

• the decision requires domain expertise the organization does not have in-house (legal counsel, regulatory specialists, technical consultants)
• a vendor, partner, or customer perspective is needed to evaluate feasibility or impact
• governance requirements mandate external review or sign-off

Use internal users when the participant is an active member of the organization, regardless of department or seniority. Internal participation carries accountability — the system validates that the participant is an active member of the organization.

Avoiding "too many cooks"

Every additional participant adds coordination cost and dilutes signal. Before adding someone, ask:

• What specific question does this person help answer?
• If they were absent, what would be worse about the decision?
• Can their input be captured asynchronously rather than through direct participation?

If there is no concrete answer to the first two questions, the person should not be a participant. They may need to be informed of the outcome, but that is different from participating in the process.

Obligation classes

Every participant holds an obligation class that describes why they are involved. This is distinct from their role, which describes what they do.

Constitutional

Constitutional participants must be involved for governance, compliance, or authority reasons. Their involvement is not optional — it is required by organizational policy, regulatory mandate, or the decision's authority structure.

Examples:

• A CFO must approve any capital commitment above a defined threshold
• Legal counsel must review any decision affecting contractual obligations
• A board delegate must be present for decisions covered by the governance charter
• A data protection officer must be consulted on decisions involving personal data processing

Constitutional participants are always involved in high-stakes decisions. If they are missing, the decision has a governance gap.

Consultative

Consultative participants improve the decision through their expertise, but they do not own it and are not required by governance rules. Their input is valuable; their absence does not invalidate the process.

Examples:

• A senior engineer consulted on the feasibility of a technology migration
• A market analyst providing competitive intelligence for a market entry decision
• A customer success lead sharing churn patterns relevant to a pricing change
• An external industry advisor offering domain perspective

Consultative participants should be involved when the decision touches their domain. The key discipline is matching consultation to relevance — not every consultative expert needs to weigh in on every decision.

Operational

Operational participants are responsible for executing the decision outcome. Their feasibility input during framing matters because they are the ones who will carry the commitment forward.

Examples:

• An engineering team lead who will implement a technical architecture change
• A regional operations manager who will roll out a new process
• A procurement team member who will execute a vendor contract
• A logistics coordinator who will handle the physical deployment

Operational participants are involved when execution feasibility is in question. If the people who must carry out the decision have not validated that it can be carried out, the commitment is premature.

Participation roles

Each participant holds a role that describes what they do in the decision process.

Owner

The owner is accountable for the decision reaching commitment. There should be exactly one owner. The owner does not need to be the most senior person involved — they need to be the person who is accountable for driving the decision through the method to a governed outcome.

The owner ensures that the Decision Frame is well-formed, that the right participants are involved, that dissent is surfaced, and that the decision moves to commitment when it is ready.

Approver

The approver must sign off before commitment proceeds. This is a formal gate, not an informal nod. Approvers typically hold constitutional obligations — their sign-off is required by policy, authority structure, or regulatory mandate.

A decision can have multiple approvers. Each approver should have a clear basis for their approval authority. If it is unclear why someone is an approver, they should probably be a contributor instead.

Contributor

Contributors provide analysis, evidence, or domain expertise. They shape the decision through their input but do not own it or gate it. Most SMEs are contributors.

Contributors do their most valuable work during framing and exploration — the first two stages of the method. Their input should be captured in the Decision Frame and the analysis that informs the Decision Plan.

Executor

Executors are responsible for carrying out the committed decision. They translate the Decision Plan into action.

Executors should be involved during framing, not introduced after commitment. If the people who must execute a decision had no input into how it was framed, execution failures are predictable.

Mapping to common frameworks

These roles map to existing frameworks without being bound by them:

The distinction matters: RACI and DACI are project-management tools. These roles describe participation in a decision process, not a project. A person who is "Responsible" in RACI may be either an executor or a contributor depending on whether they execute the outcome or provide input to the analysis.

Use whatever framework your organization already understands, but be precise about what each role means in the context of a governed decision.

Internal decision teams and execution-critical participants

What "execution-critical" means

A participant is execution-critical when the decision cannot be carried out without their active involvement. This is stronger than "their input is useful" — it means that if this person is unavailable, uncommitted, or unaware, the decision will stall or fail during execution.

Execution-critical status is not about seniority. A regional logistics coordinator may be execution-critical for a supply chain decision while a VP is merely consultative.

Mark a participant as execution-critical when:

• the decision outcome directly depends on their capacity, authority, or cooperation
• no viable substitute exists within the execution timeline
• their absence would require the decision to be revisited or rolled back

Involving executors during framing

The most common execution failure is a decision framed without the people who must carry it out. The result is a commitment that looks clean on paper but collapses on contact with operational reality.

Executors should be present during the first two stages of the method: disciplined framing and risk-aware exploration. Their role at this stage is not to approve or own — it is to validate that the framing reflects execution constraints and that the proposed path is operationally feasible.

When executors are excluded from framing:

• execution timelines are based on assumptions rather than capacity
• operational constraints surface after commitment, forcing rework
• the people carrying out the decision have no context for the tradeoffs that shaped it

Surfacing readiness gaps

Execution-critical participants who have not been involved in framing represent a readiness gap. Before commitment, review the participant list and ask:

• Are all execution-critical participants identified?
• Have they validated the feasibility of the proposed approach?
• Do they have the capacity and authority to execute within the stated timeline?

If any answer is no, the decision is not ready for commitment. The gap should be resolved during framing, not discovered during execution.

Engaging stakeholders without weakening framing rigor

Premature consensus

Stakeholder input is not stakeholder approval. The purpose of involving participants in a decision is to improve the quality of the framing and analysis — not to build consensus before the problem is understood.

Premature consensus occurs when:

• the framing is shaped to accommodate stakeholder preferences rather than to define the problem clearly
• dissent is suppressed because a senior stakeholder has already signaled a preferred direction
• the decision team optimizes for stakeholder comfort rather than decision quality

This is how Upstream Decision Failure begins. A decision that enters commitment with unresolved framing gaps, incomplete risk assessment, or suppressed dissent will accumulate Decision Debt during execution.

Where stakeholder input belongs

Stakeholder input is most valuable during the Frame and Explore stages of the method. During framing, stakeholders help identify constraints, success criteria, and blind spots. During exploration, they help stress-test assumptions and surface risks.

Stakeholder input is least valuable — and most dangerous — when it substitutes for structured analysis. "The VP wants option B" is not analysis. It is a data point about preference that should be weighed alongside evidence, constraints, and risk assessment.

Preventing stakeholder theater

Stakeholder theater is performative inclusion that does not improve the decision. It looks like participation but adds coordination cost without analytical value.

Signs of stakeholder theater:

• participants are added to satisfy political expectations rather than decision needs
• meetings are scheduled to "align stakeholders" before the problem is framed
• the participant list grows with each review cycle but the framing does not improve
• senior participants attend but contribute no domain-specific input

The antidote is role clarity. Every participant should have an explicit obligation class and role. If someone is included but has no clear obligation or role, they should not be a participant.

Tiering consultation

Not every decision requires every stakeholder. Matching participation depth to decision characteristics prevents both under-consultation (missing critical input) and over-consultation (stakeholder fatigue and decision paralysis).

A tiering heuristic

Applying obligation classes to tiering

• Constitutional participants are always involved when policy requires it. For high-stakes decisions, this is non-negotiable. For low-stakes decisions, check whether the governance threshold is actually met before including them.
• Consultative participants are involved when the decision touches their domain. The discipline is specificity — "this decision affects infrastructure pricing, so we need the infrastructure lead" is good. "Let's loop in everyone who might care" is stakeholder theater.
• Operational participants are involved when execution feasibility is in question. For decisions with straightforward execution paths, a brief feasibility check may be sufficient. For decisions with complex or uncertain execution, operational participants should be present during framing.

Avoiding stakeholder fatigue

Organizations that involve too many people in too many decisions create a predictable failure mode: participants stop engaging meaningfully because they are overwhelmed with low-relevance consultation requests.

The fix is structural:

• use obligation classes to distinguish "must be involved" from "might be useful"
• tier participation to decision impact and reversibility
• make participation expectations explicit — a contributor who is asked to review a framing document has a different obligation than an approver who must sign off
• do not default to maximum inclusion; default to minimum viable participation and expand only when a specific gap is identified

When participants trust that they will only be involved in decisions that genuinely require their input, the quality of their engagement improves. That is the real goal — not maximum participation, but maximum decision quality.