Skip to content

Wardley

File

This page did not finish loading. Reload to save or share.

Draft saved in this browser

Backup & restore

Start typing — or load an example.

Export
History
Needs… in a component's ⋯ menu rewires dependencies — mouse or touch · snapshot at each strategy review — compare records changed claims

Why a map, and why as code?

A strategy map is a current claim, not a workshop artefact. This one is text: user needs, dependencies and evolution positions in a file, the picture derived — so the next review compares the claim instead of redrawing it.

A Wardley strategic field makes an inspectable claim about a value chain: what the user needs, what each thing needs, and where each component sits from genesis to commodity. The point is the argument: why are we hand-building something the market sells as a utility? What are we treating as settled that is still genuinely novel? Horizontal position is a claim, not a forecast, delivery schedule, or decision plan.

Here the field is a projection of a text file. Vertical position is derived from the dependency chain — user needs above the things they need — rather than pretending the DSL contains a measured visibility value. Dragging a component along the evolution ruler writes its position back into the text as an ordinary undoable edit; the file stays the single source of truth.

Snapshot compare keeps changes legible: moved positions, new and dropped components, and changed dependencies become factual receipts in the next review. Strategy drift becomes an artefact you can inspect, not a memory you argue about. Use Roadmap for delivery commitments, and Paths when different outcomes could stop, pivot, or expand the work. Source: Simon Wardley's mapping work, CC BY-SA.