Mind Mapping

A mind map is a non-linear diagram that arranges ideas around a central idea, linked by single-keyword branches to topics and then to sub-topics. The business analyst uses it to think through a complex problem, explore its relationships and present a consolidated view. BABOK describes the artifact and states that there is no standardised format, which is the source of both the technique's flexibility and its risk: a map is judged by its readability, and no format guarantees that. The rules that make a map readable are the method of Tony Buzan, who codified the technique, and they decide whether the map stays a shareable thinking aid or degenerates into a scribble only its author can read.

Purpose

A mind map arranges a complex concept around a central idea and single-keyword branches, so it can be thought through, explored and presented without being forced into a linear order from the outset. BABOK gives it three uses: thinking through a complex concept or problem and generating its ideas, exploring the relationships between the facets of that problem in a way that stimulates creative and critical thinking and presenting a consolidated view to others. The deliverable is the map itself, an artifact kept in front of you while the thinking is still in motion.

The feature that decides everything, BABOK states in its very description: there is no standardised format for a mind map. No notation stands between the analyst and the problem: you place ideas where they belong, graft on a branch without reordering the rest and follow the thought instead of bending it to a template. That same absence of format tolerates the map you can still read six months later just as readily as the cloud of branches that is illegible by the next morning, and nothing in the format tells the two apart.

What tells them apart is a discipline, and it belongs to the method of Tony Buzan, the inventor of the modern mind map. BABOK describes the artifact, its elements and its uses; Buzan prescribes how to draw a good one. A successful map depends on one author's rules, and they hold because they produce maps other people than their author can use.

Usage

When to use it

Early framing of a fuzzy problem: hold every facet of a complex subject in one view before flattening them into requirements.
Consolidating a workshop: gather a group's ideas into one shared picture everyone recognises.
Structuring a presentation or a scope: draw out the main topics and their order before writing an outline.
Exploring associations: surface the links between the facets of a problem when the aim is to understand, not to specify.
Active note-taking: capture a meeting or a reading whose subject branches out, keeping every point tied to its topic.

When not to use it

The deliverable must be traceable and shareable: for a rigorous requirements specification, use an appropriate model or notation (process model, data model), not a personal map.
The goal is the sheer quantity of raw ideas: the effort of structuring inhibits generation, so run a brainstorm first, then map the result.
The map must be understood by people who were absent: its associations are its author's own and do not carry across, so document the subject in an explicit model.

Description

What BABOK leaves free: the seven elements

BABOK describes the map through seven elements, without prescribing how to arrange them. They are the shared vocabulary of every map.

The central idea (main topic) is the concept being worked out, placed at the centre so that topics radiate from it in every direction; often an image, because an image carries a great deal of information and triggers associations.
The topics develop the central idea, each linked to it by a branch; as few or as many as the subject demands.
The sub-topics develop a topic while staying attached to the central idea, linked by a keyword branch.
The branches are the associations between central idea, topics and sub-topics; each carries a keyword that names the link.
The keywords are the single words placed on the branches; they categorise the topic and trigger further associations.
Colour categorises, prioritises and analyses topics and associations; BABOK notes that no colour code is standard, so the choice belongs to the author.
Images say what a short title cannot and stimulate new associations.

What Buzan disciplines: radiant thinking

This freedom moves the rule from the standard to the method. Buzan framed his own around radiant thinking: a complex problem is thought out from a single centre from which the topics radiate, each idea linked to the one it comes from. Three rules follow that separate a readable map from a scribble.

One keyword per branch

A single word stays open and invites further associations; a whole sentence is a closed thought that shuts the branch down. It is the rule practice breaks most often, and breaking it turns the map into a list in disguise.

A real centre

A strong central idea, ideally a colour image, to which everything attaches. Without it the topics hold on to nothing and the map falls apart.

Colour and image as structure

Used throughout to categorise and to anchor, they carry information rather than decorate.

Buzan also prefers curved, organic branches to straight lines. These rules belong to an author, while BABOK confines itself to describing the artifact. We follow them because they produce readable maps.

Building the map

Construction runs from the centre outward. You place the central idea in the middle of the surface, with space around it. You radiate the first-level topics, one per branch. You descend into sub-topics wherever a topic divides, one layer at a time. You use colour to mark a category or a priority. Solo, the map follows its author's thinking and comes together quickly. In a group, a facilitator holds the board, solicits the branches and arbitrates their placement, and readability for others becomes the object of the work.

The two limitations BABOK recognises

