◀ Course contents Part 3 · Module 3-05

Mind Maps

Think in branches, not bullet points

Some problems are too tangled for a linear list. A mind map starts from one central idea and lets you branch outward freely, mirroring how ideas actually associate in your head, useful for brainstorms, meeting notes, and untangling a fuzzy problem space.

Ready?

1

A Radial Way to Think

A mind map puts a central topic in the middle and grows branches outward, each branch carrying its own sub-branches. That is the entire mechanic, and the reason it works is what it does not ask you to do.

A list forces two decisions at once: what belongs, and in what order. The second one is the expensive one, because it arrives before you have collected enough to rank anything sensibly.

The radial layout also mirrors how association actually works. One idea suggests a neighbour, which suggests another, and branches grow at different rates without any of that meaning anything about importance.

This makes mind maps a tool for the module when a problem has no shape yet. Once it has a shape, a mind map becomes the wrong instrument — you want a tree, a funnel or a table, all of which assume the structure you were still looking for.

A mind map is radial, not linear A central topic with five branches radiating outward, each carrying its own sub-points. Structure grows outward from the middle rather than downward from the top. Churn is up too slow missing feature Product Pricing renewal shock Onboarding no first value Support slow replies Competitor cheaper tier
Nothing here is first. Written as a list, “Product” would have to go above “Pricing” and somebody would have to defend that — and the defending would start before anyone had finished collecting, which is the one thing this stage cannot afford.

Everyday example, a subway map, not a train schedule

A train schedule is linear: stop 1, then 2, then 3. A subway map is radial: lines branch out from hubs, and you can see how far-apart stations relate without following one strict sequence. A mind map does for ideas what a subway map does for stations.

The list that forced a decision too early

A team opened a churn investigation with a numbered list, and the numbering became a ranking within minutes — the argument moved to what belonged at the top before anyone had finished collecting causes. Redrawn as a radial map, the same session produced eleven branches and no ranking, and the ranking that came later had more to choose from.

Quick check

What makes a mind map different from a simple bulleted list?

2

How to Build a Mind Map

Building one is quick, and a few habits are the difference between a useful map and a decorated list.

Put the topic in the centre as a question rather than a noun — “why is churn up?” rather than “churn”. Draw main branches for the broad categories, then let each grow its own twigs. Use short phrases, two or three words, because long text makes branches hard to scan and slows the association down.

Do not stop to organise. If something does not fit any branch, start a new one; if a branch turns out to be wrong, it costs nothing. Organising mid-flow is judgement entering the room, with the same effect it has in ideation.

That only works because nobody was asked to rank while they were still collecting. The branch weight is information precisely because it emerged rather than being assigned — and a map where someone decided the branches in advance tells you only what they already believed.

1

Centre it on a question

“Why is churn up?”, not “churn”. A noun invites a taxonomy; a question invites answers.

2

Draw broad branches

The obvious categories first. Two or three words each — long text makes a branch hard to scan and slows the association down.

3

Grow twigs, do not organise

If something fits nowhere, start a new branch; if a branch turns out wrong, it cost nothing. Organising mid-flow is judgement entering the room.

4

Read the weights afterwards

One branch with a single twig and another with fourteen is a finding — but only because nobody was ranking while they were still collecting.

Keep each branch to a keyword or short phrase, full sentences kill the associative speed that makes mind maps useful.

Building one without pre-judging Four steps: put the topic in the centre as a question, draw broad branches, grow twigs without organising, and only afterwards read the branch weights. 1 Centre = a question "why is churn up?" 2 Broad branches the obvious 3 Grow twigs do not stop to judge 4 Read the weights after, not during
Step four is deliberately last. Read the weights during step three and you get the map somebody expected — branches sized by what the room already believed, which is the one thing the exercise cannot tell you and the one thing it will happily appear to.

Everyday example

Planning a wedding on a single sheet: the couple in the middle, then venue, food, guests, music radiating out, each growing its own twigs. You never have to decide whether "cake" belongs above or below "seating plan", which is the entire advantage over a list.

Branches before order

A product review mapped onto five branches in twenty minutes. Two branches had a single twig each and were quietly dropped; one had fourteen and became the next quarter. The structure had done the prioritising, but only because nobody had been asked to prioritise while they were still collecting.

Quick check

A teammate fills every branch of a mind map with full paragraphs of text. What's the issue?

3

Where PMs Actually Use Mind Maps

Mind maps earn their place in a handful of specific product situations, and it is worth knowing which — so the tool does not become a habit applied to everything.

Opening an investigation, when a metric has moved and nobody knows why. Branch by plausible cause area before committing to a theory, and you avoid the usual failure of investigating the first explanation someone offered.

Preparing for a difficult conversation, by branching on who will object and what each person will object to.

