📖 Business
Three Maps Framework
A navigation framework for staff-plus engineers operating in organizational ambiguity. Tanya Reilly argues that as you grow in seniority, you need increasingly sophisticated mental models of your environment. Junior engineers only need to know where they sit. Senior engineers need to understand the terrain. Staff engineers need all three maps — locator, topographical, and treasure — to decide where to invest their expensive, finite time. Without all three, you risk solving the wrong problems, underestimating difficulty, or optimizing locally while strategic opportunities pass you by.
2
Minutes
2
Concepts
+45
XP
1
How It Works
Three maps, each building on the last:
- Locator Map — Where are you in the org? Who are your stakeholders, your reporting chain, the teams your decisions affect? What's your actual scope vs. your perceived scope? Without this, you solve wrong-scope problems — either too narrow (optimizing your team's code while the architecture crumbles) or too broad (redesigning systems you have no mandate to touch).
- Topographical Map — What's the terrain? The technical debt landscape, team dynamics, political minefields, org priorities, what's easy and what's deceptively hard. This is the map that tells you "migrating that service looks simple but three teams depend on its undocumented behavior." Without this, you underestimate difficulty and commit to timelines that blow up.
- Treasure Map — Where's the value? The highest-impact problems, the strategic bets leadership cares about, the work the org desperately needs but nobody is doing. This is what separates staff engineers from senior engineers — the ability to identify and pursue the most valuable work rather than just the most interesting or most visible work.
The maps must be actively maintained. Organizations change constantly — reorgs, new priorities, departures, acquisitions. A map from six months ago is dangerously stale.