Map Every Decision Before You Move
Two teams face the same market opportunity. One debates it for weeks, then acts on instinct. The other maps the decision in an afternoon — defining trade-offs, assigning probabilities, writing the kill criteria before a single dollar is spent. Three months later, one team is defending a sunk cost nobody can explain. The other has already pivoted to the next bet.
The difference wasn't talent or data. It was process.
Strategy is not just what you choose to pursue — it's what you commit to refusing. Every significant move deserves a framework that forces explicit trade-offs, attaches measurable triggers, and defines what "stop" looks like before you start. Without that discipline, decisions accumulate into drift.
Why a Decision Framework Matters
When uncertainty is high, intuition alone produces inconsistent choices and hidden bias. A repeatable decision process serves three purposes: it prioritises objectively, limits regret by defining exit rules before you need them, and creates accountability for stopping when the evidence turns.
The goal is not to eliminate uncertainty. It's to convert uncertainty into manageable options — with clear criteria for action, and for inaction.
Key decision making frameworks:
Framework | Best for | Core mechanism | When to use |
|---|---|---|---|
OODA Loop | Fast, iterative decisions | Observe, Orient, Decide, Act | Time‑sensitive moves and rapid learning |
Decision Tree with Expected Value | Sequential, probabilistic choices | Map branches, assign probabilities and payoffs | High‑stakes investments and phased rollouts |
MCDA Multi Criteria Decision Analysis | Complex tradeoffs across many objectives | Weighted scoring across criteria | Vendor selection, strategic option ranking |
RICE / ICE Scoring | Prioritizing many initiatives | Score by Reach/Impact/Confidence/Effort or Impact/Confidence/Effort | Feature prioritization and backlog triage |
Eisenhower Matrix | Urgency versus importance tradeoffs | Categorize tasks by urgency and impact | Short‑term prioritization and resource focus |
How to Decide What You Will Do and What You Will Not Do
- State the decision and baseline.
Objective: a measurable outcome including a “do nothing” baseline. This anchors comparisons and prevents scope creep. - Choose the right framework for the decision.
Match complexity to method: use RICE/ICE for many small bets, MCDA for complex tradeoffs, Decision Trees for sequential investments, and OODA when speed and adaptation matter. - Score options and include a baseline.
Quantify benefits, costs, and confidence. Always compare against the baseline of inaction. - Design explicit kill criteria.
For every chosen option, define clear stop rules: metric, threshold, and deadline. Treat kill criteria as strategic commitments. - Attach ownership and monitoring.
Name who watches the metrics and who has authority to stop or scale the initiative. - Declare the not‑to‑do list.
Publish a short list of excluded actions, markets, or features. Visibility reduces scope creep and aligns teams. - Timebox and review.
Set review cadence tied to triggers so decisions are revisited with fresh evidence, not emotion.
Decision memo template
- Decision: short description
- Objective: measurable outcome and baseline
- Options considered: A; B; C; Do nothing
- Framework used: e.g., Decision Tree / RICE / MCDA / OODA
- Key assumptions: top 3 assumptions and confidence levels
- Success metrics: primary KPI(s) and target values
- Kill criteria: metric, threshold, date → action (pause/stop)
- Owner: who monitors metrics and who can stop
- Review cadence: weekly/biweekly/monthly
Kill criteria example
- Pilot conversion < 10% after 90 days → pause expansion.
- CAC > 2x target for two consecutive months → stop paid acquisition.
- Regulatory delay extends beyond 6 months → reallocate budget.
Quick scoring checklist for RICE/ICE
- Reach: how many users/customers affected
- Impact: expected effect on objective
- Confidence: evidence supporting estimates
- Effort: resources required
Score and rank; exclude options below a pre‑set score threshold.
Common Pitfalls and How to Avoid Them
- Paralysis by analysis: limit frameworks to one primary method plus one sanity check; timebox the analysis.
- False precision: treat probabilities as ranges; use decision trees to show sensitivity to assumptions.
- No enforcement: pair every decision with a named owner and a kill rule; without enforcement, stop rules are meaningless.
- Misaligned incentives: ensure KPIs used for monitoring reflect the strategic trade‑offs you chose.
Short Example
A company considers entering a new vertical. They:
- Set the objective: 100 paying customers in 12 months or do nothing.
- Use a Decision Tree to model phased investment with probabilities for rapid adoption, slow adoption, and regulatory delay.
- Run a six‑week pilot scored with RICE to prioritize features.
- Define kill criteria: trial→paid conversion < 10% after three months → pause expansion.
- Publish a not‑to‑do list excluding full enterprise suite development until product‑market fit is proven.
This makes the bet reversible, measurable, and enforceable.
Closing
Strategy becomes powerful when it converts uncertainty into decisions with rules. Use scoring, probabilistic modeling, rapid loops, and explicit kill criteria to decide what you will do and what you will not do. Commit to ownership, timeboxed reviews, and a visible not‑to‑do list. Execution will be faster, less wasteful, and far more decisive when every move is made with the full field of play in view.