The inversion test: what would guarantee failure?

Ask a team how to make a project succeed and you will get the plan they already had. Ask the same team what would guarantee it fails and the room changes. People say things they have been sitting on.

That is inversion, and it is the cheapest reasoning tool there is. It costs one question and about twenty minutes.

Why it works

Success has many paths and they are hard to rank. Failure has a few, and they are specific. People find it much easier to name a concrete disaster than an abstract advantage, so you get better information out of the same room.

It also gives people permission. Saying "this will fail if we do not fix hiring" is a contribution. Saying "I think our hiring is bad" is a complaint. Same information, and only one of them gets said out loud.

Running it properly

• Ask everyone to write privately first. Spoken-first kills the answers you most need.

• Set the frame in the past tense: it is a year from now and this failed.

• Collect every cause before discussing any of them.

• Sort by whether you could see it coming, not by how likely it feels.

Inversion will not tell you what to do. It tells you what you have been declining to look at, which is more useful at the start of a project than any forecast.