Lab · Strategy & situational awareness
See the landscape, then move with intent
Wardley Mapping is a strategic practice for visualizing how user needs chain to components and how those components evolve under competitive pressure. Position (visibility vs evolution) turns opinion into a shared picture so teams can argue about the map instead of each other. This page distills a full practitioner guide: when to map, how to scope, anchors, value chains, evolution as a continuum, fit with Domain-Driven Design, team cultures, gameplay, and learning by mapping your own career.
- Situational awareness: a map encodes position and movement, not a static diagram of “our architecture.”
- Evolution is market-driven (0→1), not “how new our repo is”; the “I built it” trap is a rite of passage worth naming early.
- Methodology fit: genesis rewards exploration; commodity rewards industrialization. Mismatched process is self-harm.
- Bridge to DDD: evolution bands suggest core vs supporting vs generic boundaries; strategy and modeling reinforce each other.
Y × X
Axes
Visibility (value to the anchor) vs evolution (competitive maturity). Components slide right over time; climatic patterns mean you run to stand still.
0 → 1
Continuous evolution
Genesis through Deprecated are labels on a spectrum. Early / mid / late within a stage predicts the next disruption.
Map first
Golden rule
Map when the cost of being wrong exceeds the cost of mapping. If failure is cheap, ship and learn instead.
When to map
Triggers & contexts
You do not need a map to cross a familiar room. You need one when the terrain is unfamiliar, contested, or expensive to get wrong.
Conflict resolution
When directions collide (“rewrite in Rust” vs “stay in Node”), people often hold different mental models of the same landscape. Externalize the map so you attack the diagram, not the person.
Build vs buy
Resource limits bite everywhere. A map exposes accidental builds of commodity work, or outsourcing the genesis that should be your edge.
Breaking monoliths
Tracing user needs down to data and operations reveals domain seams. Those seams beat “slice by technical layer” when you need safer service boundaries.
Personal career strategy
You are the anchor; skills are components. Are you over-investing in a commodity skill, or planting seeds in genesis space that could compound?
Golden rule
Create a map when the cost of being wrong is higher than the cost of mapping. If you can fail fast and cheap, just do it. If failure means bankruptcy or years of lost time, map it first.
Doctrine
Phase I: stop self-harm
Before placing anchors, Wardley doctrine checks universal habits. If these are weak, mapping becomes theater instead of alignment.
- Know your users
- Focus on user needs
- Know the details (value chain)
- Understand what is being considered
- Challenge assumptions
- Use a common language
Scoping
The research question
Ask why you are mapping before you draw. You cannot map “the business.” You can only map a bounded problem space with a decision at stake.
Research question
Avoid: “Map our infrastructure.” (too broad: infinite canvas of noise)
Prefer: “Should we migrate our legacy auth service to Auth0?” (decision-bounded)
Granularity of needs
Avoid: “Situational awareness” (too abstract to anchor work)
Prefer: “Reduce customer onboarding time” (measurable, stable enough to design against)
The “why?” ladder
Too abstract
“Be successful”
Strategic
“Increase market share”
Sweet spot (map this)
“Ship mobile app faster”
Too detailed
“Fix typo in header”
Anchor & value chain
Users, needs, dependencies
In Domain-Driven Design terms, this is problem space before solution space: who is served, what outcomes matter, only then how components chain to deliver.
Placement checklist
- Who are you serving? → Anchor at top (visibility 1.0).
- What do they need? → User needs just below the anchor.
- How do you fulfill it? → Components as the dependency chain.
Multi-anchor maps
- ·B2B2C and platforms often need multiple anchors; both belong at high visibility.
- ·Default: place anchors far right (≈0.90–0.92) as ubiquitous actors.
- ·Differentiate by need novelty: a “unique experiences” anchor may sit slightly left of a pure ROI anchor.
- ·Hard limit: do not place anchors below ~0.90; they should not visually compete with genesis/custom innovation.
Value chain vocabulary
User
The person or org with the need (e.g. photo enthusiast).
User need
Outcome they want (e.g. share memories).
Channel
How you reach them: site, app, store.
Value proposition
What you offer against the need.
Key capabilities
What you must excel at (e.g. image processing).
Key dependencies
Enablers: compute, power, practices, legal, marketing.
Visibility is always relative to the anchor. Users perceive value in what is visible; deeper components are costs of doing business until they fail.
Evolution
Stages on a continuous spectrum
Components move right as competition industrializes them. Early / mid / late within a stage signals the next transition, including the “disruption zone” at the trailing edge of product.
Genesis
- •Unique, novel, volatile
- •High failure rate
- •Potential source of worth
Custom built
- •Learning and diverging
- •Rapid change
- •Differentiation
Product
- •Converging standard
- •Competition
- •Feature wars
Commodity
- •Industrialized
- •Volume operations
- •Cost focus
Deprecated
- •Being replaced
- •Migration pressure
- •EOL planning
The “I built it” trap
Evolution measures the market, not your repository age.
Custom code for user login today is often a custom build of a commodity activity. The map shows market reality; the gap to “should be utility” is strategic debt.
Why commodities matter
Commodities enable higher-order innovation: electricity → motors → automation; cloud → new application genres. Stable foundations free attention for the next genesis play.
Methodology match
| Evolution band | Fit |
|---|---|
| Genesis / Custom | Agile / explore: discovery and fast learning |
| Product | Lean / build: compete, optimize, repeat |
| Commodity | Six Sigma / buy: industrialize, outsource |
| Deprecated | Sunset / migrate: controlled wind-down |
Strategic questions by stage
Genesis
Where should we invest?
Innovation and differentiation.
Custom
How do we learn?
Iteration; reduce cost of change to find fit.
Product
How do we compete?
Optimization and credible features.
Commodity
What should we outsource?
Cost and scale; stop bespoke-building utilities.
Deprecated
What should we sunset?
Migration, debt containment, reallocation.
Evolution cheat sheet
| Genesis | Custom | Product | Commodity | Deprecated | |
|---|---|---|---|---|---|
| Ubiquity | Rare | Growing | Common | Essential | Declining |
| Certainty | Uncertain | Learning | Converging | Known / accepted | Obsolete |
| Failure | High / expected | Moderate | Low / disliked | Surprising if it fails | Expected (EOL) |
| Market | Undefined | Forming | Growing | Mature | Sunsetting |
Component types
Activity
“We do X.”
Search, login, compute.
Data
“We have X.”
Profiles, catalog, geospatial assets.
Practice
“How we work.”
CI/CD, review, agile, testing.
Knowledge
“What we know.”
Ranking algorithm, customer insight models.
Map the same label twice under different types when it helps: “Search” as commodity activity vs “ranking algorithm” as genesis knowledge clarifies buy-the-engine, own-the-moat.
Strategy ↔ model
Evolution bands and bounded contexts
| Evolution | DDD classification | Strategy bias |
|---|---|---|
| Genesis / Custom | Core domain | Build: competitive advantage. |
| Product | Supporting domain | Buy if possible: necessary but not differentiating. |
| Commodity / Deprecated | Generic domain | Outsource: utility and sunset. |
People & culture
Pioneers, settlers, town planners
Small teams matter, and matching culture to evolution stage matters alongside headcount. Pioneers suffocate under commodity governance; town planners drown in genesis chaos.
Pioneers
Genesis / Custom
- Comfortable with failure
- High ambiguity tolerance
- Intrinsically motivated
- Question everything
Settlers
Product
- Product-minded
- Customer empathy
- Balance speed and quality
- Strong prioritization
Town planners
Commodity / Deprecated
- Process-oriented
- Metrics-driven
- Scale-focused
- Risk-averse in the right places
Strategic gameplay
Moves on the map
Gameplay is contextual: industrialize, differentiate, bundle, standards games, strangler figs, controlled sunsets, all catalogued in the full guide. Categories help you browse intent before picking a named play.
Positional
Industrialize · Differentiate · Outsource · Build · Buy · Focus · Open source
Accelerators & decelerators
Land and expand · Vertical integration · Commoditize complement · Exploit inertia · FUD
Market & ecosystem
Two-sided market · Bundling / unbundling · Standards game · Ecosystem play · Co-opetition
Defensive & sunset
Tower and moat · Patent / IP · Controlled sunset · Strangler fig · Migration incentive
Example play
Industrialize
Positional play
Move a component toward commodity to reduce cost and increase efficiency.
e.g. Netflix shifting from mailed DVDs to streaming infrastructure.
First map
Map something you know: your career
Anchor on future you
The user is Future You (or family). Needs might include fulfillment, security, creative outlet.
Chain the value
Security might require marketable skills; fulfillment might require creative expression. Decompose honestly.
Place evolution
Genesis hobby (experimental AI art) vs product day-job (React, Node, SQL) vs commodity you should not rebuild (laptop, CSS framework unless that is your play).
Choose plays
Invest in genesis bets, maintain product skills without churn-chasing, accept commodity utilities to free energy.
Further reading & license
- Susanne Kaiser · Combining Domain-Driven Design, Team Topologies, and Wardley Mapping.
- James Duncan · The OSOM (Open Source Operational Model) guide.
- Robert X. Cringely · Accidental Empires: commandos, infantry, police analogy (cultural lineage).
Wardley Mapping is provided under CC BY-SA 4.0.
Wardley Mapping concepts are open under CC BY-SA 4.0. This lab page is a curated digest of a longer guide published on Intelligence.Space; it is not a substitute for the interactive material there when you want the full walkthrough, diagrams, and tooling context.
Open the full guide on Intelligence.SpaceWant to facilitate a mapping session or connect it to delivery?
Initiatives &
Research
Beyond my personal consultancy, I am actively building the future of software delivery and collaboration through these dedicated entities.
api.land
Curated infrastructure and building blocks for modern engineering teams. Providing the modules you need to build faster.
intelligence.space
A research lab re-imagining human-AI collaboration. Building an "Intelligent Space" for the entire lifecycle of systems engineering and learning itself.