The Architect
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 Architect sits at abstract and linear, building a stepwise case from a rule or a framework.
Typical behaviors
- 01Reaches for a framework or principle before getting into the specifics of the problem.
- 02Wants the rule defined before proceeding, and resists moving forward on an undefined premise.
- 03Breaks an argument into ordered steps: if the principle holds, then this follows, then this.
- 04Is often the one drafting the decision tree, the process doc, or the meeting agenda.
- 05Prefers to settle "what are we even applying here" before "what do we do about it."
Common language
“So what's the underlying principle?”
“If we accept X, then it follows that Y.”
“Let's define the framework before we get into specifics.”
“What's the rule we're actually applying here?”
“Step one, step two, step three.”
Strengths
The Architect turns a messy, one-off argument into something repeatable: a process or framework other people can run without them in the room. Because they reason from a principle rather than the specific case, their explanations scale: state the rule once and it covers the next ten situations, not just this one. That makes them strong at governance, onboarding, and any decision that needs to hold up consistently across a team.
Weaknesses
The same instinct that makes them systematic can make them rigid. An Architect can force a genuinely messy, contradictory situation into a tidy sequence that doesn't actually hold, and can miss the detail on the ground that contradicts the framework, because the framework already feels settled. To people working from facts rather than principles, this reads as theoretical, or as answering a different question than the one that was asked.
The Mapper works from concrete, systemic detail: specific pieces of a real situation, connected in a web rather than a line. To an Architect, that can look like there's no rule being applied at all, just an ever-expanding set of connections that never resolves into a clean answer. To a Mapper, the Architect's stepwise case can look like it's flattening a genuinely tangled situation into a straight line it doesn't fit. Neither is wrong about what they're seeing. They're just not looking for the same thing.
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.
