Most of the time, we’re not short on intelligence — we’re short on visibility. These seven models won’t remove the weather, but they’ll help you drive in the rain.

A while back, I wrote about avoiding collaboration traps — the Abilene Paradox, Parkinson’s Law, and Chesterton’s Fence — with a handful of strategies for saner decisions in groups. The gist: teams drift when nobody says what they think, work expands to fill the calendar, and we tear down old structures without understanding why they were built. If you missed it, here’s the one-liner: before you hit send or sit down to meet, check for group drift, false urgency, and the hidden purpose of the “fence.” (Link: my earlier post on group decision-making and problem-solving.)

Today is the inner complement: seven pocket-size models for clearer individual sensemaking — the upstream habits that make downstream collaboration easier.

1) Ockham’s Razor — Simpler usually wins.

Intro​
Our brains adore hidden plots. Reality prefers duct tape and calendar mix-ups.

Explainer​
Ockham’s Razor: if two explanations fit, favor the one with fewer assumptions.

• Traffic falls: shadow ban… or the analytics pixel broke during the deploy.
• A partner “stole” your idea: malice… or convergent thinking off the same brief.
• A “disruptor” seems magical: genius… or a cheaper distribution channel.

Practical Offering​
Run the B.A.S.I.C. cut when things feel dramatic:

1. Boring cause first,
2. Assumptions named
3. Second simple story
4. Improbables removed
5. Check the clock (what changed right before this?).
   If the boring story still fits, ship it.

→ When simplicity has you calmer but not kinder, upgrade your generosity…

2) Hanlon’s Razor — Don’t assume malice when ignorance will do.

Intro​
Evolution tuned us to over-detect threats. Email threads don’t need saber-tooth anxiety.

Explainer​
Hanlon’s Razor reframes friction:

• Ops “ignored” your ticket → intake form routes to a dead Slack channel.
• Team “stonewalls” you → incentives punish transparency, so silence feels safe.
• Vendor “ghosted” → your ask lives across three owners, none with authority.

Practical Offering​
Use NICE before you escalate:
​Nudge once (neutral ping) → Inquire for constraints (“What’s blocking this?”) → Clarify the ask (one-liner, one owner) → Escalate kindly (state impact + propose next step).
Most fires go out at “N.”

→ Even with generosity, first impressions still bend the frame. Let’s unbend it…

3) Halo Effect — When first impressions overstay their welcome.

Intro​
One shiny trait and we hand out lifetime memberships.

Explainer

• Beautiful UI ⇒ “The system must be reliable.” (Ask the on-call.)
• Calm presenter ⇒ “This plan must be safe.” (It may be calmly wrong.)
• Prestige brand ⇒ “This hire will soar.” (Prestige ≠ context fit.)
  The spotlight becomes a floodlight — and hides the trip hazards.

Practical Offering​
Do a decouple check: name the trait you like (“clear writing”), then list three things it doesn’t guarantee (“timely delivery,” “good judgment,” “follow-through”).
Make one decision using only non-halo evidence (benchmarks, references, trials).

→ Once the light stops blinding you, notice where you’re only looking where it’s bright…

4) Streetlight Effect — Searching where it’s easy, not where it’s true.

Intro​
We don’t just follow the data; we follow the light.

Explainer

• Health: You optimize to 10,000 steps (visible) while ignoring sleep debt and 3 p.m. dread (messy).
• Community: You count RSVPs, not belonging. The dashboard looks great; the neighborhood doesn’t.
• Strategy: You polish OKRs while the real constraint is an unwritten turf war.
  Visible ≠ real. Real often lives just outside the beam.

Practical Offering​
Run the Dark Corner Drill:

• Name the blind spot: “What matters here that we aren’t measuring?”
• Add one proxy: weekly 1–5 trust check, 10-minute user call, “mentions of confusion” in support tickets.
• Allocate 10% time to non-instrumented investigation. The 10% often pays for the 90.

→ And while we’re outside the beam, remember: your view isn’t the default…

5) False Consensus Effect — You are not the control group.

Intro​
Your beliefs feel normal because you live inside them all day.

Explainer

• Product: You think onboarding is obvious; new users bounce at step two.
• Culture: Async feels freeing to you; isolating to someone else.
• Policy: You “know” feedback is welcome; reports assume it’s risky.
  Designing from your head alone is designing for ghosts.

Practical Offering​
Try a 3×3 disconfirm: ask three people unlike you (role, tenure, background) three questions — “What’s unclear?”, “What would you change?”, “What did I miss?”
Treat surprise as a success metric. More surprise, clearer thinking.

→ Perception calibrated? Good. Now guard your judgment from the first story you heard…

6) Anchoring — Beware the first number (or narrative).

Intro​
A forecast says 40% growth. Months later, 32% feels like failure — even though it’s your best year.

Explainer​
Anchors aren’t just prices; they’re first stories: a confident estimate, a rumor about a competitor, last year’s budget, the opening offer on a house. Once set, “reasonable” orbits the first claim.

Practical Offering​
Use Re-anchor R&R:

• R1: Reset — Write your independent estimate before hearing others.
• R2: Range — Force low/base/high scenarios with explicit triggers that would move you between them.
  Compare. If your post-meeting number equals the first number uttered, you’re probably anchored.

→ Finally, don’t aim for perfect certainty — aim to loop faster than confusion can set…

7) OODA Loop — How to Think While Moving.

Intro​
Plans lose to reality. Loops beat plans.

Explainer

• Conflict: Observe the heat, orient to shared values (“What do we both want kept intact?”), decide one constructive next sentence, act — then read the room again.
• Creative work: Ship a sketch, gather signal, iterate; don’t romance draft one.
• Leadership: Shorten feedback cycles so truth arrives before bravado does.
  The loop is humility in motion.

Practical Offering​
Try a 10-minute OODA:

1. Observe: What’s undeniably true right now?
2. Orient: What matters most right now?
3. Decide: One reversible move.
4. Act: Do it. Calendar the next loop.
   Repeat until momentum returns.

Closing reflection

Clear thinking is less about supreme logic and more about refusing to be hypnotized — by drama, charisma, dashboards, or first drafts. Use these models as small brakes on runaway stories. And when you catch yourself reaching for certainty, borrow Feynman’s humility: you’re rarely definitely right — just less wrong than yesterday.

Pocket prompt for readers​
Which model will you practice this week, and in what situation? (Bonus: report back with what surprised you.)

Have a great week,

Griff

P.S. Do me a solid while doing yourself a favor and answer the below: it'll make your experience of The Pocket better; promise.