The Theorist
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 Theorist sits at abstract and systemic, reasoning from principles and how broader forces interconnect.
Typical behaviors
- 01Zooms out to context first (incentives, structure, history, culture) before addressing the specific issue in front of them.
- 02Holds several interacting variables at once rather than isolating a single cause.
- 03Reframes a narrow complaint into a bigger pattern: "this isn't about the missed deadline, it's about how we structure accountability."
- 04Thinks ahead to second- and third-order effects, which can make them slow to endorse a quick fix.
- 05Comfortable with an answer that starts "it depends on how these pieces interact."
Common language
“Zooming out, what's actually driving this?”
“This is part of a bigger pattern, not a one-off.”
“If you change that incentive, it'll ripple through the rest of the system.”
“The issue is structural, not this one instance.”
“How does this interact with X and Y?”
Strengths
Theorists catch root causes that are genuinely systemic, ones a narrower read would misdiagnose as a one-off. That's valuable anywhere multiple forces are actually interacting: strategy, culture change, org design. They're often the person who stops a team from fixing the symptom and calling it done.
Weaknesses
The same range that lets them see the system can make their explanations hard to pin down or test. "It's structural" can be true and also unfalsifiable if it never lands on a specific, checkable claim. And because there's always another interconnection worth considering, Theorists can struggle to call an analysis finished, and the elegant systemic explanation crowds out a simpler fix that would have worked fine.
The Tracer wants one specific, verifiable cause tied to one specific effect. To a Theorist, that can look like fixating on a single data point and missing the pattern it's part of. To a Tracer, "it's structural" can sound like a way to avoid ever naming what actually happened. Both are trying to be rigorous. They just disagree about what counts as evidence.
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.
