Skip to content
Source on GitHubVisitors

Wardley map

Map a value chain by how visible each component is to users and how evolved it is.

Diagram · origin tag wardley/map · Strategy & landscape mapping

Availability

Availability per host
HostStateHow to get it
StandalonePrototypeNot yet released
DesktopPrototypeNot yet released
IntelliJ PlatformNot plannedNot planned
Visual Studio CodeNot plannedNot planned
EclipseNot plannedNot planned
ThinkRailNot plannedNot planned
NotionNot plannedNot planned
ClaudeNot plannedNot planned

What it is for

Wardley map (the components of a value chain, placed by their visibility to the user and by their evolution from genesis to commodity, with their dependencies and planned movements)

Why a specialized view helps

The evolution axis puts each component where it is in its life cycle, which is the point of a Wardley map and what a generic diagram leaves out.

File formats

ExtensionFormatReadsWrites
.owm.owmYesYes

Screenshots

The bounded map: both axes labelled, the four evolution bands named along the bottom, components and links drawn. Nothing selected.

Standalone, at a8616b3

What is visible: The bounded map: both axes labelled, the four evolution bands named along the bottom, components and links drawn. Nothing selected.

Why it matters: Every component sits on the two axes that give a Wardley map its meaning, visibility in the value chain and evolution from genesis to commodity, which a generic canvas cannot enforce.

Licence: Apache-2.0

Background

Focus areas

Sources