What needs to be true?
Before committing to a direction, break it into the conditions it needs in order to work, and test those first. Don't debate the approach. Competing analogies never settle, because each side has a story where theirs worked. Competing positions measured against the same preconditions always do. This is the question I ask before any of the others.
- What it rejects
- Reasoning by analogy: it worked there, so it will work here. It is fast, it feels safe, and it is how most strategy decisions actually get made.
- When it is wrong
- When speed matters more than being right, and being wrong is cheap and reversible. A quick call based on an analogy, plus a fast feedback loop, beats a full breakdown that slows the team down. This principle is overhead when the downside is small.
- Where I used it
- At Reejig, the case for a self-serve growth motion was that it had worked at Atlassian. I set out the three conditions self-serve needs and showed where we stood on each. We met none, and the debate ended. Work OS: Strategy
- Where it sits
- Closest to Roger Martin's "what would have to be true?" in Playing to Win, and first-principles reasoning over reasoning by analogy. Martin uses it to stress-test a finished strategy. I use it in the middle of a disagreement, to turn "should we do this?" into "what would this need?" and then check our situation against the answer.