Mind Map Exercise

A project manager who is highly organized and sequential in her thinking. When given the mind map exercise, she produces a central node with five branches, each branch with one item - effectively a formatted list with spokes. The structure looks like a mind map but doesn't function like one: there are no connections between branches, no sub-branches, and no emergent insights from the spatial relationships.

Name the structure before she commits to it. 'A mind map works differently from a list - the value comes from branching and from the connections between branches, not from the number of spokes. Before you finalize this, let's try extending one branch. Take this one and go two levels deeper: what does this connect to, and what does that connect to?' The resistance is efficiency: she has a clear, organized output and adding branches feels like mess. Name the value of productive mess: 'The branches that feel least organized are usually where the new connections are.'

Watch whether she can extend branches into sub-branches when prompted. If she adds one level of sub-branches but stops there, she's still in list mode. Also watch the Connections section: if she leaves it blank or draws connections only between items she already knew were related, the map hasn't produced new insights. The map is working when she draws a connection and looks surprised by it.

Start with the Connections section. 'Walk me through the connections you drew. Which one surprised you?' If the connections feel obvious: 'What two branches do you NOT see a connection between - and what would it mean if there were one?' That question often surfaces a link she's been avoiding. The question that creates movement: 'What does this map show you that your usual way of thinking about this topic has been missing?'

A VP who has used mind mapping informally for years. He's comfortable with the branching structure and generates rich, detailed maps quickly. But he always stops at the generation phase - he has never explicitly mapped connections between branches or written down what the structure revealed. He uses it as a brainstorming tool but not as an analytical one.

Name the two-part structure explicitly. 'You're good at the generative phase - you build rich maps fast. The exercise adds a step you may not have used: mapping connections between branches, not just within them, and then synthesizing what those connections mean. That's the part where the map stops being a list of ideas and starts being a picture of something.' The resistance is completion satisfaction: the generation phase feels like enough. Don't contest that. 'The generative phase is productive on its own. The question is what you might be missing by stopping there.'

Watch the Connections section specifically. If he maps connections only between adjacent or obviously related branches, he's pattern-matching rather than discovering. The valuable connections in a rich map are usually between branches that don't obviously belong together. Also watch whether his Insights section reads as a summary of what he already knew before the map, or as something the map revealed that he didn't know going in.

After he completes the Connections section, ask him to read the two or three connections that feel most unexpected. 'What does this connection tell you that you didn't know before you drew it?' Then move to Insights: 'Read me what you wrote. Is this something the map showed you, or something you already knew?' The question that creates movement: 'If you had to act on one insight from this map - not a plan, just a next move - what would it be and what's making it hard to name?'

A senior manager who wants to do the mind map exercise on a topic she's been circling in coaching without engaging directly: whether to leave her organization. The topic is emotionally charged. She gravitates toward the mind map because it feels less direct than a pros/cons analysis or a decision framework. That motivation is worth understanding before the exercise begins.

Name the topic before the exercise. 'You've said you want to mind-map this decision. Before we start, I want to name what the map will likely surface: the reasons you want to leave and the reasons you're staying. Both branches will be on the same page. That can be useful or uncomfortable - sometimes both. Are you ready to put both of those on paper?' That preparation prevents her from steering the map away from the difficult content without realizing she's doing it.

Watch which branches get the most sub-branches and detail. If the 'stay' branches are thin and the 'leave' branches are rich, she's been thinking about one side much longer. The reverse pattern - thin 'leave' branches - may indicate avoidance of the exit scenario. Also watch the Connections section: a connection between 'what I value' and 'what this organization offers' is the most revealing connection the map can produce, and clients often skip it.

Start with the branch distribution. 'Which side of this map is more developed? What does that tell you about where your thinking has been?' Then move to the connection she may have avoided: 'Is there a connection you could draw between the values branch and the organization branch? What would you write on that line?' The question that creates movement: 'Looking at this complete map, what does it say about what you know and what you're still avoiding knowing?'