Contents
In 1942, engineers working on wartime logistics could not solve some problems with speeches. The system was too large: ships, ports, factories, convoys, fuel, weather, spare parts, enemy movement. The work became visible through maps, boards, flows, and status rooms.
The visualization did not simplify the war. It simplified the conversation enough for decisions to happen.
The same pattern appears in much smaller rooms.
The Story
Tom Wujec’s TED talk uses a deceptively ordinary exercise: ask people to draw how to make toast. The drawings expose how people model systems differently. Some focus on objects. Some focus on sequence. Some include the human. Some omit the power source.
The point is not toast. The point is that language often hides model differences.
A leadership team says it wants to improve “customer onboarding.” Everyone agrees. The phrase feels clear. Then someone maps the current onboarding process. The map has seventeen handoffs, four duplicated data entries, two invisible approval steps, and no owner for the moment when the customer gets confused.
Before the diagram, the team agreed. After the diagram, they finally understood what they had agreed about.
Three Ways This Appears
In everyday life: A couple argues about household work. Both say the division is unfair. When they map the recurring tasks, invisible planning labor appears: remembering appointments, noticing empty supplies, anticipating deadlines. The argument changes because the system becomes visible.
In technology: A team claims the deployment process is simple. A sequence diagram reveals hidden manual checks, undocumented permissions, and one engineer who is effectively the release system.
In organizations: A company says strategy is blocked by execution. A dependency map shows the opposite: execution is blocked by unresolved strategic contradictions.
The Pattern
Diagrams reduce the cost of shared attention.
A verbal discussion forces each person to hold a model privately while comparing it to other people’s words. A diagram externalizes the model. Once externalized, it can be corrected, challenged, annotated, and improved.
The diagram is not evidence by itself. It is a negotiation surface for evidence.
The Cross-Domain Connection: Cartography
Maps changed exploration because they allowed knowledge to accumulate outside any single traveler. A coastline seen by one ship could be corrected by another. The map became a shared memory system.
Process diagrams do the same for organizations. They let experience accumulate beyond individual memory. They also show where the official map differs from the territory people actually travel.
The Framework: Model Externalization
Why This Matters Outside Technology
Any repeated argument may be a mapping problem. People are often disagreeing not about values but about the system they believe exists. Until the model is externalized, the disagreement stays personal.
Drawing is not childish. It is one of the fastest ways to make hidden structure accountable.
The Memorable Sentence
A diagram is where vague agreement goes to become useful disagreement.
Closing Question
What process in your work is still being debated in words because nobody has forced the system onto a page?
- Wujec, T. (2013). Got a wicked problem? First, tell me how you make toast. TEDGlobal 2013.
- Larkin, J.H., & Simon, H.A. (1987). Why a diagram is sometimes worth ten thousand words. Cognitive Science.
- Norman, D.A. (2013). The Design of Everyday Things. Basic Books.
By 2031, AI will generate diagrams instantly, but the valuable diagram will still be the one that changes the conversation. The test is whether the picture exposes dependencies, disagreements, and missing owners that prose had allowed the room to avoid.