What is inversion thinking?
Inversion is a way of solving a problem from the far end. Normally we look at a goal and search for a route to it. With inversion you picture the failure first and list the reasons that caused it.
The logic is simple: a recipe for success is hard to find, while the causes of failure are easier and more precise to name. There is never one correct road — there are dozens. But the things that knock you off the road usually fit on one hand.
The idea is old. The mathematician Carl Jacobi advised attacking hard problems by inverting them. Charlie Munger carried the habit into investing and management: "All I want to know is where I'm going to die, so I'll never go there."
Why the negative question gives a sharper answer
A positive question produces many vague answers. The inverted question produces a short, specific list. And removing a list is practical work — you can start on it today.
"How do I save money?" leads to hundreds of pieces of advice: investing, side income, budgeting apps, personal finance books. All true, none of it tells you where to begin.
"What will leave me broke?" returns about five answers:
- 1. Unplanned purchases
- 2. Debt
- 3. No emergency buffer
- 4. Depending on a single income source
- 5. Not tracking expenses
Closing those five is already a large result. Notice that every item converts straight into a task, while "start investing" is a topic, not a task. That is the real power of the inverted question: it moves you from topic to action.
Inversion is not pessimism
The two get confused because both name bad outcomes. The difference is what follows: a pessimist lists the problems and stops; someone using inversion lists them and then closes each one.
The list is a starting point, not a conclusion. If nothing on your page has a counter-action next to it, you are not inverting — you are worrying. The test is easy: after reading the list, do you have a specific thing to do tomorrow?
How to apply inversion in 5 steps
- 01
Write the goal in one sentence
Inversion does not work on vague goals. Not "get healthy" but "train three times a week until autumn". To know what could break something, you first need to know exactly what you are building.
- 02
List everything that would ruin it
Give yourself five to ten minutes and write without filtering. External causes count (work schedule, family, money) and so do internal ones (procrastination, forgetting, over-promising). Do not cross anything out yet.
- 03
Sort the list by likelihood and damage
Two questions per item: how likely is this, and how badly would it hurt? The items that score high on both are your real opponents. There are usually no more than three to five of them.
- 04
Write one concrete action against each cause
"I will forget" becomes a reminder. "No energy in the evening" becomes a morning session. "My training partner drops out" becomes a solo version of the workout. Removing the list is the first part of the plan, not an add-on.
- 05
Reread the list once a week
New obstacles show up along the way and old ones get closed. During your weekly review, walk the list: which items are still alive? Five minutes of this keeps a goal from quietly dying halfway.
Examples: the usual question vs the inverted one
The same goal, asked two ways. The answer in the right column is always more concrete and gets done sooner.
| Goal | Usual question | Inverted question and first step |
|---|---|---|
| Savings | How do I save money? | What leaves me broke? → move the buffer out on payday, before spending |
| Training | How do I train consistently? | What stops the training? → evening fatigue → move it to the morning |
| Exams | How do I prepare well? | What makes me fail? → leaving it to the last day → spread topics across dates |
| Project | How do I make this project succeed? | Why would it fail? → unclear requirements → written agreement in week one |
The last row has a team name: the premortem. Before a project starts, the team sits down and answers "imagine this failed completely — why?" (method described at Harvard Business Review). Mistakes spoken out loud in advance mostly stop happening.
Where the method breaks down
I have used it badly more than once: written the list, looked at it, and then never started the work at all. Three limits worth keeping in mind:
- Early idea stage — when you are still inventing something, a constraint list arrives too soon and smothers it. Write the idea down first, invert afterwards.
- Long lists — twenty causes is anxiety, not a plan. Keep the three to five most likely and most damaging.
- Lists without actions — a cause with no counter-action just sits there and drains motivation. One item, one task — do not break that rule.
Running an inverted plan in Unumly
A notebook works fine for this, with one catch: the failure list gets written once and never opened again. Reopening it is where the value is.
Here is how I keep it in Unumly: the goal goes into Maqsad (goals), and the steps under it are not vague intentions but counter-actions — "move the buffer out on payday", "shift training to 07:00". They appear in Bugun (today) as ordinary tasks, and the Telegram bot pings when one is due. The list does not stay on paper; it turns into a day.
For bigger work, open a document in Loyiha (projects) and keep the premortem there. The interface is in Uzbek for now, but the sections are simple: Bugun — today, Maqsad — goals, Kalendar — calendar.
Inversion sits on top of normal planning rather than replacing it. Once the list exists, use time blocking or a plain daily plan to give the counter-actions a slot. The general foundations are in the time management guide.
Frequently asked questions
- What is inversion thinking?
- Inversion thinking means solving a problem from its end — the failure side. Instead of asking "how do I achieve this?", you ask "what would stop me from achieving this?", list the answers, and start the plan by removing that list.
- How is inversion different from pessimism?
- A pessimist lists the problems and stops there. Someone thinking in inversion writes the same list, then attaches a counter-action to every item. The difference is not the mood, it is what happens to the list.
- Who popularised the inversion model?
- The principle "invert, always invert" (man muss immer umkehren) is attributed to the German mathematician Carl Jacobi. In business and decision-making it was popularised by Charlie Munger, who advised starting any analysis with the question "where could I be wrong?".
- What is a premortem?
- A premortem is an exercise where, before a project starts, the team imagines it has failed completely and explains why. It was proposed by psychologist Gary Klein. It is inversion done as a group: mistakes get said out loud before they happen.
- When should you not use inversion?
- During idea generation and at the start of creative work — a list of constraints arrives too early and shuts down thinking. Also, once a list grows past fifteen or twenty items it stops being a plan and becomes anxiety. Keep the three to five that matter.
- What about causes outside my control?
- Mark them separately. Those get a fallback rather than a counter-action: "internet goes down — an offline version of the work", "client delays — a second source of tasks". That still closes the item.
- How do I fit inversion into a daily plan?
- When you set a new goal, make the failure list your first task. Then turn each counter-action into its own task with a time on it. In Unumly those simply live as tasks inside the goal.