Get in Touch
Sign-In
Quadrant four of four

The Mapper

ConcreteSystemic

Two people can look at the same problem and read it completely differently. It isn't because one is right and the other wrong; it's because they're running a different kind of analysis. Sense Making is the teamscape dimension that maps this: how abstract or concrete your reasoning is, and how linear or systemic it is.

The Mapper sits at concrete and systemic, seeing how specific pieces of a problem affect each other.

abstract linear
systemic concrete

Typical behaviors

  • 01Maps how real, specific elements (people, teams, tools, decisions) actually influence each other.
  • 02Is comfortable with a messy web of relationships, as long as every connection is grounded in something real, not theoretical.
  • 03Often ends up diagramming "if this changes, here's everyone and everything it touches."
  • 04Thrives on genuinely cross-functional problems where the pieces really are interdependent.
  • 05Resists naming a single root cause when the honest answer is that several things are interacting.

Common language

“This connects to that, which affects this other thing.”

“It's not one cause. It's how these pieces interact.”

“Let's map out who's actually involved.”

“That team's decision touches these three things.”

“It depends which part of the system you mean.”

Strengths

Mappers are strong wherever a problem is genuinely interconnected and a single-cause explanation would be wrong. Because their maps are built from specifics rather than theory, they're checkable: you can point to each connection and confirm it's real. That also makes them good at spotting the unintended consequence of a change before it happens.

Weaknesses

A map with no clear priority is hard to act on. If everything connects to everything, a Mapper can struggle to say where to start, and can resist the simplifying rule that would make the picture usable, because it feels like it's leaving something out. To people who need one clear next step, this can feel like analysis without a conclusion.

Likely to clash with

The Architect

Read the Architect page →

The Architect wants one clean, principle-driven sequence. To a Mapper, that can look like oversimplifying a situation that doesn't actually run in a straight line. To an Architect, the Mapper's web of connections can look ungrounded: always more nuance, never a rule to act on. Both are right about the piece they're looking at.

The other three quadrants

Where would you place your last team disagreement?

Sense Making is one of the teamscape dimensions. A short walkthrough maps your team across all of them.

Book a walkthrough