It Takes a Social System to Map a Social System

✨ It Needs to Be a True Collaboration

Social System Mapping is more of an art than a science. It’s the art of process — one that begins by understanding the purpose and aims of a collaborative, action-oriented, or intentional network. From there, it’s about learning what kinds of relational and systemic awareness might help the network see itself more clearly, so it can learn and act together with greater coherence.

Then comes the craft of translation — distilling those needs all the way down into spreadsheets and data flows, designing questions that will gather the right information, and ultimately creating a map that’s not just a diagram, but a shared space for insight and conversation. Something we can look at together, explore, tell stories through, and derive meaning from.

This is a process that spans a wide range of mental skills — and most of us don’t possess all of them.

Most of the time, creating a truly useful Social System Map requires a minimum of four different kinds of thinkers. We call these the Thinking Hats.

• One listens and inspires — drawing out people’s imaginations and intuiting what kind of information might help a community grow. This is an imaginative, people-y, connective kind of thinker. We call this Hat the Visionary. The Visionary generates energy and possibility before there’s anything to look at.
• One navigates the technical tools — setting up interfaces, shaping data flows, solving problems with systems logic. This is a tech-y, detail-savvy, implementation-focused kind of thinker. We call this Hat the Technician. The Technician takes the energy generated by the Visionary and translates it into something tangible — something the rest of us can see.
• One brings systems thinking and inquiry into play — asking deep questions, noticing patterns, helping others make meaning from the map once it’s created. This is a conceptual, teacher-y, pattern-seeking kind of thinker. We call this Hat the SenseMaker. The SenseMaker helps the network reflect, learn, and make better choices using the map we can now explore together.
• And one bridges them all — helping the community stay connected to why the map matters, surfacing insights in ways that resonate, and rippling meaning in and out of the network. This is a connective, reframing, meaning-weaving kind of thinker. We call this Hat the StoryTeller. The StoryTeller is present at every stage — inviting people in, reflecting back what’s emerging, and helping others find their way in.

Of course, there are more than four kinds of thinkers. Many other ways of thinking contribute to good mapping work. But in our experience, without at least these four orientations in the mix, a project tends to falter. The potential it holds remains unrealized.

And it’s rare — really rare — for one person to be strong in all four areas. Even I (Christine), who often have to wear all the Hats at once, find it hard to perceive and process well from more than one of them at a time. If I’m not clear about which Hat I need to be wearing in a given moment, I can find myself spinning in circles. It’s part of why Social System Mapping is inherently, and inevitably, collaborative.

You may have noticed that the Hats correspond roughly with the three phases of mapping — Envisioning, Mapping, and SenseMaking (or more simply, Before, During, After). And while they’re all involved throughout, each phase emphasizes a different Hat. Each phase is best led by someone whose strength aligns with its focus.

These Hats — these roles — also require different kinds of knowledge and attention. And in the name of true collaboration, where each person brings their own strength to the table without needing to master everyone else’s domain, we’ve structured this knowledge base to align with the Thinking Hats.

So as you dig in, try to notice which Hat you’re wearing. Let that guide where you begin — and what you look for.

🎩 Key Driving Roles — or “Thinking Hats”

Whether they’re filled by one person or shared across a group, a strong mapping project requires someone to take responsibility for each of the following roles:

🟣 Visionary

Catalyzes the mapping process by helping others see its potential — before there’s anything to look at. Guides purpose, gathers people, inspires the process forward.

🔵 Technician

Takes member lists and survey designs and turns them into a functioning interface in sumApp. Translates data from sumApp into a meaningful, interactive Kumu map.

🟢 SenseMaker

Helps the community read and learn from the map. Brings systems awareness, asks useful questions, and helps turn visuals into shared understanding.

🟡 StoryTeller

Bridges all phases and roles. Helps people stay connected to the why, reflects what’s emerging, translates between Hats, and connects the process to the broader network’s story.

👥 Other Key Roles

Ambassadors / Advocates

Visionaries need others to envision with. Members of the network need to feel part of the process. Many successful projects gather a subgroup — sometimes called Ambassadors, Pilot-Testers, Design Team, or Advocates — to help shape the survey, offer feedback, and encourage participation.

You might convene them for a group session (once or repeatedly), or engage them one-on-one. It all depends on your network’s size, energy, and context.

Diversity matters here. You can’t surface the needs of the whole if you’re only hearing from a few familiar voices. But if fanfare is hard to generate — don’t worry. Start with who’s willing. Iterate from there.

Network Members

You can’t map much without participation. You have to consider the value to members at every stage. Start with those who are interested. Run a pilot. Create a prototype. Let people see themselves in the early map — and enlist them in spreading the word.

Once you have a map, invite others to make sense of it with you. That kicks off the next iteration. And the cycle begins again.

🌱 The Opportunity

A Social System Map is more than a tool — it’s a practice. It gives us a chance to work across real difference. Not just demographic or ideological difference — but cognitive difference. The Hats represent different languages, different strengths, different ways of making meaning.

In network-weaving spaces, we talk a lot about the importance of bridging across difference. But we still tend to gravitate toward people who think like we do. And that can make true collaboration difficult — especially when our thinking styles start to bump into each other.

I used to say that my job was to translate the infinite, abstract, non-linear, multi-dimensional longings of Visionaries into the finite, structured, single-dimensional bits and bytes of computer logic — so the Technicians had tools to work with — and then translate that structure back out again into abstract, interactive visuals that allow people to see what they couldn’t see before.

That meant learning to navigate four wildly different languages, all at once.

The hardest part was that most people didn’t realize those other languages existed. They assumed their way of thinking was the only one in play — the only one that mattered. The mental load of translating constantly, without acknowledgment, could get heavy. And sometimes, I got cranky.

But here’s the gift:
This work can be a powerful practice — if you let it.
It invites you to slow down. To ask better questions. To listen more deeply. To become clearer, more transparent, more curious.
It teaches you to co-create from difference.

I love that you can’t do this alone.
I love that it demands we stretch, together.
I love that it makes us more than the sum of our parts.