01 / UNDERSTAND
What is mind mapping?
Mind mapping develops a topic through branches radiating from a central idea. Short labels, subbranches and connections make an expanding set of associations visible. It is a way to externalise and organise thinking while it is still taking shape.
A mind map is not automatically a model of a service or an analysis of research. Its structure reflects the person or group making it. A tidy branch can still contain a weak assumption.
Why use Mind Mapping?
Early discussions often jump between needs, features, constraints and unanswered questions. A map gives those thoughts a place without requiring a finished narrative. It can help a team find overlooked directions and decide what deserves a more rigorous investigation.
When to use it
USE IT WHEN
A design question feels broad and needs several possible angles.
You are preparing a discussion, investigation or piece of writing.
The team needs to see connections between ideas before choosing a direction.
When to choose another method
Use Affinity Mapping to organise observations from a defined body of research.
Use Ecosystem Map to describe actors and exchanges around a service.
Use a task flow or prototype when sequence and interaction are the central question.
What you’ll need
Write one question in language the group understands. Bring relevant notes but distinguish them from new associations. Use paper or a shared digital canvas that participants can comfortably access. Agree whether the map is private thinking space or a shared record that others will need to interpret.
What the method needs
Keep the elements that help answer your question and support a decision.
One topic or question that gives the exploration a boundary.
Distinct starting angles rather than a fixed universal set.
More specific ideas, examples or questions.
Relationships across branches that matter to the discussion.
A way to distinguish known material from speculation.
The limited set of directions worth carrying forward.
02 / PUT IT INTO PRACTICE
How to make a useful mind map
Keep evidence and assumptions distinct. Revisit your work when new information changes your understanding.
01
Frame the centre
Use a question that invites exploration without prescribing the solution.
Try helping residents borrow equipment, rather than designing a booking app.
02
Start with different angles
Create several branches from needs, circumstances, constraints or possible approaches.
Consider access, trust, maintenance and returning an item.
03
Expand in short phrases
Add concrete associations and split broad labels where useful. Keep the wording understandable later.
Under access, distinguish opening hours from transport and eligibility.
04
Connect across branches
Mark a relationship without forcing every idea into a single parent category.
Maintenance affects availability as well as trust.
05
Challenge the arrangement
Look for overloaded branches, missing perspectives and labels that quietly assume an answer.
A branch called app features may be too narrow for the original question.
06
Choose the next form
Turn selected branches into research questions, concepts or an outline. Keep the map as a record of exploration.
Investigate return difficulties before choosing a reminder mechanism.
Example: exploring an equipment lending service
Illustrative example: a community group is considering a shared equipment library. The central question is how residents could borrow useful items reliably. Initial branches cover access, trust, maintenance and returns.
A return branch produces questions about late items, damaged equipment and transport. A connection to maintenance reveals that an item can be returned on time but still be unavailable to the next borrower. The group adds a question about inspection and turnaround.
Instead of immediately designing a booking interface, it would investigate how items are checked and how uncertainty is communicated. The map records possible considerations. It does not establish that any of these problems actually occur in a particular community.
03 / BELOW THE SURFACE
Below the surface: your first branches frame the answer
The structure that helps thinking can also constrain it.
FRAME
What does the centre assume?
Check for a hidden solution or viewpoint.
ALTERNATIVE
What changes under another centre?
Notice newly visible work and people.
TRANSFER
Which question deserves a next step?
Choose inquiry rather than diagram polish.
Starting with discover, book and collect may make the exercise look like a user flow. Starting with ownership, responsibility and repair may expose a different service question. Neither structure is neutral. Try a second centre or branch structure before treating the first as complete.
For the equipment library, compare a map centred on borrowing with one centred on keeping equipment usable. Note which people and activities become visible in only one version. That difference is a useful prompt for inquiry.
This guide’s editorial check does not require merging both maps into a huge diagram. Carry forward the consequential omissions and retain the separate perspectives. More branches can add clutter without correcting the original framing.
Mind Mapping companion worksheet
The two page companion includes a central question with open branches and a second framing review. Use it for short text entries, or print it to draw freely. It is an original worksheet rather than a prescribed mind mapping notation.
Practical tips
Keep enough wording for another person to understand each branch.
Use cross connections only where they add meaning.
Common mistakes
Presenting associations as validated research themes.
Polishing the map before deciding what it is for.
Assuming the first branch structure is the only sensible one.
What you’ll get
A visible exploration and a smaller set of next questions. Transfer those questions into research or concept development rather than treating the map as a final recommendation.