Start with a specific topic, group supporting details into a few branches, and mark uncertainty. These fictional examples show how to turn a map into a useful outline or action list.

What changed (Nov 06, 2026): Merged content from the top 5 mind map examples post: added decision, brainstorm, goal and trip examples, thesis and lecture-note variations, a tools table with free plans checked November 6, 2026, and two FAQs. Added downloadable outlines and OPML files for the four new examples, three related guides, a shorter description, and corrected cover alt text.
To make a mind map, put one specific topic in the center, add 3–5 main branches, and place supporting details under the branch they explain. Mark unanswered questions, check the relationships, and copy any agreed actions into a separate task list. Use the examples below for a launch, a meeting, a problem investigation, study work, a decision, a brainstorm, a personal goal, or a trip.
Updated November 6, 2026. Published by AFFiNE. These are fictional, editor-written examples you can adapt; they are not customer case studies or measured productivity results.
The same steps answer “How do I create a mind map?” You can begin on paper or in an editor. For AI-assisted drafting, see rough notes to mind map.
Input: a fictional three-person review of a website pilot, with 12 ideas, 3 decisions, and 4 follow-up tasks. Purpose: make the agreed scope and unresolved risks visible.
Website pilot
├─ Scope
│ ├─ One-page pilot site
│ └─ Email signup; no payment flow in this phase
├─ Decisions
│ ├─ Use one clear headline
│ ├─ Use a manual FAQ before adding a chatbot
│ └─ Keep an existing page available during the pilot
├─ Risks
│ ├─ Mobile form behavior needs checking
│ └─ Launch date remains unconfirmed
└─ Next actions
├─ Alex: draft the headline
├─ Priya: check the mobile form
├─ Sam: draft the FAQ
└─ Alex: confirm a launch date with the team
Finished output: a scope map plus a separate four-row action list. The names are fictional and due dates are intentionally blank until agreed. This is not a scheduling engine: do not infer dependencies, calendar events, or reminders from the shape of the map.
Download the launch outline, OPML structure, and actions CSV. The CSV was written from the example decisions; it is not an automatic mind-map-to-task export.
Input: “People cannot find the setup guide.” Purpose: organize possible explanations without mistaking them for proven causes.
| Branch | Example hypothesis | Evidence to collect |
|---|---|---|
| Content | The guide uses a different product name | Compare the guide's wording with actual search terms |
| Navigation | The relevant link is hard to find | Observe someone following the intended path |
| Access | Some intended readers cannot open the page | Check the affected account's permissions |
| Maintenance | Two conflicting versions are available | Compare URLs, dates, and owners |
These are cause categories, not the “5 Whys.” To use repeated why questions, follow one observed problem and investigate each answer before continuing. For example: “Why did this reader miss the guide?” may lead to a navigation hypothesis, but it does not prove the navigation is wrong for everyone.
Finished output: an evidence-collection plan, then a decision once the evidence is available. Use a fishbone diagram if cause categories are more useful than a radial map. A mind map alone cannot establish a root cause.
Input: a discussion where ideas, commitments, and unresolved questions arrive in a mixed order. Purpose: preserve what was decided without presenting every suggestion as a commitment.
Use branches for Context, Decisions, Open questions, and Actions. Under each decision, record the actual wording and relevant source note. Under an action, record an owner only when someone has agreed to it. Keep a chronological record as well if the sequence matters.
Finished output: a short decision brief that participants can correct. The sample decision brief shows one possible written follow-up to the launch map.
Start with a question or provisional thesis. Add branches for each argument, then evidence, counterarguments, and source references beneath them. Mark weak claims “needs evidence.” A source title alone does not support a claim: keep the relevant page or passage so you can check what it actually says.
Example: “Should the library extend weekend hours?” can branch into Access, Staffing, Cost, and Alternatives. Add evidence only after collecting it; do not invent a survey or turn a preference into a statistic.
Finished output: a writing outline with traceable sources. Keep the full quotation and citation in your research notes; a compact map is not a substitute for them.
Variation for a research project or thesis: put the research question in the center, then branch into Objectives, Sources, Method, Chapters, and Gaps. Under Sources, group readings by theme so you can see where the evidence is thin. Update the map when the question changes.
Use a topic such as “Cellular respiration,” then branches for concepts, processes, examples, and questions you cannot yet answer. Attach course-page references. Try explaining one branch without looking, then compare your explanation with the material and correct it.
Finished output: a review plan focused on gaps. A mind map is one study option; this guide does not promise faster learning, a particular recall improvement, or higher grades. Use a linear outline, practice questions, or another format when it better fits the subject.
Variation for lecture notes: start with the lecture title, add a branch for each main point as it is introduced, and put examples and questions underneath. After the lecture, fill gaps from the slides or readings and mark anything you still need to ask about.
Input: a fictional team choosing a venue for a two-day workshop. Purpose: compare options against agreed criteria instead of arguing from first impressions.
Workshop venue
├─ Options
│ ├─ Office meeting room
│ ├─ Rented venue downtown
│ └─ Remote session
├─ Criteria
│ ├─ Cost within the agreed budget
│ ├─ Travel time for attendees
│ └─ Space for breakout groups
├─ Evidence
│ ├─ Venue quote: requested, not received
│ └─ Room capacity: needs checking
└─ Decision
├─ Owner: Sam
└─ Status: open until the quote arrives
Finished output: a comparison table with options as rows and criteria as columns, plus a dated decision note. The same structure works for choosing software, a supplier, or a career direction: keep options and criteria on separate branches and record where each piece of evidence came from. A map does not weigh criteria for you, so agree on what matters most before you score.
Download the decision map outline or the decision map OPML file.
Input: “Ideas for a spring newsletter campaign.” Purpose: collect many ideas first, then sort them before anyone commits. A loose brainstorm map like this is sometimes called an idea map.
Use branches for Audience, Message angles, Channels, Assets needed, and Questions. During the session, add ideas without judging them. Afterwards, mark each one “keep,” “park,” or “drop.” If the ideas arrived as loose sticky notes, you can first sort them bottom-up with the affinity diagram method. The same layout works for product feature ideas, a startup outline (customers, offer, revenue, channels, risks), or design ideation (color, type, and layout references).
Finished output: a shortlist of two or three ideas, each with an agreed next step and owner. Parked ideas stay on the map so they are not lost. For structured session formats, see brainstorming templates.
Download the brainstorm map outline or the brainstorm map OPML file.
Put one goal in the center, such as “Run a 10 km race.” Branch into Why, Milestones, Weekly habits, Obstacles, and Support. Write each milestone as something you can check, and leave dates blank until you have actually set them.
Finished output: a short list of next steps you can copy into a calendar or to-do list. Review the map when a milestone passes or the plan changes. A goal map is a planning aid; it does not guarantee results.
Download the goal map outline or the goal map OPML file.
Use the destination and dates as the central topic. Add branches for Transport, Accommodation, Places to visit, Documents, Budget, and Packing. Keep booking references and passport details in a private note rather than on the map, especially if you share it.
Finished output: an itinerary outline and a packing checklist. The same pattern works for a party, a wedding, or a house move: one branch per area of work, then a separate checklist for tasks with dates.
Download the trip map outline or the trip map OPML file.
Use short labels where they remain precise, and keep longer explanations in nearby notes. Color can help distinguish a question from a decision, but add a text label too so meaning does not depend on color. A radial layout is optional; choose a layout whose relationships your reader can follow.
Do not force a single word onto every branch if a phrase is clearer. Split a large map when its readers can no longer find the key question, evidence, or action. There is no universal branch count that makes a map correct.
| Need | Paper | Digital editor |
|---|---|---|
| Rough exploration | Easy to start with a pen and available space | Easy to revise if you know the controls |
| Collaboration | Useful for people gathered around the same surface | Can support remote work, depending on the app and sharing settings |
| Revision | Redrawing may be needed | Nodes can be rearranged in an editable map |
| Retrieval | Label, photograph, and file the result | Typed labels may be searchable; check the app and format |
| Preservation | Keep the original or a scan | Keep the editable file and a backup; an image preserves appearance only |
In AFFiNE, a document can hold written notes and an Edgeless visual workspace. Use that arrangement when the map needs explanations beside it. Check your plan's cloud sharing limits if other people need access. A local workspace, a shared cloud workspace, and an AI request have different data paths.
To compare free plans and limits across five apps, read five free mind map tools compared.
If you choose a digital editor, these are common options. Free-plan details were checked on each vendor's website on November 6, 2026 and change often. Disclosure: AFFiNE publishes this guide.
| Tool | Good fit for | Free plan |
|---|---|---|
| AFFiNE | Maps that need written notes and documents beside them | Free local workspaces; cloud sharing limits are on the pricing page |
| XMind | Dedicated mind maps with several layouts on desktop, mobile, and web | Up to 10 manually created online maps |
| Miro | Live workshops where many people add ideas to one board | 3 editable boards |
| ClickUp | Teams that want map nodes to become tasks in ClickUp | The Mind Map view is not included on Free Forever; paid plans include limited or unlimited use |
| Coggle | Quick browser-based maps shared by link, with version history | 3 private diagrams and unlimited public diagrams |
For a longer comparison, see mind mapping software.
For the launch example, “Mobile form behavior needs checking” becomes “Check signup on a mobile device and record any failure,” assigned to Priya. The due date stays blank because none was agreed.
AFFiNE supports visual work and structured information, but this guide does not claim an automatic switch from a mind-map object to a Kanban board or a calendar. The downloadable actions CSV is a manual handoff example you can copy into your chosen workflow.
Download the full sample pack. It includes Markdown outlines and OPML files for examples 1, 6, 7, 8, and 9, an interview-notes outline and OPML file, a decision brief, and CSV checklists. All examples are fictional. The OPML files have been checked as XML with nested text outlines, but have not been verified in an AFFiNE UI import session. They contain text structure, not colors, positions, images, permissions, or calendar integration.
If you try an import, use a copy and check node text, parent-child relationships, adding and moving a node, saving, and reopening. Record the version and result in the included verification sheet. You can also build the map manually from the Markdown outline or begin with the visual mind-map study planner.
Use a central topic, main branches, supporting details, and visible relationships. Add labels or color where they help distinguish categories. Images are optional, and precise phrases can be more useful than single-word labels.
Yes. Group context, decisions, unanswered questions, and actions into separate branches. Verify the decision wording and task owners with participants, and retain a chronological record when the sequence is important.
It depends on the task. Paper can work well for a local discussion or an initial sketch. Digital maps make revision and remote sharing easier when the tool supports them. Neither format guarantees better recall or better decisions.
Write the question you want to answer, then try branches such as Who, What, Why, Constraints, and Unknowns. Leave a branch empty if you do not yet have evidence. The purpose is to reveal what you need to learn.
Common examples include a project launch plan, meeting notes organized by outcome, a problem investigation, an essay or thesis outline, an exam review or lecture-notes map, a decision map, a campaign brainstorm, a personal goal map, and a trip plan. Each starts with one specific central topic and a few branches chosen for that purpose.
Choose by how the map will be used. A dedicated mapping app such as XMind or Coggle suits a single structured map, a whiteboard such as Miro suits live group sessions, and a task tool such as ClickUp suits maps that become assigned work. Paper is enough for a quick sketch. Check the free-plan limits in the tools table before you build many maps in one tool.
Use brainstorming templates to structure an idea session, or read AI-assisted notes to mind map before asking a model to organize your source notes.