Skip to content
product-skill
product-skill/ Field Guide/ Decision heuristics Decision-making

Decision Heuristics & Anti-Patterns

Name the rule before you argue the case — and classify the door before you decide.

Recall these by name; don't re-derive them each time. The reversibility of the decision sets how much rigor it earns — everything else follows from that read.

Type-2 · reversible

Two-way door

Decide fast, iterate. Most decisions are reversible — the cost of waiting exceeds the cost of a wrong turn you can undo.

Type-1 · one-way

One-way door

Slow down. Pre-mortem, gather diverse input, apply regret-minimization. Irreversible bets earn the extra rigor.

Reversibility is the rigor dial — the first read on any decision.

Above the fold

The three moves that carry the judgment.

01

Classify the door first.

Type-2 (reversible): decide fast & iterate. Type-1 (one-way door): slow down, pre-mortem, diverse input. The read sets the rigor.

02

Price the opportunity cost.

“Every yes is a no to something else” (Doshi). Cost the alternative you're not doing — the real price of a choice is what it displaces.

03

Check whether you're in the build trap.

If success means features shipped rather than outcomes moved, the process is the problem — not the backlog (Perri).

Decision heuristics

Three to recall by name. Five to keep in full.

The dashed cards are apply-by-name pointers — canon you invoke, not re-teach. The solid cards carry the judgment and stay in full.

Apply by name · canon

Regret-minimization

canon

Reserve it for big one-way bets only — project yourself forward and choose the path you'll least regret. Overkill for reversible calls.

Reversibility

canon

Type-2 (reversible) — decide fast & iterate. Type-1 (one-way door) — slow down, pre-mortem, diverse input. The classification is the whole heuristic.

Opportunity cost

Doshi

Price the cost of not doing the alternative. “Every yes is a no to something else.”

Keep in full · these carry the judgment

Build-trap detector

Perri

You're trapped if any of these hold:

  • success = features shipped not outcomes
  • roadmap = dated feature-list not problems
  • PMs are order-takers
  • no discovery process
  • nobody talks to customers regularly

Value-exchange check

Perri

Every decision must create customer value AND capture business value. One-sided is not sustainable — a delight that never monetizes and a monetization that never delights both decay.

Minimum Lovable > Minimum Viable

Rachitsky

Fully resolve a subset of the struggle. A narrow slice that delights beats a broad slice that doesn't.

Sharp-problem test

the Udezues

Does it compress a painful workflow and trigger a visceral “I need this now”? A multi-signal read, not a checklist — a weak reaction means the problem isn't sharp enough to fund.

≥3× Zone of Benefit

the Udezues

To overcome switching cost and inertia, be ~3× better than the status quo on the one dimension that matters. Incremental wins don't move people.

Directional

Anti-patterns · the tell, and the fix

Thirteen ways it goes wrong. Thirteen ways back.

Eight classic failure modes and five the AI era added. Each pairs the tell — how you notice it — with the fix that pulls you out.

Classic 8

Feature Factory

Tell

Output-measured — success is count of features shipped.

Fix

A problem + outcome metric per item.

HiPPOhighest-paid person's opinion

Tell

authority wins

Fix

frameworks + experiments

Analysis paralysis

Tell

Endless research, no decision.

Fix

Time-boxed discovery to a “sufficient-confidence” bar.

Solution-first

Tell

Spec written before the problem is framed.

Fix

A JTBD problem statement first.

Stakeholder appeasement

Tell

Yes to all requests.

Fix

Transparent prioritization + a published “not doing” list.

Metric vanity

Tell

Signups/downloads as the headline.

Fix

North Star + activation/retention.

Premature scaling

Tell

Scaling before product-market fit.

Fix

Fix retention first.

Ivory-tower PM

Tell

Data only — no direct customer contact.

Fix

Weekly customer contact.

AI-era 5 · new failure modes

Shiny-objectAI-era

Tell

Chasing AI because it's AI.

Fix

Demand a sharp problem + an eval plan before building. A demo is not a product.

CEO/exec-bypassAI-era

Tell

Leadership drops AI features over the PM.

Fix

Surface the opportunity cost, re-anchor the decision on the problem. (Udezue)

Demo-theaterAI-era

Tell

A happy-path demo treated as shippable.

Fix

Gate on eval pass-rate + real traces, not the rehearsed path.

Build-every-ideaAI-era

Tell

Cheap generation floods the backlog.

Fix

Raise the bar, not the throughput. Most ideas still shouldn't ship.

Shipping-velocity-as-vanityAI-era

Tell

Ship-count as the headline metric.

Fix

Learning velocity > shipping velocity. Measure outcomes, not output.

Try it

Tag your own decision.

The blind-spot tagger, live: match the ritual to the stakes — the full five-point check for irreversible calls, a one-line tag for routine ones. It writes the decision tag for you.

The blind-spot tagger needs JavaScript to run. Run it on the Tools page.

All 13 tools →