Munger's core operating modelsPart I

Checklists

Pre-commit to running through known failure modes. The disciplined pilot beats the talented improviser under stress.

Atul Gawande wrote a book on this (The Checklist Manifesto). Munger has been preaching it for decades. The idea: in any field where the cost of forgetting a step is high, written checklists outperform memory and improvisation, even for experts.

Pilots use them. Surgeons use them. Industrial operators use them. The pattern that keeps appearing: someone with 20 years of experience still misses an obvious item once a year. The checklist catches it.

The mechanism isn't that the checklist is smarter than the expert. It's that humans are predictably bad at remembering everything under stress, in a rush, or when distracted. A piece of paper isn't.

For operators, the right places for checklists are:

• Tasks that get done occasionally but rarely (annual reviews, year-end closes, board meetings, hiring decisions)
• High-stakes tasks where a single miss is expensive (M&A diligence, regulatory filings, major launches)
• Tasks done across many people who need to do them similarly (sales calls, support tickets, code reviews)

The wrong places:

• Genuinely creative or novel work, where the checklist constrains the thinking
• Trivial tasks where the overhead of the checklist exceeds the cost of mistakes

A good checklist is short. It captures the few items most likely to be forgotten under stress, not every step. The checklist for a B2B sales call has maybe 5 items, not 50. The checklist for a deal close has maybe 10 items, not 100. If it's longer, people stop using it.

Examples in the wild