Scoping a feature, where the branches become the edges nobody thought about: error states, permissions, migration, what happens to existing data. Onboarding yourself to a new domain, where a map of what you know and what you do not is a better artefact than linear notes.

Where they do not help: anything requiring arithmetic, comparison or sequence. A mind map has no mechanism for weight, so it cannot show that one branch is worth five times another.

The signal that a mind map is the right tool is that you cannot yet write the list. The signal that you have outgrown it is that you can.

Opening an investigation

A metric has moved and nobody knows why. Branch by plausible cause area before committing to a theory, and you avoid investigating the first explanation someone offered.

Preparing for a difficult conversation

Branch on who will object, and on what each of them will object to.

Scoping a feature

The branches become the edges nobody thought about: error states, permissions, migration, what happens to existing data.

Onboarding yourself to a new domain

A map of what you know and what you do not is a better artefact than linear notes, because the gaps are visible.

When a mind map is the right tool A chooser. Use a mind map when the problem has no shape yet; use a structured tool once it does; and never use one where arithmetic or sequence is required. Do you already know the structure? no Mind map. You cannot write the list yet yes A tree, funnel or table — they assume the structure needs arithmetic Not a mind map. It has no mechanism for weight
Two of these branches lead somewhere and the third leads away from the tool entirely. A mind map has no mechanism for weight, so it cannot say that one branch is worth five times another — and a room that needs that answer will invent it from tone of voice instead.

Everyday example

The tool you reach for when the problem has no shape yet. Once it has a shape, a mind map is the wrong tool — you want a tree, a funnel or a table, all of which assume the structure you were still looking for.

Where it earned its place

A team used a mind map to prepare for a stakeholder meeting, branching by who would object and what each would object to. It surfaced two objections nobody had considered and one that turned out to be fatal to the plan — which was cheaper to discover on a whiteboard than in the room.

Quick check

A team has a fuzzy, not-yet-defined problem area ("our onboarding feels off somehow") and needs to explore it before writing a sharp problem statement. What tool fits this early stage well?

4

Mind Maps vs. Other Tools

Several product tools are drawn as branching diagrams, and confusing them causes real damage — because only some of them can be checked for correctness.

A mind map holds associations. Nothing is weighted, nothing multiplies, and there is no correct version. Its job is to find the shape of a problem that does not have one yet.

A KPI tree holds arithmetic. Children must combine to produce the parent, which means a wrong tree is demonstrably wrong and can be repaired.

An opportunity solution tree holds a decision structure, governed by a rule you can visibly violate.

A fishbone holds a diagnosis, organised by fixed cause categories.

They look alike on a whiteboard and belong at completely different moments. The characteristic failure is carrying the loose tool into a room that expects a strict one — presenting associations to people who came to make a decision. Every branch then appears equally weighted, and importance ends up assigned by whoever speaks with the most confidence.

Use the loose tool to find the shape, then move what you found into the strict one before anyone has to decide anything with it.

Loose

Mind map

Holds associations. Nothing is weighted, nothing multiplies, and there is no correct version.

Strict

KPI tree

Holds arithmetic. Children must combine to produce the parent, so a wrong tree is demonstrably wrong and can be repaired.

Strict

Opportunity solution tree

Holds a decision structure, governed by a rule you can visibly violate: a solution may never attach to the outcome.

Strict

Fishbone

Holds a diagnosis, organised by fixed cause categories rather than by whatever came to mind.

Loose tools and strict ones Two panels. A mind map holds associations and has no correct version; a KPI tree, opportunity tree or fishbone are governed by rules and can be checked. Loose · mind map finds the shape Branches are associations Nothing is weighted No correct version exists For when structure is unknown Strict · tree, fishbone carries a decision Governed by a rule Arithmetic or causation Can be demonstrably wrong For when a decision follows
Both columns are branching diagrams and they look alike on a whiteboard, which is the whole trouble. Only the right-hand one can be shown to be wrong — and a diagram nobody can refute, presented to people who came to decide something, hands the decision to whoever sounds most certain.

Everyday example

A mind map is a brainstorm with geometry. A KPI tree is arithmetic. An opportunity solution tree is a decision structure. They all look like branching diagrams and only one of them can be checked for correctness.

Using the map as if it were a tree

A team presented a mind map to leadership as though it were a prioritisation. It had no criteria, no sizing and no arithmetic, so every branch looked equally weighted and the meeting spent an hour assigning importance by voice. The map had done its job in the workshop; it was the wrong artefact to take out of the room.

Quick check

A researcher has 200 sticky notes of raw user quotes from interviews and needs to find recurring themes. Which tool fits better, a mind map or an affinity map?

Drill what you learned
Scenario 1 easy

A PM opens a blank spreadsheet to explore a fuzzy, not-yet-defined problem area.

What's a better starting tool, and why?

