ANALYSIS TOOL BOX

Mind Map

Decompose a fuzzy analytic problem before hypotheses harden. Radiate drivers, actors, precedents, and open questions out from a central topic — spatially on the map or textually in the outline. Run timed brainwriting rounds that keep contributions hidden until the reveal, converge with dot-voting, flag a devil's advocate, and promote the top-voted ideas straight into an ACH matrix. The map stays a living, versioned artifact as the project matures.

How this technique works

About this technique

What is a mind map?

A mind map breaks a problem into its parts by branching outward from one central topic: drivers, actors, precedents and open questions. Tony Buzan popularized the format in the 1970s, and Heuer and Pherson include it among their decomposition and visualization techniques. It differs from a concept map, which formally labels every relationship. A mind map stays loose and associative, built for capturing ideas quickly and broadly rather than for structuring an argument.

When to use it

Use a mind map at the start of an analysis, when a question is broad and unstructured, and before you write hypotheses or test assumptions. Its job is to get everything out of people's heads before the group settles too early on one view. Later, the map feeds directly into a Key Assumptions Check and ACH.

How to use this tool

  1. Start with the central topic. Phrase it as your core analytic question.
  2. Branch out with ideas and sub-ideas. Add an idea as floating when it has no obvious home yet, and attach it later.
  3. Attach notes and sources to ideas, color-code them, and draw cross-branch connectors for links between branches.
  4. Run a facilitated session for group work. A brainwriting round keeps new ideas hidden until the reveal. An open discussion follows, then a dot-voting round to find what the group thinks matters most.
  5. Send top-voted ideas to ACH as hypotheses. Color an idea amber to flag it as a likely assumption for your Key Assumptions Check.
  6. Switch to the outline view for a linear read, and save versions as the map evolves.

Common pitfalls

  • Converging too early. Capture first, then organize.
  • Letting the loudest voice set the map. That is what silent brainwriting is for.
  • Overloading one branch. The tool warns when a branch grows too deep or wide, which is a sign to split it.

Related