Inversion thinking: turn possible failure into a better plan
Inversion thinking examines the opposite of the result you want. Ask what would make a project fail, identify causes you can influence, and turn those causes into practical safeguards. Then return to what success requires.
This is useful when a plan sounds convincing but its weak spots remain vague. A launch, a handoff, or a meeting gives you something concrete to examine. Start with a bounded project rather than trying to invert your entire working life.
In Poor Charlie’s Almanack, Charlie Munger argues for examining problems both forward and in reverse. Our exercise below applies that idea to an everyday project; it is not a method Munger prescribed step by step. Read Munger’s “Practical Thought about Practical Thought?” in the publisher’s free edition.
Define a result you can recognize
“Make the project successful” is difficult to invert usefully. Specify who should benefit and what they should be able to do.
Hypothetical project: you are creating a starter guide for new volunteers at a community workshop. The desired result is that a first-time volunteer can find their assignment, arrive with the right materials, and know whom to ask for help.
The inverted question becomes: “What would we do if we wanted a new volunteer to arrive confused and unprepared?” The deliberate reversal gives you permission to name awkward possibilities before they happen.
Move from failure cause to a check
For this invented example, the failure list might include sending instructions too late, burying assignments in a long document, and naming a contact who is unavailable during setup.
Convert each cause into something that can be checked. “Communicate better” is still vague. The table below shows our suggested next move.
| Possible failure cause | Practical safeguard | Owner and check |
|---|---|---|
| Instructions arrive after people have made travel plans. | Send the arrival details before volunteers need to plan their journey. | Coordinator: check the send date against the event schedule on Monday. |
| The assignment is hidden among general information. | Put the individual’s task, arrival time, and materials together at the top. | Guide editor: ask a new reader to locate all three on Wednesday. |
| The listed contact is busy elsewhere. | Confirm a setup contact and a backup. | Event lead: verify both people’s availability before sending. |
These are proposed checks, not evidence that the workshop will run smoothly. The reader test may reveal a different problem. Use that information to update the plan.
Choose what deserves attention
Do not turn every imagined problem into another rule. Mark each item as something you can change, something you need to investigate, or something outside your control. Prioritize plausible causes that would meaningfully spoil the intended result.
In the workshop example, you can revise the guide. You can check a contact’s availability. You cannot guarantee that no one will ever be late. A fallback arrival instruction may be more useful than an elaborate prevention plan.
Also check whether a safeguard creates a new burden. Asking volunteers to read three confirmation emails might make the original information harder to find.
A worksheet for your next project
Copy and complete this sequence for one project.
- Desired result: Who should be able to do what, and by when?
- Opposite result: What would disappointment look like to that person?
- Possible causes: Which three choices or omissions could produce it?
- Control: Which cause can I change? Which needs evidence?
- Safeguard: What specific adjustment will I make, who owns it, and when will it be checked?
- Forward action: What still has to happen for the project to be useful?
Inversion and a premortem: what is the difference?
Inversion is the broader habit of reversing a question. A premortem is a specific planning exercise: imagine that the proposed plan has already failed, then have the team generate explanations. That is how Gary Klein describes his method. Read Klein’s premortem overview.
“How could we make the handoff confusing?” is an inversion prompt. “It is next month, the handoff failed, and we are explaining why” uses a premortem frame. Either can surface possibilities. Neither makes those possibilities facts or establishes their probability.
Finish by moving forward
Avoiding confusion is only part of a useful volunteer guide. Someone still needs to assign the work, gather accurate details, and make the guide available. End the exercise with one constructive action, not just a longer list of worries.
Continue with James Clear’s inversion essay in the library.