Most stuck decisions aren’t stuck on analysis. They’re stuck because the options are vague, the criteria are unstated, and the two are being weighed in your head at the same time. A map fixes the first two problems and a table fixes the third, which is the whole method: map to find the options and what matters, then leave the map to compare them.
Trying to do the comparison inside the diagram is where mind-mapping a decision usually goes wrong.
Step 1: Write the decision as a question with a deadline
In the centre, one sentence: “Do we hire a second engineer before March, or not?”
Two properties matter. It’s a question, not a topic. “Hiring” is a subject area and cannot be resolved. And it has a date, which converts “should we” into something with a cost for waiting.
If you can’t write the question, that’s the finding: you have a situation, not a decision, and the first branch is “what would have to be true for this to become a decision”.
Step 2: Find more options than you have
Take one branch called Options and be deliberately generous. Almost every stuck decision is stuck as a binary, and binaries are usually an artefact of how the question got asked.
Force these four onto the branch, every time:
- Do nothing, explicitly. Sometimes it wins; it should always be on the list, with its costs written down rather than assumed to be zero.
- A smaller version. The reversible, cheap, two-week version of the big option. This one wins far more often than it gets considered.
- Later. Not a dodge, but a real option with a date and a trigger attached.
- The opposite. If you’re deciding whether to add something, put removing something on the list.
This is the part a mind map is better at than a list, because siblings sit next to each other and a thin Options branch is visibly thin.
Step 3: Name the criteria, before you look at the options
A second branch called What matters, filled in without reference to any particular option. Order matters here: criteria written after you have a favourite are criteria that describe your favourite.
Cost, time, reversibility, who it affects, what it forecloses, how it feels in six months. Four to six is plenty.
Then do the one thing that makes the rest of this work: mark which two are decisive. Not ranked, not weighted; just circle two. Most decisions are actually made on two criteria, and the other four are there to make the process look thorough. Knowing which two is what lets you finish.
Step 4: Under each option, the honest branches
For each option, three children:
- Consequences — what actually happens, not what you hope.
- What has to be true for this to be the right call. These are assumptions, and they’re testable, which makes this the most useful branch on the map.
- Cost of being wrong — and crucially, whether it’s reversible. A cheap mistake you can undo in a week is a different category of decision from one you cannot, and treating them the same is the most common decision error there is.
Step 5: Leave the map, build the table
Now stop drawing. Put the options down the rows and your two decisive criteria across the columns, and fill it in.
The map was for generating and organising; a table is for comparing, because comparison needs the same attributes lined up in the same order. Diagrams are bad at that, and this is exactly the case where a table beats a picture.
The table usually produces one of three outcomes:
- A clear winner. Take it. The map’s job was to make sure the option was on the list at all.
- A tie. A tie means the criteria don’t separate the options, so pick the one that is easier to reverse and move on. Time spent breaking a genuine tie is time spent on something the criteria said doesn’t matter.
- A missing fact. The best outcome, and the most common. You now know the single thing you need to find out, which is a much smaller task than the decision was.
Step 6: Write down why, and what would change your mind
Two topics, sixty seconds, and they’re what makes the map worth keeping:
- The decision, and the two reasons.
- What would change your mind — a specific, observable event. “If churn is still above 4% in March, revisit.”
The second one is the difference between a decision you can revise and a position you have to defend. Six months on, you’ll have forgotten which facts you actually had, and the map is the record. Export it with the write-up if anyone else has to live with the outcome.
When not to use a map for this
Reversible and cheap. Just do it. The mapping costs more than the mistake.
Decisions with real numbers. Pricing, budgets, anything with a spreadsheet underneath. Model it; a diagram of a calculation is a worse calculation.
Someone else’s decision. Map the inputs you owe them, not the choice. A map of a decision you don’t own reads as an attempt to make it for them.
Genuinely stuck between two goods. No framework resolves a values conflict. The map at least shows you that’s what it is, which is more than another hour of thinking about it will do.