All insights

Invert, always invert — many problems are best solved backward

Thinking in reverse is one of the most powerful problem-solving techniques: instead of asking what you want, ask what you want to avoid, then don't do that

Charlie Munger — Poor Charlie's Almanack, Talk 4: Practical Thought About Practical Thought (pp. 299-305) · · 8 connections

Munger lists “thinking in reverse” as one of his five most powerful problem-solving techniques, citing the algebraist Carl Jacobi who “so often said, ‘Invert, always invert.’” Many problems that seem intractable when approached forward become obvious when inverted. The Pythagoreans proved the square root of two was irrational by thinking in reverse. The rustic “wanted to know where he was going to die so that he’d never go there.”

In the Coca-Cola case study, Munger demonstrates inversion practically: after constructing a plan to reach $2 trillion forward, he reverses direction with “What must we avoid because we don’t want it?” The answers are immediately clear: avoid aftertaste that stops consumption, lose the brand name, fail on distribution, or let a competitor copy the formula before building an unassailable lead. These “avoid” answers shaped strategy more precisely than the forward plan alone could. Darwin used the same approach, “spending much of his long life thinking in reverse as he tried to disprove his own hardest-won and best-loved ideas.” Einstein ranked self-criticism alongside curiosity, concentration, and perseverance as the four causes of his achievement.

The technique connects to First conclusions become nearly permanent — the brain resists its own updates — inversion is a direct antidote to Inconsistency-Avoidance Tendency, because it forces you to actively seek what could disprove your first conclusion. It also connects to A latticework of mental models beats isolated facts for real understanding — inversion is one of the “mere handful” of models that “carry very heavy freight” across all disciplines. In autonomous systems, inversion manifests as the guard command pattern: Every optimization has a shadow regression — guard commands make the shadow visible — instead of only asking “did the metric improve?”, also ask “what could have gotten worse?” In organizational decision-making, Ask for 'no' not 'yes' — default-proceed framing accelerates organizational decisions applies inversion to the approval process — instead of asking “how do we get approval faster?”, invert to “how do we remove the need for approval?” and frame proposals as default-proceed unless objected to.