THE IDEA
The people are the expertise
A system map drawn by an expert from outside the system is limited by what the expert can see. It might be technically sophisticated. It might use the right notation. But it will miss the dynamics that only the people inside the system experience - the informal workarounds, the hidden relationships, the unwritten rules, the things that matter but don’t show up in any data set.
Participatory systems mapping puts the pen in the hands of the people who live in the system. A facilitator guides the process, but the knowledge comes from the participants. They draw what they see, argue about what’s connected to what, discover that they hold different pictures of the same reality, and gradually assemble a shared understanding that no individual had before.
The map is valuable. The process is more valuable. When people build a system map together, they develop shared language, shared understanding, and shared ownership of the analysis. They see connections they’d missed. They understand each other’s perspectives. They arrive at insights that no amount of expert analysis would have produced, because the insights come from the collision of different lived experiences of the same system.
IN PRACTICE
Drawing together, seeing together
A neighbourhood health initiative brings together GPs, social workers, community leaders, patients, and local government officers to map the system of support for elderly residents. Each group draws their part of the picture. The GPs see medical needs. The social workers see isolation and housing. The community leaders see informal networks of care. The patients see a confusing maze of services that don’t connect. When the separate views are assembled on a shared wall, the group sees something none of them saw alone: the formal services are duplicating some functions and missing others entirely, while the informal community networks are doing critical work that nobody funds or supports.
A school improvement team includes teachers, students, parents, and administrators in mapping why attendance is declining. The administrators’ map focuses on processes and data. The teachers’ map focuses on curriculum engagement. The parents’ map focuses on morning routines and transport. The students’ map focuses on social dynamics and feeling unsafe in certain corridors. The combined map reveals that the biggest driver isn’t disengagement with learning - it’s a physical safety concern in a specific part of the building that only the students knew about.
A product team invites customer service agents, engineers, and actual customers to map the user journey together. The engineering map shows the technical flow. The customer service map shows where people get stuck and call for help. The customer map shows a completely different journey from the one either internal team imagined. The most critical insight: customers use the product in an order that the design didn’t intend, creating frustration at a point the product team thought was straightforward.
WORKING WITH THIS
Running a participatory mapping session
Choose your participants with care. Include people from different positions in the system - not just decision-makers but frontline workers, service users, and people affected by the system’s outputs. The diversity of perspective is what makes the map rich.
Start with a shared question: “What’s happening in this system?” or “Why does this pattern keep occurring?” Give people materials - markers, sticky notes, a large surface. Let them draw individually first, then share, then integrate. The disagreements are as valuable as the agreements - they reveal where the system looks different from different positions.
Facilitate for inclusion, not consensus. The goal isn’t to produce one “correct” map. It’s to produce a shared map that holds multiple truths. Some connections will be debated. Some will be surprising. Some will be uncomfortable. All of this is the process working. The map should be messy, contested, and alive - because the system it represents is all of those things.
THE INSIGHT
The line to remember
The best map of a system isn’t drawn by the smartest person in the room. It’s drawn by everyone in the room together - because the system is bigger than any single view.
RECOGNITION
When this is in play
You need participatory mapping when the experts’ analysis doesn’t match the experience of the people living in the system. When a map drawn from data alone misses the dynamics that everyone on the ground knows about. When different stakeholders tell completely different stories about the same situation and nobody has assembled them into a shared picture. When the people most affected by a problem haven’t been involved in understanding it.