Poor Charlie's Almanack
There is an old two-part rule that often works wonders in business, science, and elsewhere: 1. Take a simple, basic idea and 2. Take it very seriously.
Essence (why this landed for me)
This is a manual for clearer judgment. The latticework idea turns scattered knowledge into a working kit: collect reliable models, cross-check them, and apply with calm. It trades hot takes for process. The rules are simple on purpose so they hold under pressure. It feels usable across product, design, and engineering.
Insights (mapped to mental models)
Takeaways grouped by mental models, with a short action you can use now.
Build a latticework, not a bookshelf.
Invert to see the pitfalls early.
Stay inside your circle of competence.
When incentives change, behavior changes.
Seek simple, durable explanations.
Second-order effects matter more than first wins.
Use checklists to de-bias fast.
Demand a margin of safety.
Avoid siren songs of authority.
Use base rates before narratives.
Favor patience and few big decisions.
Design systems that learn, not just perform.
Guard against envy, hubris, and momentum.
Think in opportunity cost at all times.
Use redundancy where failure is ruin.
Prefer incentives aligned with reality.
Use multi-track analysis to avoid tunnel vision.
Reduce complexity until you can explain it plainly.
Keep a not-doing list to protect focus.
Seek disconfirming evidence before you believe the plan.
Take a simple idea and take it seriously.
Be consistently not stupid before trying to be brilliant.
Ethics as advantage: reputation compounds.
Absorption Notes (short essay)
Judgment improves when the work begins with base rates and ends with a checklist. Start from simple, sturdy models and link a few before acting. Keep the circle of competence written so scope stays honest. Map incentives for each actor and adjust when the map reveals pressure points. If a decision could be ruin, add a margin and test there first. Pose the inversion early to surface failure modes, then review second-order effects to catch delayed costs. Look for disconfirming evidence before you commit. Compare three paths before choosing one. Prefer rare, high-quality bets over constant motion and write the opportunity cost beside the choice. Close the loop so outcomes teach the next pass. Plain language is the test. Simple moves, steady rhythm.
Reflection Prompts (product × design × engineering)
Questions to apply the ideas across projects. Pick one or two and use them today.
Invert first
What would make this fail, and how do I block it
InversionUse before committing a plan.
Circle check
Is this inside my competence or am I stretching into fog
Circle of CompetenceQuick boundary check.
Base rates
What does the reference class suggest about likely outcomes
Base RatesStart with priors, then adjust.
Incentives map
How will each actor be paid or praised, really
IncentivesAssume behavior follows rewards.
Second order
What happens after the first win, at 3 and 12 months
Second-Order ThinkingWrite downstream effects.
Margin
Where is ruin possible and what buffer blocks it
Margin of SafetyProtect the critical path.
Options
What is the best alternative use of this time or capital
Opportunity CostState the next best.
Checklist
Which misjudgments should I scan for before I ship
ChecklistsRun the list quickly.
Explain it
Can I state this plan in one simple paragraph
SimplicityPlain words, no jargon.
Disconfirm
What evidence would make me change my mind right now
DisconfirmationHunt for the counter.