Definition
Anchoring is the practice of grounding a Wardley Map in a specific user need. Every map must start with a user need at the top of the value chain — not with the organization's capabilities, products, or technologies, but with what the user actually needs.
Why Anchoring Matters
Anchoring to user needs is both a mapping technique and a doctrine principle. It prevents a common strategic error: building strategy around what the organization happens to produce rather than what users actually need. Maps anchored to organizational capabilities tend to justify existing investments; maps anchored to user needs reveal gaps, redundancies, and opportunities.
The Practice
To anchor a map: 1. Identify the user (who needs something) 2. Identify the need (what they need, in their terms) 3. Place the need at the top of the map 4. Decompose downward: what components are required to meet that need? 5. Continue decomposing until you reach fundamental infrastructure
Connection to Doctrine
"Focus on user needs" is one of the most fundamental doctrine principles. Anchoring is the mechanism by which this principle is enforced in practice — if every map starts with the user, the organization cannot lose sight of why it exists.
Connection to Boyd
The anchoring concept parallels Boyd's emphasis on purpose as the foundation of strategy. Boyd argued that organizations that lose sight of their purpose become internally focused and vulnerable to faster-adapting competitors. Wardley's anchoring enforces external orientation by making the user need the starting point of all strategic analysis.