InsightsDecisions, Risk & Governance

In 2018 and 2019, two Boeing 737 MAX jets crashed, killing 346 people.

By Uttam Dinodia2 min readView this post on LinkedIn

The engineers had the ideas. What they didn't have was a map of how those ideas connected: the MCAS software, the pilot training, and the certification process were each handled in their own silo.
Nobody owned the relationship between them. And the relationship is what failed.

That gap is the difference between a mind map and a concept map. Most people use the words interchangeably. They are not the same tool, and confusing them is expensive.

Mind mapping (Tony Buzan, 1970s) vs concept mapping (Joseph Novak, Cornell, 1972).
A mind map is hierarchical: a central topic with ideas branching outward. It captures YOUR thinking.
A concept map is relational: cross-links with named, directional connections. It captures HOW THINGS RELATE.

Three reasons that distinction matters more than it looks:

1. Mind maps give the illusion of completeness.
Fifty ideas in bubbles look comprehensive. They aren't. Listing fifty things is not the same as understanding how they connect.

2. Concept maps force you to name the relationship.
"Causes" is not "depends on" is not "blocks."
The verb is the insight. The verb is exactly what mind maps skip.

3. Most decisions don't fail on missing ideas. They fail on missing connections.
Boeing wasn't short on engineering talent. It was short on a single view of how three separate systems depended on each other.
A mind map would have shown each system neatly in its own branch.
A concept map would have surfaced the gap between them.

Buzan gave us a tool to capture thinking.
Novak gave us a tool to test that thinking against reality.

Here's why this matters now: in 2026, AI can generate a 200-node mind map in seconds.
Listing more ideas is no longer an advantage. Everyone can do it instantly.

The advantage belongs to whoever can name the connections between the ideas. That's still a human skill, and it's the one worth building.

Save this for the next time you're making a big decision: don't just list the moving parts. Draw the lines between them, and name what each line does.

Quick gut check: think of the last project that went sideways. Was it because someone missed an idea, or because two teams never mapped how their pieces connected? Curious which one you see more often.

Uttam Dinodia

Uttam Dinodia

Pharmaceutical Business Consultant & Executive Director, A One Afro Limited

Over 22 years in pharmaceutical supply. Helps international manufacturers and Zambian institutions with public tenders, ZAMRA regulatory pathways and distribution.