Methods
These methods turn high-pressure decisions into clear calls with ownership and next actions.
- Move faster without skipping rigor.
- Make tradeoffs explicit before commitment.
- Leave with one owner and a concrete next move.
How to use this page
- Pick one method based on your current bottleneck.
- Apply the steps exactly once before re-opening debate.
- Decide your next action and route to the right session.
You can browse all briefs in /briefs, or go directly to /sprint and /ignite.
FAST Pressure Protocol
Definition: A time-bound protocol for high-stakes calls under deadline pressure.
When to use
- Decision window is 24 to 72 hours.
- Delay risk is rising daily.
- Team is split on urgency versus rigor.
Steps
- Frame the exact decision and scope.
- Assure minimum viable rigor.
- Select one path and owner.
- Track a short-interval checkpoint.
Output artifact: Pressure decision brief with owner, timeline, and checkpoint.
Related briefs:
- High-Stakes Decisions Under Time Pressure
- High-Stakes Decision Brief
- Making Decisions With Incomplete Data
Best fit session: Ignite when one urgent call needs closure now.
Decision Brief Protocol
Definition: A one-paragraph record of the decision, rationale, owner, and what changes the call.
When to use
- Decisions are being re-litigated.
- Ownership is unclear after meetings.
- Cross-functional execution is drifting.
Steps
- Write the decision in one sentence.
- Add why this option won.
- Name owner and first deadline.
- Add revision trigger.
Output artifact: One-paragraph decision brief.
Related briefs:
Best fit session: Ignite when the problem is clarity of one live decision.
Criteria Lock
Definition: A method to lock 3 to 5 decision criteria before option debate begins.
When to use
- Criteria keep changing mid-discussion.
- Stakeholders are arguing past each other.
- Option scoring feels political.
Steps
- List candidate criteria.
- Select 3 to 5 non-negotiable criteria.
- Define each criterion in plain language.
- Freeze criteria for current decision cycle.
Output artifact: Locked criteria set with shared definitions.
Related briefs:
Best fit session: Sprint when multiple stakeholders need one scoring standard.
Scoreboard Comparison
Definition: A shared scoring sheet that compares options against locked criteria in one view.
When to use
- Two or more options look equally plausible.
- Teams are using different decision logic.
- Final call needs documented tradeoffs.
Steps
- Create one table with all options.
- Score each criterion per option.
- Add downside notes per option.
- Select highest-confidence path.
Output artifact: Option scoreboard with selected path and rationale.
Related briefs:
Best fit session: Sprint when tradeoffs are real and visible scoring is needed.
Reversibility Gate
Definition: A gate that classifies decisions by reversibility and sets the right pace.
When to use
- Everything is treated as equally urgent.
- Teams over-analyze reversible calls.
- Irreversible calls are moving too fast.
Steps
- Classify the decision as reversible or not.
- Estimate downside if wrong.
- Set speed and rigor by class.
- Publish gate outcome before execution.
Output artifact: Reversibility classification and decision pace rule.
Related briefs:
Best fit session: Ignite for one call, Sprint for system-wide use.
Correction Trigger Design
Definition: A pre-defined signal that forces review or course correction after commitment.
When to use
- Teams avoid defining failure conditions.
- Calls stay open-ended after launch.
- Re-openings happen without evidence.
Steps
- Define one success signal.
- Define one correction trigger threshold.
- Set review date and owner.
- Pre-commit correction action.
Output artifact: Success signal + correction trigger pair.
Related briefs:
Best fit session: Ignite when execution is active and trigger design is missing.
Commitment Mechanics
Definition: A closeout method that assigns owner, timeline, and first 72-hour actions.
When to use
- Decisions are made but work does not start.
- Accountability is distributed and vague.
- Teams ask for one more meeting before action.
Steps
- Assign one accountable owner.
- Set timeline and first checkpoint.
- Define first 72-hour actions.
- Publish commitment to stakeholders.
Output artifact: Commitment plan with owner, timeline, first 72 hours.
Related briefs:
Best fit session: Sprint when commitment failure spans multiple teams.
Disagreement Timebox
Definition: A bounded disagreement window with a final decider and closure time.
When to use
- Founder or executive disagreement is stalling progress.
- Debate quality is high but endless.
- Team confidence is dropping due to ambiguity.
Steps
- Timebox debate window.
- Define decision scope and decider.
- Capture assumptions from both sides.
- Close at deadline and publish call.
Output artifact: Timeboxed disagreement log and final decision.
Related briefs:
Best fit session: Sprint when disagreement affects core company direction.
Capacity Allocation Grid
Definition: A grid that allocates constrained resources by impact, effort, and dependency drag.
When to use
- Too many priorities for current capacity.
- Work starts but does not finish.
- Priority changes are constant.
Steps
- Set capacity ceilings by function.
- Score initiatives by impact and effort.
- Penalize dependency-heavy items.
- Fund top set and pause the rest.
Output artifact: Funded initiative grid and pause list.
Related briefs:
Best fit session: Sprint when leadership needs one quarter-level allocation call.
Vendor Risk Exit Map
Definition: A vendor decision method that scores control, lifecycle cost, and exit feasibility before commitment.
When to use
- Vendor lock-in risk is unclear.
- Buy vs build is contested.
- Reliability and governance concerns conflict with price pressure.
Steps
- Define non-negotiable control requirements.
- Compare lifecycle cost, not only contract cost.
- Score exit complexity and migration burden.
- Select vendor with explicit risk owner.
Output artifact: Vendor risk map with selection rationale and exit notes.
Related briefs:
Best fit session: Ignite for one vendor choice, Sprint for platform-level stack decisions.
The Clarity Frame artifacts
- Decision statement: One sentence describing the exact call.
- Criteria set: 3 to 5 locked criteria used for evaluation.
- Option scoreboard: Side-by-side comparison against criteria.
- Commitment plan: Owner, timeline, and first 72-hour actions.
- Success signal: The metric that confirms the decision is working.
- Correction trigger: The signal threshold that forces review.
- Risk and rollback notes: Known downside and fallback path when relevant.
Choose your session
Clarity Sprint
- Best for: Multi-stakeholder, high-consequence decisions.
- You leave with: Decision brief, scoreboard, commitment plan.
- Typical pace: Deeper pressure test and full closeout in-session.
Go to Clarity Sprint.
Clarity Ignite
- Best for: One urgent decision with narrow scope.
- You leave with: Clear call, owner, and next checkpoint.
- Typical pace: Fast resolution with practical guardrails.
Go to Clarity Ignite.
FAQ
What is a decision brief?
A decision brief is a one-paragraph record of the call, why it won, who owns execution, and what trigger changes it.
How many criteria should we use?
Use 3 to 5 criteria. Fewer can miss key tradeoffs. More usually slows scoring and creates debate noise.
What is a correction trigger?
A correction trigger is a pre-defined signal threshold that forces review and potential change to the chosen path.
When is Ignite better than Sprint?
Ignite is better when one urgent, bounded decision needs fast closure. Sprint is better when tradeoffs span teams and downside is higher.
How do you handle founder disagreements?
Use a disagreement timebox, define the final decider, capture assumptions, and close at a fixed deadline.
What if we lack data?
Use minimum viable rigor, make assumptions explicit, and attach correction triggers so the decision can adapt safely.
Can these methods work for teams, not just founders?
Yes. The methods are built for founders, operators, and executive teams making high-pressure decisions.
Where should I start if everything feels stuck?
Start with FAST Pressure Protocol for the immediate call, then apply Commitment Mechanics to force execution.