a builder's codex
codex · operators · Annie Duke · ins_make-intuition-explicit

Force intuitions into explicit predictions so you can find out where you are wrong

By Annie Duke · Author, Thinking in Bets and Quit; former WSOP poker champion · 2026-04-28 · podcast · Decision quality, explicit thinking, feedback loops

Tier B · TL;DR
Force intuitions into explicit predictions so you can find out where you are wrong

Claim

Intuition is useful, but if it stays implicit you never get feedback on when it fails. Force every important intuition into an explicit, falsifiable prediction with a number and a horizon — then check it.

Mechanism

Implicit intuition is unfalsifiable: any outcome can be retrofitted into "I knew that." Explicit predictions are anchors. They force the intuition into a shape that can be wrong, which is the only shape that can teach. Over time, calibration emerges — the operator learns where their gut is sharp and where it is biased. Without the explicit step, both gains and losses go unrecorded.

Conditions

Holds when:

Fails when:

Evidence

"I think this positioning will resonate" is implicit. Explicit: "We expect 15% CTR on this LP variant, and we'll know we're wrong if it's <8%."

Annie's framing: explicitness forces specificity, specificity enables falsification.

— Annie Duke on Lenny's Podcast, 2026-04-28

Signals

Counter-evidence

Forcing every intuition into a number can produce false precision and crowd out genuine ambiguity-tolerance. Some operators reason better by analogy and metaphor than by quantified prediction.

Cross-references

Open the interactive view → View original source → Markdown source →