Enable Decisions and Escalation

Flow · 7 controlled steps

1. 01

   Frame the decision question

   Turn a concern or stalled conversation into a bounded decision.

   • — State what must be decided, why now, intended outcome, affected work and people, deadline, reversibility, and cost of delay.
   • — Separate facts, interpretations, assumptions, preferences, and unknowns.
   • — Identify current action, interim control, and consequence if no decision arrives.
   • — Split compound questions or route matters that belong to governed specialist processes.

   Responsible

   Decision-process owner

   Output

   Decision Brief

   Decision

   Is there a sufficiently clear and legitimate decision to make?

2. 02

   Resolve authority and participation

   Place the decision with the lowest capable authorized owner and the right contributors.

   • — Map decide, recommend, consult, execute, and inform roles and identify conflicts or unavailable authority.
   • — Confirm technical, fiduciary, budget, safety, quality, people, legal, regulatory, and policy boundaries.
   • — Choose the smallest participant set that covers material expertise and affected interfaces.
   • — Set response time, escalation level, delegation, proxy, and fallback authority.

   Responsible

   Decision-process owner

   Output

   Decision Authority Record

   Decision

   Who has sufficient authority, competence, proximity, and accountability to decide?

3. 03

   Assemble sufficient decision evidence

   Reduce consequential uncertainty without turning analysis into indefinite delay.

   • — Define decision criteria, constraints, guardrails, evidence sources, confidence, and the value of additional information.
   • — Gather current operational, customer, technical, financial, workforce, risk, quality, safety, and dependency evidence proportionate to consequence.
   • — Make assumptions, data limitations, conflicting evidence, and qualified dissent visible.
   • — Time-box analysis and identify what can be learned after a reversible decision.

   Responsible

   Decision-process owner and subject-matter owners

   Output

   Decision Evidence Record

   Decision

   Is the evidence sufficient for this decision’s consequence and reversibility?

4. 04

   Form options and consequences

   Make real alternatives and their system effects comparable.

   • — Develop continue, stop, defer, stage, test, redesign, contain, delegate, resource, or other feasible options.
   • — Include a no-change or no-decision consequence and reasonable fallback.
   • — Assess intended effect, cost, timing, dependencies, reversibility, implementation, affected processes, and guardrails.
   • — Seek disconfirming evidence and surface tradeoffs rather than presenting one recommendation as the option set.

   Responsible

   Proposer or recommendation owner

   Output

   Decision Options Record

5. 05

   Decide and record

   Convert evidence and authority into an explicit state.

   • — Review the question, criteria, evidence, uncertainty, options, recommendation, dissent, authority, and time constraint.
   • — Choose an outcome and state rationale, assumptions, conditions, limits, effective time, implementation owner, fallback, and review trigger.
   • — Record evidence requests, deferrals, delegations, and no-decision outcomes with the same clarity as approvals.
   • — Do not claim consensus where material disagreement remains.

   Responsible

   Decision owner

   Output

   Authorized Decision Record

   Decision

   Which authorized state best serves the outcome within constraints and acceptable risk?

6. 06

   Communicate and hand off implementation

   Make the decision real across affected work and connected processes.

   • — Communicate what was decided, why, what changes, what does not, when it applies, and where questions go.
   • — Transfer actions, resources, constraints, conditions, and evidence to implementation and connected owners.
   • — Update authoritative plans, workflows, priorities, risks, controls, and records and retire superseded assumptions.
   • — Obtain acknowledgement from material receiving owners and escalate rejected or impossible handoffs.

   Responsible

   Decision-process owner

   Output

   Decision Implementation Handoff · Connection Notices · Updated Operating State

   Decision

   Can receiving owners implement the exact decision under its conditions?

7. 07

   Review outcome and improve decision flow

   Test the decision and the mechanism rather than merely closing the record.

   • — Review intended outcome, implementation, assumptions, side effects, affected people, guardrails, new evidence, and changed conditions.
   • — Distinguish decision quality from outcome luck and implementation quality.
   • — Choose continue, adapt, reverse, replace, or escalate and update authoritative state.
   • — Review recurring delays, escalations, overrides, authority gaps, evidence defects, and handoff failures for system improvement.

   Responsible

   Decision owner

   Output

   Decision Outcome Review · Decision-System Improvement Record

   Decision

   What does outcome evidence justify now?

Connections

Seams · 11 hops within 2 steps

Upstream and downstream neighbourhood over public reference processes only. Each hop shows the trigger, carried objects, and what the receiving process loses if the producing step is skipped.

Roles

Systems + Data

Measures

Evidence + judgment

Draft reference standard. Requires client context and qualified technical, fiduciary, finance, employment, labor, accessibility, safety, quality, privacy, security, conduct, legal, regulatory, and jurisdiction-specific review before deployment.