You’re prepared when you can complete this sentence:
If
specific bad thinghappens, then Ispecific actionusingnamed resource/person/policy, which results inexpected outcome.
If you can’t complete that sentence, you’re still exposed. If you can, you’re done.
SOP: Reaching the Preparedness Threshold
Purpose
This procedure converts open-ended research into a concrete stopping point. Use it when you’re deep in research and can’t tell whether you’re being thorough or spinning.
- Without this: Research continues indefinitely, anxiety compounds, and you exhaust yourself without knowing if you’re actually safer.
- With this: You know the exact moment you’ve crossed from “exposed” to “prepared” and can stop with confidence.
Procedure
Inputs:
- A decision, risk, or situation you’re uncertain about
- Whatever research you’ve already done
Step 1. You have a specific worst-case scenario written down.
Use pre-mortem thinking: imagine the situation went badly. What specifically happened? Name it concretely.
| Too vague | Specific enough |
|---|---|
| ”Something goes wrong" | "The wax seal fails and water damages the unit below" |
| "I get in trouble" | "Strata charges me their [deductible amount] insurance deductible" |
| "It doesn’t work out" | "The contractor abandons the job mid-renovation” |
Step 2. You have a response action identified.
Ask: “If that happens, what do I do?” This must be a verb—an action you take, not a state you hope for.
| Not an action | Action |
|---|---|
| ”Hope it’s covered" | "File a claim under Section I" |
| "Deal with it" | "Call my adjuster and provide documentation" |
| "Figure it out" | "Invoke the warranty clause in the contract” |
Step 3. You have a named resource identified.
The resource is what makes your action possible. It must be specific enough that you could use it right now if needed.
| Vague | Named |
|---|---|
| ”My insurance" | "[Insurer] policy #[policy number], Condominium Deductible Coverage (Section I)" |
| "A lawyer" | "[Insurer] legal helpline: [direct line]" |
| "The contract" | "Indemnity Agreement Section 4(b), signed copy in [drive] > Strata > Reno” |
Step 4. You have an expected outcome stated.
What does success look like after you take the action? This closes the loop and confirms the action actually solves the problem.
| Incomplete | Complete |
|---|---|
| ”They’ll handle it" | "[Insurer] reimburses the deductible up to [coverage limit], no out-of-pocket" |
| "It’ll be fine" | "Contractor’s insurer pays for damage; I’m not personally liable" |
| "Problem solved" | "Strata withdraws the claim; no entry on my insurance history” |
Step 5. You’ve assembled the complete sentence and tested it.
Combine all four elements into the template:
“If
worst case, then Iactionusingresource, which results inoutcome.”
Read it out loud. Does every slot contain a specific, concrete element? If any slot is vague, return to that step.
Step 6. You’ve set tripwires for ongoing monitoring (optional but recommended).
The Preparedness Threshold tells you when to stop researching. Tripwires tell you when to start acting.
Use this template:
“I will check for
early warning signonspecific day/time. If I see it, I willresponse action.”
Example:
“I will check for a Section 135 notice in the mail every Monday. If I receive one, I will photograph it, email it to my adjuster, and respond within the 14-day window.”
Outputs
You’re done when you can say the complete sentence out loud with no vague slots:
“If the wax seal failed, strata claims on their insurance and charges me the deductible under Bylaw 2(3.2)(c), I file under Condominium Deductible Coverage (Section I) with [Insurer], and they reimburse up to [coverage limit] with no deductible.”
Observable confirmation: The sentence contains (1) a named scenario, (2) a specific action verb, (3) a named resource you could access today, and (4) a concrete expected result.
FAQs
What if I can’t complete the sentence? Then you’re not prepared yet. Either continue researching until you can, or consciously accept you’re taking the simple path (see Simplicity Moves Cost, It Doesn’t Reduce It).
How do I know if it’s specific enough? The “named resource” test: Could you use that resource right now if the scenario happened? If the answer is “I’d have to look it up first,” it’s not specific enough.
What if I have multiple worst-case scenarios? Complete the sentence for each one. You’re prepared when you can complete it for every scenario that matters. Use Question Generation SOP to prioritize which scenarios are “Must Answer.”
I completed the sentence but still feel anxious. Now what? The anxiety might not be about preparedness. If you have a specific response plan and still feel uneasy, the feeling is either (a) general risk aversion, (b) distrust of the resource, or (c) something else entirely. Name which one, then address that directly.
When should I use this vs. just deciding? Use this when there’s downside risk you care about. For low-stakes decisions, just decide. For decisions where failure has real consequences, run this procedure before acting.
What’s the difference between “informed” and “prepared”? Being informed means understanding the risk. Being prepared means knowing your response. You can understand a risk completely and still not know what you’d do. The sentence structure forces the latter.
Why This Works
The Sentence Structure Forces Specificity
Each component does specific work:
| Component | What it forces | Rejects |
|---|---|---|
| If [bad thing] | Name the specific scenario | Vague anxiety (“something might go wrong”) |
| Then I [action] | Name the specific response | Passive waiting (“deal with it then”) |
| Using [resource] | Name the tool/person/policy | Unspecified help (“call someone”) |
| Which results in [outcome] | Name the expected resolution | Uncertain endings (“figure it out”) |
You can’t complete the sentence with vague intentions. The structure itself rejects them.
Connection to The Causality Meta-Framework
The sentence structure isn’t arbitrary—it’s a causal chain:
If [trigger] → then [action] → using [resource] → which results in [outcome]
This is “therefore” thinking applied to risk:
| And-Then (fails) | Therefore (works) |
|---|---|
| “Something might go wrong AND I have insurance AND I’ll figure it out" | "If X happens, THEREFORE I do Y, WHICH ENABLES Z, RESULTING IN W” |
| List of disconnected elements | Consequence architecture |
Vague answers fail because they break the causal chain. “I’ll deal with it” has no therefore—no mechanism connecting trigger to resolution. The sentence structure forces you to build the full chain, which is why it rejects incomplete thinking.
This also explains why completing the sentence feels different from just “knowing more.” Knowledge is accumulation. Preparedness is causation—knowing that A leads to B leads to C. The chain is what makes you ready, not the volume of information.
Connection to Certainty Framework
The Certainty Framework structures recommendations:
[Action] SHOULD [Outcome], based on [Evidence], assuming [Assumption], mitigated by [Pilot/Test].
The Preparedness Threshold is the defensive version—applied to risk rather than recommendation:
| Certainty Framework | Preparedness Threshold |
|---|---|
| ”This should work because…" | "If this fails, I will…” |
| Confidence in success | Confidence in recovery |
| Proactive | Reactive |
| Enables action | Enables stopping |
Both require: specific action + named resource + expected outcome.
Connection to Simplicity Moves Cost, It Doesn’t Reduce It
That framework says take the simple path if:
- The worst case is survivable
- You’re the one who pays (or those paying consented)
The Preparedness Threshold adds: and you know what you’ll do when the cost comes due.
- Simple path without response plan = gambling
- Simple path with response plan = calculated bet
Connection to The Output Contract
The Preparedness Threshold and The Output Contract are companion stopping rules:
| The Preparedness Threshold | The Output Contract |
|---|---|
| Answers: “When do I stop researching?” | Answers: “When do I stop planning?” |
| Test: Can I complete the sentence? | Test: Can I point to the action I took? |
| Produces: Readiness despite uncertainty | Produces: Traction despite incomplete clarity |
| Stops: Research that doesn’t change your response | Stops: Planning that doesn’t change your behavior |
Both prevent productive-feeling avoidance. Research feels responsible. Planning feels strategic. But research that doesn’t improve your response plan is spinning. Planning that doesn’t convert to action is comfort.
Use them together:
- Preparedness Threshold → Know your response to failure
- Output Contract → Convert that clarity to action same-day
Connection to Six Rules for Effective Forecasting
Paul Saffo’s forecasting framework illuminates why the Preparedness Threshold works.
The Cone of Uncertainty
Saffo argues forecasters should “map a cone of uncertainty”—the range of possible futures expanding from the present. The cone isn’t static; it widens and narrows as events unfold. Critically: drawing the cone too narrowly is worse than drawing it too broadly.
The Preparedness Threshold operates within this cone. You’re not trying to predict which future arrives—you’re preparing your response to the futures that matter most. The sentence structure (“If X happens, then Y using Z”) is how you map your response across the cone without requiring certainty about which scenario materializes.
Strong Opinions, Weakly Held
Saffo’s principle: form a forecast as quickly as possible, then set out to disprove it. The Preparedness Threshold version:
- Complete the sentence with your best current answer (strong opinion)
- Set tripwires to detect if your assumptions break (weakly held)
- Revisit only when tripwires fire, not continuously
This prevents both extremes: endless research (never forming an opinion) and false certainty (never testing it).
The Destroyer Story
On September 8, 1923, nine U.S. destroyers ran aground on the California coast. The squadron commander on USS Delphy had radio bearing data that contradicted his dead-reckoning position. Convinced his reckoning was right, he reinterpreted the data to fit his conclusion—and led nine ships onto the rocks.
Meanwhile, the skipper of USS Kennedy (11th in formation) faced the same conflicting data. His deck officers’ reckoning also suggested they were closer to shore than the Delphy claimed. Rather than resolve the contradiction, he hedged—ordering a course change that placed his ship several hundred yards west of the formation. When the Delphy crashed, the Kennedy and three trailing destroyers survived.
| USS Delphy (disaster) | USS Kennedy (survived) |
|---|---|
| Ignored conflicting weak signals | Listened to multiple weak signals |
| Narrowed certainty when data said broaden | Accepted uncertainty, hedged position |
| Knew where he was (wrongly) | Knew what to do given uncertainty |
| Felt prepared | Was prepared |
The Kennedy’s skipper didn’t know their true position. But he knew his response to uncertainty: hedge west. That’s the Preparedness Threshold. Preparedness isn’t certainty about what will happen—it’s clarity about what you’ll do when you don’t know.
Connection to Illusion of Competence
The Illusion of Competence describes the gap between feeling like you’ve learned something and actually being able to use it. Highlighting a textbook feels like studying. Recognizing an answer feels like knowing it. But recognition isn’t recall. The test is whether you can produce the knowledge without cues.
The same illusion applies to preparedness:
| Illusion of Competence | Illusion of Preparedness |
|---|---|
| Highlighting feels like learning | Researching feels like preparing |
| Recognition ≠ recall | Understanding risk ≠ knowing your response |
| Test: explain without notes | Test: complete the sentence without vague slots |
| Cure: retrieval practice | Cure: the Preparedness Threshold sentence |
If you can’t complete the sentence with specifics—named resource, concrete action, expected outcome—then your feeling of preparedness is an illusion. You’ve recognized the risk but can’t recall your response.
The sentence structure functions like retrieval practice for risk response. It forces you to produce the answer, not just recognize that an answer exists somewhere. That’s why it feels different from “knowing about” a risk. Knowing about is recognition. Completing the sentence is recall.
Common Traps
“One more search” After the threshold, more information makes you more informed but not more prepared. Those are different. Knowing more doesn’t change your response plan.
Confusing understanding with preparedness You can understand a risk completely and still not know what you’d do about it. The sentence forces the response, not just the analysis.
Vague resources “Call a lawyer” isn’t a response. “Call [name] who handled [similar situation], using the documentation in [folder]” is a response. Named resources are the difference between prepared and pretending.
Skipping to action The threshold isn’t “just do something.” Acting without a failure response is the same as not researching at all. The point is knowing your fallback, not ignoring that you need one.
Origin: How This Insight Emerged
This came from exhaustion.
I spent days researching a strata indemnity agreement for a toilet and hot water tank replacement. It started with a potential liability claim after water damage appeared in the unit below. No proof it was us. Just pressure to “call our insurance.”
One question led to another:
- Are we liable under the bylaws? → Strict liability, toilets explicitly listed
- Does the indemnity agreement create new exposure? → Section II exclusion for “liability assumed by contract”
- Would our insurance cover us? → Depends which coverage type
- What if → What if → What if…
I traced through bylaws, case law, insurance policy wordings, strata meeting minutes. I built a complete picture of every possible scenario.
The Question That Followed
I asked myself: Is all of this research worth doing if it doesn’t change the outcome?
By one measure—outcome—no, not if I would have been covered either way. The blind signer who doesn’t read anything ends up in the same position.
By another measure—intention—yes. I was protecting people I love from a risk they couldn’t see.
But the real question wasn’t “was this right.” It was: when should I have stopped?
I already had frameworks that should have answered this—Certainty Framework, Question Generation SOP, Pareto Diagnostic Framework. But none of them stated a clear stopping rule. They all converge on the same underlying structure. None made it explicit.
The Preparedness Threshold is that explicit stopping rule.
The Meta-Insight
Anxiety is unbounded. Fatigue recovers.
Research converts anxiety into fatigue. That’s valuable. But the conversion happens at the threshold—when you know your response. Everything after that is refinement, not protection.
Knowing when to stop isn’t laziness. It’s recognizing that “prepared” and “completely informed” are different destinations, and only one of them is reachable.
North: Where this comes from
- Certainty Framework (action + evidence + assumption + mitigation structure)
- Question Generation SOP (prioritized question hierarchy)
- Simplicity Moves Cost, It Doesn’t Reduce It (survivability test)
- Pareto Diagnostic Framework (minimum viable assessment)
- The Causality Meta-Framework (the sentence is a causal chain—“therefore” thinking applied to risk)
- Six Rules for Effective Forecasting (cone of uncertainty, strong opinions weakly held)
East: What opposes this?
- Analysis Paralysis (never reaching the threshold)
- Perfectionism (believing the threshold requires complete knowledge)
- Gut Decisions (acting without checking preparedness)
- Illusion of Competence (feeling prepared without being prepared)
South: Where this leads
- The Output Contract (once prepared, convert clarity to action same-day)
- Confident action (acting because you know the fallback)
- Sustainable thoroughness (research calibrated to exposure)
- Reduced anxiety-to-fatigue cycle
West: What’s similar?
- Pre-Mortem Thinking (imagining failure before it happens)
- Emergency response planning (if X, then Y using Z)
- Insurance thinking (surviving loss, not preventing it)
- Strong Opinions Weakly Held (form position quickly, test it, discard if wrong)