itk-mindmapping

name	itk-mindmapping
description	Generate insights into relationships between concepts in a flexible and engaging way to visualize information.
intent	Show the relationships between concepts and ideas, which are often difficult. Foster creativity and generate a memorable final product. Introduce new ideas and explore connections between them.
type	component
phase	generate
outcome	generate
difficulty	beginner
group_size	2+ people
time_required	30+ minutes
best_for	["Early discovery when the problem space is ambiguous and you need to map dependencies before scoping a PRD","Decomposing a vague feature request into themes, sub-features, and edge cases for backlog refinement","Synthesizing user interview findings into clustered insights that reveal Jobs-to-be-Done patterns","Kicking off OKR planning by visualizing how candidate initiatives connect to strategic objectives","Aligning cross-functional teams during a kickoff by externalizing assumptions about a domain"]
sources	["MITRE Innovation Toolkit (ITK)","https://itk.mitre.org/toolkit-tools/mindmapping/"]

Mindmapping

What Is It

Generate insights into relationships between concepts in a flexible and engaging way to visualize information.

Why Use It

Show the relationships between concepts and ideas, which are often difficult. Foster creativity and generate a memorable final product. Introduce new ideas and explore connections between them.

When to Use It

When creating, visualizing, and organizing ideas, either individually or with a group. When the problem is not well defined or if a solution field is broad. When you would normally hold a “brainstorming” session.

How to Do It

1. Write the main topic in the center of the paper or whiteboard.
2. Using images, symbols, and keywords, add related topics that branch out of the main topic. Use multiple colors throughout the mind map.
3. Add branches to each new entry. These branches may represent specific instances of a general topic or general instances of related topics. Keep the mind map clear by using radial hierarchy or outlines in each branch. Use emphasis and show associations between branches and entries.

Key Concepts

Radial Hierarchy — Ideas branch outward from a central node, with proximity to center signaling importance. This structure forces explicit parent-child relationships that surface how sub-features ladder up to a core theme.

Associative Linking — Drawing cross-connections between branches that aren't directly hierarchical. For PMs this exposes hidden dependencies and shared components across otherwise separate epics.

Divergent Generation — A non-linear ideation mode that prioritizes breadth before structure. It mirrors discovery-phase thinking where you want to surface the full solution space before converging on scope.

Central Node — The single anchoring topic the entire map radiates from, typically a problem statement, user goal, or feature theme. A poorly framed central node distorts every downstream branch.

Depth Levels — The successive layers of branches from general to specific. Shallow maps stop at obvious categories; deeper levels are where non-obvious edge cases and requirements emerge.

Visual Encoding — Using color, imagery, and emphasis to encode meaning like priority, ownership, or status. This turns the map into a shared artifact teams can scan and reason about quickly.

PM Applications

• Structuring the 'scope and requirements' section of a PRD by mapping the central feature outward into user flows, edge cases, and non-functional requirements.
• Running a discovery workshop where you map a Job-to-be-Done into related needs, pains, and gains to identify which branches warrant deeper research.