A concept map shows relationships between concepts using labeled connecting lines. It's more expressive than a mind map and more flexible than an outline. Perfect for complex domains where the relationships are as important as the concepts themselves.
Use a concept map when you need to show how concepts relate to each other — not just what they are, but how they connect. It's the right tool for explaining a system, mapping a knowledge domain, designing a curriculum, or exploring the relationships between components in a complex product or architecture.
Concept maps work well for learning and knowledge transfer. If you're onboarding someone to a complex domain, a concept map of how the key concepts relate is often more useful than any written explanation.
Each concept is written in a circle or rectangle on the board. Concepts are nouns — specific, concrete, well-defined. Start with the most general concepts at the top and work toward more specific concepts below. Aim for 10–25 concepts for a useful but manageable map.
The labeled connections between concept nodes. Linking phrases are verbs or verb phrases: 'causes,' 'is a type of,' 'requires,' 'produces,' 'is part of.' The linking phrase is what makes the connection specific and meaningful. A concept map without labeled links is just a diagram.
Each combination of two nodes and a linking phrase forms a proposition — a meaningful statement. 'Sprint retro → produces → action items' is a proposition. The proposition is the unit of knowledge in the concept map. A good concept map contains dozens of valid propositions.
Connections between concepts in different parts of the map that aren't in a hierarchical relationship. Cross-links are the most cognitively valuable part of the concept map — they reveal non-obvious relationships between domains that a hierarchical organization wouldn't show.
Concept maps are typically organized with more general, inclusive concepts at the top and more specific, less inclusive concepts at the bottom. The hierarchy isn't strict — some concepts span multiple levels — but providing a rough top-to-bottom organization makes the map more readable.
The focus question anchors the concept map: 'What do new team members need to understand about how BoardSnap generates action items?' Write it at the top of the board. Every concept in the map should be relevant to answering this question.
Write all relevant concepts on stickies — one per note. Don't organize yet. Aim for 15–30 concepts. More than 30 and the map becomes unreadable; fewer than 10 and it's not worth the format.
Place the most general, inclusive concepts at the top of the board. Place the more specific concepts lower. This loose hierarchy gives the map a readable flow.
Draw lines between related concepts and write the linking phrase on each line. Be specific about the link — 'relates to' is too vague. Use active verbs that describe the actual relationship.
Look across different sections of the map for non-obvious connections. Draw cross-links in a different color. These are the insights — the connections that weren't obvious before you built the map.
Snap the concept map with BoardSnap. The AI reads the node-and-connection structure and outputs a structured summary of the key propositions and cross-links — ready to use as an onboarding document or knowledge base article.
Concept maps are inherently non-linear — the relationships go in multiple directions, cross-links cut across the hierarchy, and the meaning lives in the connections between nodes as much as in the nodes themselves. A whiteboard handles this natively. Digital concept-mapping tools force you to work in a small viewport and lose the whole-board perspective that makes patterns visible.
BoardSnap reads the concept map structure — nodes, labels, and connections — and preserves the relationships as a structured knowledge graph. The map becomes a reusable knowledge artifact rather than a session artifact.
Joseph D. Novak developed concept mapping at Cornell University in the 1970s, based on David Ausubel's theory of meaningful learning. Novak designed concept maps specifically as a learning and knowledge organization tool, with the proposition structure (concept + linking phrase + concept) as the formal unit of knowledge.
Mind maps radiate from a single central topic in a tree structure. Concept maps show a network of relationships between multiple concepts with labeled connections. A mind map organizes information hierarchically around one idea. A concept map represents how multiple ideas relate to each other in a network.
10–25 is the practical range for a whiteboard session. Fewer than 10 and the map is too simple to be useful. More than 25 and the connections become too dense to read. For large knowledge domains, create multiple focused maps around different focus questions rather than one mega-map.
Yes. Concept maps are excellent for documenting how a product's core concepts relate — especially for complex developer tools, data platforms, and systems with many interdependent components. Snap the concept map with BoardSnap and the output becomes a starting point for architectural documentation or an API concept guide.
No exporting, no transcription. Snap the board, get the action plan.