Chapter 2: Three Maps
tsep situational-awareness locator-map topographical-map treasure-map westrum org-culture local-maximum
Status: Notes complete
Overview
A staff engineer must navigate an organization as well as a codebase. Chapter 2 introduces three mental maps that provide the situational awareness needed to operate effectively at broad scope. Without these maps, staff engineers see only their local context — optimizing their own team while missing organizational realities that make their work succeed or fail.
The central argument: technical decisions are made inside an organizational context. Understanding that context — where you fit, what the terrain looks like, where the destination is — is as important as technical skill. The three maps are not things you build once; they require ongoing maintenance as organizations change.
Core Concepts
Locator map: A sense of where you (your team, your system, your project) fit in the broader organizational and technical landscape. Used to avoid local maxima.
Topographical map: A detailed understanding of your organization’s culture — how power flows, how decisions get made, where the obstacles and shortcuts are.
Treasure map: An understanding of where the organization is headed technically — the direction, the destination, and the path. Includes understanding why the direction matters.
Local maximum: Doing the best possible work in your immediate context while missing larger opportunities or creating broader problems. A team can be highly effective at something that doesn’t matter.
Westrum typology: A model of organizational culture with three categories — Pathological, Bureaucratic, and Generative — based on how the organization processes information and handles failure.
Shadow org chart: The informal power structure that often determines how decisions really get made, distinct from the formal org chart.
Map 1: The Locator Map
The locator map answers: “Where are we in the larger picture?”
Purpose
Without perspective, teams fall into the trap of the local maximum: they work hard, optimize everything in their domain, and get very good at something that doesn’t matter. A team that owns a slow internal tool may spend a year making it 10x faster — without realizing the organization has already decided to replace it.
The locator map prevents this by keeping you aware of:
- How your team’s work connects to the broader mission
- What other teams and systems depend on you (and what you depend on)
- What your organization’s current priorities are and how your work ranks among them
- What’s happening in adjacent areas that will affect you
Building a Locator Map
- Read engineering org announcements and all-hands notes
- Understand who your “customers” are (internal and external)
- Know the key metrics your organization cares about and which ones your team affects
- Have relationships with people in other parts of the org who can tell you what they’re seeing
Map 2: The Topographical Map
The topographical map answers: “What is it like to get things done here?”
Culture Axes
Organizations sit somewhere on each of these six spectrums:
| Axis | One end | Other end | What it affects |
|---|---|---|---|
| Information sharing | Secret | Open | How much context you can gather; who you need to ask |
| Communication style | Oral | Written | Where decisions are recorded; how you influence remotely |
| Decision-making | Top-down | Bottom-up | Who you need buy-in from; how much bottom-up consensus matters |
| Change pace | Fast/reactive | Deliberate/slow | How long to get buy-in; risk tolerance for mistakes |
| Access | Back channels | Front doors | Whether relationships or process get things done |
| Resource availability | Allocated | Available | Whether teams have slack or are always at capacity |
| Social capital | Liquid (transferable) | Crystallized (position-based) | Whether influence moves with you or stays in a role |
Westrum Organizational Typology
| Type | Cooperation | Failure handling | Information flow |
|---|---|---|---|
| Pathological | Discouraged | Scapegoating | Withheld |
| Bureaucratic | Tolerated | Ignored | Allowed through narrow channels |
| Generative | Encouraged | Inquired into | Actively sought |
Generative organizations learn faster and recover from failure better. Westrum’s research links this typology to software delivery performance (see DORA research).
Obstacles in the Terrain
Chasms: Gaps between teams or systems that nobody bridges. Information, work, or help can fall into a chasm and disappear.
Fortresses: Teams or individuals who protect their domain aggressively. Information doesn’t cross the walls; getting anything from them requires special effort.
Disputed territory: Areas where multiple teams claim ownership or where ownership is genuinely unclear. Common source of projects that get blocked or never happen.
Shadow Org Chart
The formal org chart shows who reports to whom. The shadow org chart shows who actually influences decisions. Understanding the shadow org chart means knowing:
- Who do people consult before big decisions?
- Whose objection can kill a project?
- Whose approval is needed even if they’re not technically in the review chain?
- Which informal networks shape how work gets prioritized?
Building relationships in the shadow org chart (without manipulating it) is a critical skill for staff engineers who need to move work across organizational boundaries.
Map 3: The Treasure Map
The treasure map answers: “Where are we going, and why?”
The Tech Tree Analogy
Like a technology tree in a strategy game, an organization’s technical trajectory has dependencies: you can’t build capability C until you have B, and you can’t have B until you have A. A treasure map gives you visibility into:
- What the organization is trying to achieve technically (the destination)
- What steps are needed to get there (the path)
- What the dependencies are (what must happen before what)
- Why the direction was chosen (the reasoning, which may change)
Why This Matters for Staff Engineers
Staff engineers are often assigned to drive parts of the journey toward the destination. Without a treasure map:
- You don’t know if your project is on the critical path or a sideshow
- You can’t make good decisions about trade-offs (is this worth slowing down the migration?)
- You can’t explain to your team why the work matters
- You’re vulnerable to being surprised by changes in direction
Sharing the Map
One of the most valuable things a staff engineer can do is make a treasure map visible to others — especially to teams working on components of the journey who can’t see how it fits together. This isn’t about communication for its own sake; it’s about enabling better decisions. Teams who understand the destination can make local decisions that align with it.
Key Takeaways
- Three maps provide the situational awareness staff engineers need: Locator (where you are), Topographical (what the terrain is like), Treasure (where you’re going).
- Without a locator map, you risk optimizing a local maximum — doing excellent work on something that doesn’t matter.
- The topographical map captures organizational culture across 6 axes and the informal power structure (shadow org chart).
- Westrum’s typology (Pathological / Bureaucratic / Generative) predicts how well an org handles information and failure.
- Common terrain obstacles: chasms (gaps), fortresses (closed-off teams), disputed territory (unclear ownership).
- The treasure map lets you connect today’s work to the long-term direction — and helps others do the same.
- All three maps need ongoing maintenance as organizations evolve.
Related Resources
- ch03-creating-big-picture — Building the treasure map (technical vision and strategy)
- ch01-what-would-you-say — How scope and archetypes shape which maps matter most
- ch05-leading-big-projects — How topographical map knowledge navigates project obstacles