BABOK states two limitations, and they are the two failures the discipline sets out to contain. The first: the map can be diverted into a brainstorming tool, because the act of documenting ideas and tracing associations can inhibit the generation of ideas. The practical consequence is to separate the two moments: generate the ideas first, map them afterwards. The second: a map's meaning is hard to communicate to others, because one person's associations are not another's. This is where the freedom of format costs the most, and it is where Buzan's discipline earns its place: a clear centre, one keyword per branch and a colour that categorises make a map readable by someone who was not there, as far as a map with no format can be. Beyond that, when the result really has to travel, the map gives way to an explicit model.

AI considerations

AI helps at three moments. It drafts a first map from a transcript or a framing document, proposing a central idea, topics and sub-topics that the analyst corrects rather than starting from nothing. It suggests branches and associations that bring distant facets together. It reorganises an overgrown map, clustering nearby branches and proposing a more readable hierarchy, which answers directly the communicability limitation BABOK notes.

The limit is one of principle. The value of the map is in the act of tracing the associations: it is by linking the ideas that the analyst understands the problem, and a machine-drawn map delivers the drawing without the thinking. The tool starts and revises; it does not think in the analyst's place. Data sensitivity sets the second limit: handing the transcript of a workshop or the notes from an interview to an external service is a disclosure of personal data, often outside Switzerland, and the choice of tool is settled on where that data is processed before it is settled on the quality of the map.

Examples

The example shows what the discipline changes on the artifact, at equal format. A municipality in French-speaking Switzerland opens the analysis of an online-services portal, the gateway through which residents and businesses would reach municipal services online. The subject has too many facets for a list on day one, and the analyst maps it before flattening anything.

The central idea is the online-services portal. Six topics radiate from it, each reduced to a keyword: Users, Services, Data, Integrations, Constraints and Risks. Under Users: residents, businesses, commuters. Under Data: residents' register, residents' records. Under Constraints: FADP, accessibility. Under Integrations: cantonal information system. The colour orange is reserved for the Risks branch and its attachments, so that a risk link stays visible wherever it appears.

The single-keyword rule is what keeps this map readable to a colleague who missed the session. Residents' register holds on a branch and is grasped at a glance; "online access to the residents' register for businesses subject to power of attorney" would not fit, would close the branch and would bury the idea inside a sentence. The same map, written in sentences, would become the scribble BABOK's second limitation describes: readable by its author that same evening, opaque to anyone else the following week. The format is free; readability is paid for in discipline.

Mind map framing a municipal online-services portal: a real centre, six single-keyword branches, one layer of sub-topics and colour reserved for risks. The single-keyword discipline is what makes it readable to a third party.

Visualisations

The technique's output is radial: a centre, branches, sub-branches and links that matter as much as the nodes. The finished map is also an instrument of control, read back like a readability checklist. Does each branch carry one keyword or a sentence that has closed it? Is there a single centre to which everything attaches, or do the topics float unanchored? Does the colour categorise, or decorate? A map that answers these three questions poorly is the one BABOK's communicability limitation targets: readable by its author that same evening, opaque to a third party the following week.

Cost

Phase	Level	Justification
Preparation	Low	A whiteboard and markers, a sheet of paper or a free piece of software are enough. No template and no prior data collection: you choose the central idea and begin.
Execution	Low to moderate	An individual map is drawn in minutes. A facilitated group map costs the participants' time, the running of the session and the arbitration of branch placement.
Documentation	Low	The map is the deliverable. The line rises to moderate when the map has to be redrawn cleanly for people who were absent from the session, which is the cost of the free format.

Tools

The basic tooling is either a whiteboard and coloured markers or a sheet of paper and pencils. For a co-located group map, repositionable notes on a wall become movable branches. None of these forms survives a distributed team: a map on a physical board stays in the room, and a remote team calls for a shared online canvas.

Mind-mapping software (XMind, MindManager, Freeplane, Coggle) holds the map in a format you can collapse, reorganise and export; it often enforces one word per node, which builds Buzan's discipline into the tool. Ayoa extends Buzan's method directly. Collaborative canvases (Miro, Mural) carry the group map remotely, with several authors at once and a map that stays accessible after the session. The choice of an online service is also settled on where the data is hosted, as soon as the map holds sensitive information.

Sources

IIBA, A Guide to the Business Analysis Body of Knowledge (BABOK Guide) v3, §10.29 Mind Mapping: the definition of the artifact, the seven elements, the three business-analyst uses, the strengths and the two limitations. BABOK states explicitly that there is no standardised format.
Tony Buzan and Barry Buzan, The Mind Map Book: How to Use Radiant Thinking to Maximize Your Brain's Untapped Potential, BBC Books, 1993: the method of the technique's inventor, including radiant thinking, the central image and the one-keyword-per-branch rule. This is one author's method, distinct from BABOK's format-free description.