THE IDEA
Drawing the system to see the system
Systems are invisible. You can see the people, the products, the events - but you can’t see the system itself. The flows of information, the feedback loops, the delays, the power dynamics, the incentives - they’re all there, shaping every outcome, and none of them are visible to the naked eye.
Systems mapping is the practice of making them visible. It’s a broad category that includes many different techniques - causal loop diagrams, stock and flow diagrams, stakeholder maps, rich pictures, network diagrams - but they all share the same purpose: get the system out of people’s heads and onto a surface where it can be examined, debated, and understood.
The insight behind all systems mapping is that drawing the system changes how you see it. When the relationships are in your head, you see them partially and selectively, filtered by your own position and assumptions. When they’re on a wall, you see connections you missed, feedback you ignored, and gaps in your understanding that were invisible as long as the model stayed internal. The map isn’t the territory - but making the map is how you discover that your idea of the territory was wrong.
IN PRACTICE
Making the invisible negotiable
A charity working on youth unemployment brings together employers, training providers, young people, local government, and funders. Each has a different understanding of the problem. The charity facilitates a mapping session where everyone draws their part of the system on a shared wall. The employers see barriers the training providers didn’t know about. The young people describe a journey that nobody else had mapped. The funders see duplication they’d been inadvertently creating. Nobody changes their mind about their own piece. But everyone can now see the whole picture, and the whole picture changes which interventions seem worthwhile.
A product team maps the user journey - not the idealised one in the design document, but the real one. They include the workarounds, the moments of confusion, the support tickets, the features that get ignored. The map reveals that users consistently skip a step the team considers critical, and the step they spend most time on isn’t in the journey at all. The product roadmap changes, not because of new data, but because the map made existing data impossible to ignore.
A family going through a difficult transition - a divorce, a move, a bereavement - sits down with a counsellor and draws a “rich picture” of everyone involved and what they need. It’s messy, emotional, and imprecise. But it surfaces things that conversation alone didn’t: a child who feels caught between two households, a grandparent who’s been left out, a practical need that everyone assumed someone else was handling. The map doesn’t solve anything. It makes visible what needs to be solved.
WORKING WITH THIS
The practice of drawing together
The most important thing about systems mapping isn’t the technique. It’s who’s in the room. A map drawn by one person reflects one perspective. A map drawn by the people who live in the system reflects the system. Get the right people together, give them a wall and some markers, and the conversation that emerges is usually more valuable than the map itself.
Start simple. Put the thing you’re trying to understand in the middle. Ask: what affects this? What does this affect? Draw the connections. Don’t worry about formal notation or the “right” way to do it. The goal is shared understanding, not a publishable diagram.
The biggest mistake is treating the map as finished. A systems map is a snapshot of current understanding. It should be revisited, challenged, and redrawn as understanding changes. Tape it to a wall where people can see it, add to it, argue with it. The moment it gets filed away in a slide deck, it stops being a thinking tool and becomes an artefact. Keep it alive, keep it messy, and keep asking: what’s missing?
THE INSIGHT
The line to remember
You can’t change what you can’t see, and you can’t see a system by looking at its parts. You have to draw the connections.
RECOGNITION
When this is in play
You need systems mapping when different people describe the same situation in completely different ways. When a problem feels overwhelming because nobody can see the whole picture. When interventions keep producing unexpected results because the connections weren’t visible. When a team has all the information it needs but can’t assemble it into understanding. When the phrase “it’s more complicated than that” keeps being said but nobody draws what “more complicated” looks like.