Scenario 2 easy

A mind map's central node reads: "Improve our onboarding flow by adding a five-step wizard with progress indicators and skip options."

What's wrong with this central node?

Scenario 3 easy

A branch on a team's mind map says: "Users seem to get confused around the third screen of onboarding when we ask for payment info before they've seen any value, which might be why..."

What's the fix?

Scenario 4 easy

A facilitator is running a brainstorm from the HMW question "how might we help sellers price with confidence?" and wants a tool to capture the session live.

Would a mind map fit well here?

Scenario 5 easy

A team wants to break "Revenue" into the exact multiplied inputs that produce it (Users x Conversion x ARPU).

Is a mind map the right tool?

Scenario 6 medium

A UX researcher has 200 individual sticky notes, one per user quote, and needs to find 5-6 recurring themes.

Should they build a mind map from one central topic?

Scenario 7 medium

A meeting note-taker uses a strict bulleted outline during a wide-ranging discussion and keeps having to backtrack and renumber items.

What alternative would handle the messiness better?

Scenario 8 medium

A product team's mind map for "Q3 Feature Ideas" has grown to 80 branches with no grouping or color-coding.

What's the practical problem?

Scenario 9 medium

A new PM insists mind maps are "unprofessional" and refuses to bring one to a stakeholder review of a defined roadmap.

Is that instinct right?

Scenario 10 medium

A mind map for "Reasons Users Churn" has one branch labeled "Price" and another labeled "Too Expensive" right next to it, unconnected.

What should happen?

Scenario 11 hard

A designer sketches a mind map with images and rough icons instead of text for every branch.

Is this a valid approach?

Scenario 12 hard

A team uses a mind map to plan a feature launch, including specific dates and a sequenced list of dependent tasks.

What's the concern?

Scenario 13 hard

During a brainstorm, one participant keeps trying to evaluate and cross out branches as they're added to the shared mind map.

What's the issue?

Scenario 14 hard

A stakeholder reviews a mind map and asks "so what's the actual decision here?" after 45 minutes of branching.

What does this reveal?

Scenario 15 hard

A remote team wants to build a mind map together live, with people in four different time zones.

What's a practical way to do this well?

Drilled it. Now apply it to a real situation.

Put it to work
From lesson 1

The list that hid the dependency

A payments team

Planning a migration to a new card processor, the tech lead writes a linear checklist of 34 items. Two weeks in, the team discovers that refunds cannot be tested until chargebacks are configured, which cannot happen until the merchant account is live — three items sitting 20 rows apart on the list with nothing connecting them.

What does a radial map show that the list could not?

From lesson 2

A map that was just a list in a circle

An HR software team

Someone maps the onboarding product. The centre says "Onboarding". Around it, eleven branches: Contracts, Equipment, Payroll, Buddy, Training, Access, Welcome Email, Desk, Handbook, Introductions, Probation.

Every branch is a single node. Nothing has children.

What has gone wrong, and what would fix it?

Select all that apply — there are 3 to find.

From lesson 3

Four moments, one tool

A product team's week

Four situations in one week. A mind map genuinely helps in some and is the wrong reach in others.

Order these from best fit for a mind map to worst.
A. Opening up a vague problem space before research. B. Preparing questions for a discovery interview. C. Communicating a decision to the exec team. D. Tracking which of 40 bugs are fixed.

Drag the rows, or use the arrows, then check.

  1. A — opening up a vague problem space Best fit. Nothing is known, nothing is ordered, and the job is to find the shape. This is exactly what radial branching is for.
  2. B — preparing interview questions Good fit. Themes branch into questions, and seeing them grouped stops you spending the whole hour on one branch and missing another entirely.
  3. C — communicating a decision upward Poor fit. A map shows everything considered with no emphasis; an exec needs the conclusion and the reasoning that supports it. Use the map to prepare, then write prose.
  4. D — tracking 40 bugs Worst fit. State that changes daily, needs filtering, sorting and assignment. A map has no state and no query. This is a table.
From lesson 4

Same problem, four different tools

A grocery app

Substitutions — when an item is out of stock and a replacement is sent — generate more complaints than anything else in the product. Four people propose four different artefacts to start with.

Work out which to reach for, and when.

  1. Step 1 of 3

    Nobody yet agrees what "the substitutions problem" even covers. Which tool goes first?

    The map produced five branches. Three were about the moment of substitution; two were about what happens afterwards.

  2. Step 2 of 3

    The team picks one branch — "the customer finds out too late". Which tool now?

    The journey map showed the notification arriving after the van had left, which made every subsequent step worse and was invisible in the mind map.

  3. Step 3 of 3

    The fix is scoped. How do you decide whether it is worth the quarter?

    Three tools, three modules, in an order where each one's output was the next one's input.

Notification