Inversion: the mental model, explained

Cerno is a private AI boardroom that runs consequential decisions through a structured process and returns an Executive Decision Brief. Inversion is one of the reasoning lenses it applies — here it is on its own, with a second worked example and the ways it goes wrong.

What is inversion?

Most people attack a goal head-on: list the ways to win, pick one. Inversion flips it. You ask what would reliably ruin the outcome, then treat avoiding each of those as a requirement. "How do we build a great team?" becomes "what would guarantee a terrible team?" — no clarity of roles, no feedback, tolerating brilliant jerks — and now you have a concrete list to avoid.

The value is that failure modes are often more obvious and more agreed-upon than success factors. Ask five people how to make a business succeed and you get five theories. Ask them what would guarantee it fails and they'll largely agree: run out of cash, sell something nobody wants, hire badly, ignore customers. Avoiding stupidity is a lower bar than seeking brilliance, and it compounds.

Why it works

Failure is more concrete than success. "A successful launch" is an abstraction. "We launched with a checkout that didn't work on phones" is a scene. Inverted questions produce scenes, and scenes can be checked against a plan.

It sidesteps optimism. Asked how to succeed, people list the things they're already planning to do — the exercise confirms the plan. Asked what would guarantee failure, they have to think about the plan's absences, which is where the trouble usually is.

Losses are more motivating than gains. People will work harder to avoid a named disaster than to reach a vague good outcome. A rule phrased as "never let a client wait more than a day for a reply" gets followed; "provide excellent service" gets nodded at.

When should you use it?

Reach for inversion when a problem feels vague or the path to success is genuinely uncertain, but the ways to fail are easier to name. It pairs naturally with big, open-ended calls — strategy, investments, hiring — where "what must we not do?" is a sharper question than "what's the best move?"

It is weaker in two situations. When the obvious failure modes are already avoided, inversion produces a list you've already ticked, and you need a different tool. And when you're choosing between several options that are all safe, inversion can't rank them — it filters, it doesn't select.

How to use inversion in 5 steps

1. ›State the goal plainly. "A successful product launch." "A first hire who's still here and useful in a year."
2. ›Invert it. "What would guarantee a failed launch?" "What would guarantee this hire is gone or useless in a year?"
3. ›List the failure guarantees. Be specific and unsparing — no audience, no message, shipping half-built, no way to measure it. Aim for the failures that would be your fault, not the world's.
4. ›Convert each to a rule. Every guaranteed-failure becomes a must-avoid or a precondition: "we do not launch without a way to measure the first week."
5. ›Check your plan against the rules. Anything that trips one of them is a red flag to fix before you commit. Anything that survives all of them is a plan you can proceed with — though inversion won't tell you it's the best plan.

Worked example

Weighing an investment, inversion asks what would make it a clear loss — and the brief records the guardrails:

A second example: the first hire

A sole trader is about to hire their first employee. The forward question — "how do I make this hire a success?" — produces the usual list: write a good job ad, interview well, pay fairly. All true, none of it sharp.

Inverted: what would guarantee that, a year from now, this person has left or I wish they had?

• ›I hired whoever was available soonest, because I was drowning.
• ›I never wrote down what the job actually is, so we disagreed about it from week two.
• ›I kept doing the work myself because handing it over felt slower than doing it.
• ›They had nobody to ask when I was out, and no way to make a decision without me.
• ›I set no point at which we'd both check whether it was working.

Each of those becomes a rule. Do not hire before the role is written down. Do not hire while the only criterion is availability. Block the first month's handover in the diary, and treat doing it yourself as a failure, not a shortcut. Agree a three-month check-in on the day they start.

Nothing on that list is clever. All of it is the difference between a first hire that works and one that quietly doesn't, and none of it came from asking how to succeed.

Common mistakes

Listing only external failures. "The market could shrink." "A big competitor could enter." These are real but you can't avoid them, so they generate no rules. Inversion earns its keep on the failures that would be your doing — those are the ones a rule can prevent.

Stopping at avoidance. Ruling out every guaranteed failure leaves you with the set of acceptable plans, not a choice. People sometimes treat the survivor of inversion as "the answer" when it's merely "not wrong". Pick among the survivors with a different tool — expected outcomes, reversibility, or plain judgement.

Inverting the wrong goal. "What would guarantee we don't hit the sales target?" produces a list about sales. If the real goal was "a business I still want to run in five years", the inversion needed to start there. State the goal you actually hold, not the one on the dashboard.

Treating the rules as guarantees. Avoiding every named failure mode does not make success certain — it removes the failures you could see. The unnamed ones are still out there, which is why inversion pairs so well with a pre-mortem on the specific plan you end up with.

Inversion, pre-mortem, second-order: which one when

They overlap, and people conflate them. A rough division of labour:

• ›Inversion (this guide) to define the problem: what must this plan not do? Use it early, while the plan is still forming.
• ›Pre-mortem to stress-test a specific plan: assume this exact plan failed — why? Use it just before committing.
• ›Second-order thinking to trace consequences: if this plan works, what does it set in motion? Use it on any decision other people will react to.

A consequential decision can reasonably get all three. Cerno's advisors apply them from different seats — the Investor inverts, the Risk Officer runs the pre-mortem, the Futurist traces the second order — which is one reason a board reaches a different answer from a single voice.

Which Cerno advisor uses this?