A mind map represents ideas around a central topic through branches and relationships. It makes knowledge visible, exposes gaps, and opens associations; it is not a final hierarchy.

After brainstorming, Lumen may see that most proposals focus on the setup screen and that information before setup or help during the journey have received little attention.

Build a useful map

  1. Put the challenge in the centre.
  2. Create first-level branches: user, steps, information, support, and constraints.
  3. Add evidence and ideas, marking what is known and what is assumed.
  4. Connect related elements.
  5. Review gaps and form a testable question.
Independent initial setup
├── User: unfamiliar terms, wants to publish quickly
├── Steps: choose service, set availability
├── Information: example, preparation list
├── Support: contextual help, save and continue
└── Constraints: required data, accessibility

Exercise

Map a confusing task using people, steps, information, constraints, and opportunities. Mark assumptions that need checking.

Suggested answer

For a meeting that is hard to close, branches could include participants, preparation, decisions, time, and records. The assumption “everyone knows the goal” suggests sending a decision question beforehand.

Common mistakes

  • Using long sentences in every branch.
  • Presenting assumptions as facts.
  • Treating the map as a document that never changes.

Conclusion

Mind maps organise exploration without reducing it too soon. Lumen has connected needs, ideas, and constraints; SCAMPER will now modify an existing proposal systematically.

© Copyright 2026. All rights reserved