Inversion Thinking: Solve Problems Backwards to Win

Inversion thinking is the practice of solving a problem backwards — instead of asking how to achieve what you want, asking what would guarantee failure, and then systematically avoiding that.

It is one of the few mental models that reliably produces different answers from the same information. Most thinking runs forward: here is the goal, what are the steps. Inversion turns the problem around and asks what would have to happen for this to go badly. The answers are usually more specific, more actionable, and considerably harder to argue with.

Where inversion thinking comes from

The instruction belongs to the nineteenth-century mathematician Carl Gustav Jacobi, who advised students facing intractable proofs to invert — man muss immer umkehren, one must always invert. Difficult problems in mathematics, he noticed, often become tractable when expressed backwards.

Charlie Munger took the idea out of mathematics and made it a decision-making discipline. His version was blunter: rather than trying to be brilliant, work out what would produce disaster and avoid it. He argued repeatedly that consistently avoiding stupidity beats consistently seeking intelligence, partly because failure modes are fewer and more predictable than success modes, and partly because the mistakes that destroy people are usually well known in advance.

That asymmetry is the whole case. There are countless ways to build a good business and a very short list of ways to reliably kill one. The short list is the one you can actually work with.

There are countless ways to build a good business and a very short list of ways to reliably kill one. The short list is the one you can actually work with.

How inversion thinking works

The technique has two distinct modes, and they are used for different problems.

Mode one: subtract the causes of failure. Instead of “how do we build a great team”, ask “what would guarantee this team fails?” The answers arrive immediately and concretely — unclear ownership, no feedback, tolerating a brilliant bully, promoting on tenure, hiring in a rush. That list is a to-do list in negative form, and it is far more specific than anything the forward question produces.

Mode two: reverse the goal to expose assumptions. Instead of “how do we increase retention”, ask “how would we drive our best customers away as efficiently as possible?” This surfaces things the forward question hides, because the mind is more honest about damage than about improvement. Teams that struggle to name five retention initiatives can name fifteen ways to annoy a customer in about four minutes.

The second mode works for a reason worth understanding: forward questions invite aspiration, and aspiration is vague. Backward questions invite recognition, and people are extremely good at recognising problems they have already seen.

Forward questions invite aspiration, and aspiration is vague. Backward questions invite recognition — and people are extremely good at recognising problems they have already seen.

Inversion thinking: worked examples

Strategy. Forward: how do we win this market? Inverted: what would make us irrelevant in five years? The second question surfaces the substitution risk, the channel dependency, and the cost structure — none of which appear in a growth plan.

Product. Forward: what features should we build? Inverted: what would make someone abandon this product in week one? Usually onboarding friction, not missing features. The roadmap changes shape entirely.

Personal decisions. Forward: how do I have a successful career? Inverted: what reliably derails careers? A short, uncomfortable, actionable list — burning relationships, stopping learning, staying too long somewhere with no growth, mistaking activity for progress.

Communication. Forward: how do I make this presentation persuasive? Inverted: what would make this audience stop listening? Almost always length, jargon, and burying the point — which no amount of forward polish fixes.

Inversion thinking and the pre-mortem

The relationship is worth being precise about, because these are often conflated.

Inversion thinking is the general principle: reason from the failure end.

A pre-mortem is one structured application of it — assume the project has already failed, then work backwards to explain why. It is inversion with a fixed format, a specific moment in the project lifecycle, and a group process attached.

You can use inversion thinking without running a pre-mortem, in about thirty seconds, on any decision. The pre-mortem is what you do when the decision is large enough to justify assembling people and formalising the exercise.

When inversion thinking is most useful

When the forward answer is generic. If your plan could belong to any company in your industry, invert. Failure modes are specific in a way that success plans are not.
When everyone agrees. Consensus usually means the forward case has been examined and the failure case has not.
When the goal is protection rather than gain. Anything involving risk, safety, reputation, compliance, or survival is naturally an inversion thinking problem.
When you are stuck. A blocked forward question is often an unblocked backward one.

The danger: how inversion thinking gets misused

Avoiding failure is not achieving success. This is the central error. Removing every cause of failure leaves you with something that does not fail — which is not the same as something that wins. A restaurant that eliminates every reason to dislike it is not thereby a restaurant anyone loves. Inversion thinking is excellent at establishing a floor and largely useless at raising a ceiling, and treating it as a complete strategy produces organisations that are competent, defensible, and completely unremarkable.

Defensive drift. Teams that adopt this as a habit gradually become risk-management functions. Every proposal is met with a failure analysis, the failure analysis is always correct, and over time the organisation optimises exclusively for not losing. This is how incumbents die — not through any single bad decision, but through a decision process that only ever asks what could go wrong.

Confusing the invertible with the non-invertible. Some problems genuinely have symmetric answers, and many do not. “What would make this marriage fail” is useful. “What would make this novel bad” produces a competent, forgettable novel. Creative work in particular resists inversion thinking, because the absence of flaws is not what makes it good.

Failure-mode theatre. Listing what could go wrong feels like rigour and costs nothing. Unless each identified failure mode gets an owner, a mitigation, and a date, the exercise is a well-attended meeting that changes nothing.

Negativity contagion. Sustained inversion thinking is psychologically corrosive on a team if it is never paired with the forward question. The people who habitually run the failure analysis acquire a reputation for pessimism, which eventually causes them to be excluded from the conversations where it would matter most.

How to practise inversion thinking

Take any decision you are about to make and spend five minutes on one question: if this goes badly, what will the explanation be?

Write the answers down. Cross out the ones you cannot influence. For each one that remains, name what you would have to do differently and who owns it.

Then — and this is the step that keeps the method honest — return to the forward question and ask what would make this genuinely good, not merely un-bad. Inversion tells you what to remove. It cannot tell you what to build. Used alone it produces safety; used alongside forward reasoning it produces judgment.

Inversion tells you what to remove. It cannot tell you what to build.

Inversion Thinking