When to Use the Decision Lifecycle
Most decisions don’t need a framework. Your autopilot handles 90%+ of life correctly. The Decision Lifecycle exists for the exceptions — the 2-5% where autopilot creates risk you don’t want to take.
This note helps you recognize which decisions warrant conscious process, and prevents both under-investment (dismissing things that matter) and over-investment (analyzing everything).
The Distribution
ALL STIMULI
│
├── 90%+ → AUTOPILOT (no framework needed)
│
├── ~8% → QUICK WEIGH (Stages 1-2 only, usually → "just try it")
│
└── ~2% → FULL PROCESS (Stages 3-10)
If you’re running everything through the framework, you’ve misunderstood it. If you never use it, you’re probably missing the exceptions that matter.
The “No Framework” Test
| If… | Then… |
|---|---|
| You’ve done this type before and it worked | Autopilot |
| Outcome is easily reversible | Autopilot |
| You’re the only one affected | Autopilot is probably fine |
| Cost of being wrong < cost of thinking about it | Just try it |
If all four are true → autopilot. Trust your gut.
The Analysis Anxiety Test
“If I just did what feels right, what’s the worst realistic outcome? Can I survive that?”
| If you can answer… | Then… |
|---|---|
| ”Worst case is X, and I can handle X” | Autopilot — survivable downside |
| ”I can’t name the worst case” or “I couldn’t handle it” | Enter Stage 1 |
This isn’t about eliminating risk. It’s about knowing whether the risk is worth analyzing.
Trigger Thresholds
If ANY of these are true → enter Stage 1 (ROUGH FRAME):
| Trigger | What It Means |
|---|---|
| Irreversibility | Can’t easily undo, exit, or course-correct |
| Consequence magnitude | Bad outcome would materially affect life, work, relationships, or finances |
| Novelty | No existing heuristic applies — you’re in unfamiliar territory |
| Recurrence | Will face this type again — worth building capability, not just deciding |
| Stakeholder exposure | Others meaningfully affected by your choice |
| Hesitation signal | Keeps returning to mind, or you notice yourself avoiding it |
If no triggers met → autopilot. The absence of triggers is permission to trust your default.
What Happens After Entry
Stage 1 (ROUGH FRAME): State the decision in one sentence. 10 seconds.
Stage 2 (WEIGH): “Is the cost of analysis higher than the expected cost of being wrong?”
| WEIGH Result | What To Do |
|---|---|
| Reversible + low cost if wrong | ”Just try it” — exit framework |
| Irreversible OR high cost if wrong | Continue to Stage 3+ |
Most entries stop at Stage 2. “Just try it” is the framework working correctly, not a failure to use it.
Addressing Both Failure Modes
For Under-Investors
“None of my decisions are worth this much process.”
Most aren’t. That’s correct. If no triggers are met, autopilot is the right answer.
This framework exists for the exceptions — where autopilot creates risk you don’t want. The trigger thresholds help you identify those exceptions without having to analyze everything.
If uncertain whether something qualifies, run Stages 1-2 (30 seconds total). WEIGH will usually say “just try it.” That’s the system working.
For Over-Investors
“I have this tool, so I should use it for everything.”
If you’re running everything through this, you’ve misunderstood it.
Stage 2 exists specifically to say “this doesn’t need more process.” The 10 stages aren’t a checklist to complete — they’re options for when you need them.
Signs you’re over-investing:
- Running trivial decisions through multiple stages
- Feeling like you “should” analyze things that don’t meet any trigger
- Decision fatigue from too much conscious processing
- The framework feels like a burden rather than a tool
The goal is to get OUT of the framework as quickly as possible for decisions that don’t warrant it.
Calibration Over Time
Your triggers won’t be perfect. You’ll:
- Miss things that turned out to matter (under-recognition)
- Over-process things that didn’t warrant it (over-recognition)
The fix isn’t better real-time filtering. It’s learning.
Weekly Audit Questions
“What did I autopilot this week that turned out to matter more than I thought?”
If something surfaces:
- What trigger should have caught it?
- What signal did I dismiss or miss?
- How do I notice that pattern next time?
“What did I over-process this week that didn’t warrant it?”
If something surfaces:
- Why did I think it needed analysis?
- Was I using the framework to avoid acting?
- What made this feel bigger than it was?
The Mindset
The framework trains your autopilot over time. Each audit improves your pattern-matching for what deserves conscious attention.
You’re not trying to catch everything in real-time — that’s hypervigilance. You’re trusting your defaults, learning from misses, and improving gradually.
Why Not Real-Time Tripwires?
You might think: “Why not scan every stimulus against the trigger list?”
Because that’s hypervigilance with extra steps:
| Healthy Awareness | Hypervigilance |
|---|---|
| Default: “This is probably fine” | Default: “This might be important” |
| Triggered by anomaly | Triggered by everything |
| Quick and automatic | Effortful and depleting |
| Trusts pattern-matching | Distrusts pattern-matching |
| Learns from misses | Tries to prevent all misses |
The triggers are for post-hoc calibration, not real-time scanning. When you notice something mattered that you dismissed, the triggers help you understand what you missed.
Domain-Specific Vigilance
There may be specific domains where YOU tend to under-recognize. These warrant extra attention — not because everything in that domain needs analysis, but because your autopilot is miscalibrated there.
Common high-risk domains:
- Legal commitments (irreversibility hidden in language)
- Relationship precedents (small moments create patterns)
- Health decisions (compounding effects invisible until too late)
- Financial commitments (recurring costs feel small, compound large)
If you’ve identified a domain where you consistently under-recognize, the intervention is: “When I’m in this domain, slow down and check triggers.”
That’s targeted vigilance, not general hypervigilance.
Quick Reference
| Situation | Action |
|---|---|
| No triggers met, survivable downside | Autopilot |
| Uncertain if it qualifies | Run Stages 1-2 (30 sec) |
| Any trigger met | Enter Stage 1, let WEIGH decide depth |
| WEIGH says reversible + low cost | ”Just try it” — exit |
| WEIGH says irreversible OR high cost | Continue to Stage 3+ |
| Weekly review | Audit what you over/under-processed |
North: Where this comes from
- The Decision Lifecycle (the framework this contextualizes)
- The Limit of Borrowed Signal (when research can’t help anyway)
- Diagnosing Decision Default Type (predicting your failure mode)
East: What opposes this?
- Analysis Paralysis (over-investment failure mode)
- Premature Action (under-investment failure mode)
- Hypervigilance (trying to catch everything in real-time)
South: Where this leads
- Appropriate framework use (right tool, right decision)
- Calibrated intuition over time
- Permission to trust autopilot for most of life
West: What’s similar?
- When to Build Systems (parallel structure in Decision Lifecycle)
- Satisficing (good enough for low-stakes)
- Bounded Rationality (can’t analyze everything)