Last month I facilitated a two-day systems mapping session with a twelve-person product team at a Tehran-based logistics startup. Here’s what the process actually looks like — and why it consistently surfaces insights that months of sprint retrospectives miss.
Day One: Divergent Mapping
We begin with individual mapping. Each participant draws their mental model of the product’s core system — the actors, the flows, the bottlenecks — on a large sheet of butcher paper. No templates, no frameworks, just markers and intuition. The exercise is deliberately unstructured because the goal isn’t accuracy; it’s surfacing the invisible assumptions each person carries.
After an hour, the sheets go up on the wall. The team walks the gallery, silently, placing small dots on elements that surprise them. The dots cluster predictably: engineering sees a different system than customer success, which sees a different system than the founders. These gaps are not bugs — they’re the workshop’s raw material.
Day Two: Convergent Synthesis
On the second day, the team builds a single shared map. This is where the real negotiation happens — which loops are reinforcing, which are balancing, where the delays live, and where the leverage points hide. I facilitate with a simple rule: every arrow must be justified by observable evidence, not opinion. This constraint slows the conversation but dramatically raises the quality of the output.
By midday, the shared map typically reveals two or three “invisible engines” — feedback loops the team was unconsciously managing through heroic effort that could be managed through design instead. In this case, the team discovered that their driver onboarding delay was creating a reinforcing churn loop that no amount of customer discount could offset.
Key Takeaways
- Individual maps reveal hidden assumptions faster than any survey or interview.
- The gap between maps — not any single map — is where the richest insights live.
- Requiring observable evidence for every causal arrow prevents the map from becoming a wishful-thinking diagram.
- Two days of mapping often replaces weeks of unfocused discovery sprints.
If your team is navigating a complex growth challenge and the usual frameworks feel insufficient, a systems mapping session might be the most efficient way to find clarity. It’s the foundation exercise in my Problem-Solving Game Workshop — and it works because systems see what silos cannot.
Leave a Reply