A Chat Disappears. A Map Keeps Growing.
Most AI conversations are throwaway -- you ask, you get an answer, you close the tab. A mindmap is different. It's a workspace you come back to, branch from, and build on over time.
Explore a reference map
A living reference map of US history and its presidents, zoomed out to the whole timeline, so you can zoom into any era or president and keep adding to it.
How it works
A chat is a single session. You ask questions, get answers, and when you close the tab, the conversation is effectively over. You might scroll back, but you’ll never branch from message #47 to explore a tangent you skipped.
A mindmap is a workspace. You create it once and come back to it as your understanding grows. Every new thing you learn gets added as a branch in the right place. The structure holds the context, so even months later you can pick up exactly where you left off.
-
Start with a question or topic. It doesn’t need to be fully formed. The first few branches are a rough sketch of what you’re exploring.
-
Come back when you learn something new. Read an article, had a conversation, ran an experiment — add it as a branch where it belongs. The tree grows organically, not chronologically.
-
Branch from any point at any time. Found a branch from two weeks ago that’s suddenly relevant? Continue from there. The full context of everything above that branch is still intact.
-
Use the map as a reference. The accumulated tree becomes a decision record, a research log, or a knowledge base. It’s not a chat transcript — it’s structured knowledge you can navigate.
Why this doesn’t work in a chat
Chat interfaces are designed for single sessions. The conversation scrolls linearly, and there’s no way to branch from an earlier point without starting over. If you learn something new three weeks later, you either start a new chat (losing all context) or append to a thread that’s already hundreds of messages long (losing all structure).
A tree has no “bottom.” Every node is a potential starting point. You can have a branch that’s been growing for months next to one you started today. The structure gives you orientation that a linear transcript never can.
Example
A public health researcher studying antibiotic resistance starts a map in January. By April, it has branches for overprescription patterns, agricultural antibiotic use, phage therapy as an alternative, and WHO policy recommendations. Each branch grew from different sessions: a literature review in week one, notes after a conference in February, a new CDC dataset she found in March, and a conversation with a microbiologist that challenged her framing of agricultural use. When she sits down to write her grant proposal, the map is the literature review — every source, every argument, every gap she identified, organized by where it fits in her argument, not by when she found it.
For related workflows, see deep dive for exhausting a single question, or decision making for weighing specific options.