DM-15 Wardley mapping
Positions the components of a service by visibility to the user and by evolution stage, with dependency lines, and produces a two-axis map.
What it does
Positions the components of a service by visibility to the user and by evolution stage (genesis, custom build, product, commodity), with dependency lines. Artefact: a two-axis map; read components placed at the wrong stage for how they are treated.
When to use it
Use when you want to see which components of a service are treated as if they were at a different stage of maturity than they are.
When it does not fit
Placement on the evolution axis cannot be agreed or evidenced, so the map records opinion only.
Result format
The result is a two-axis map with visibility to the user on one axis and evolution stage (genesis, custom build, product, commodity) on the other. Each component of the service is placed on the map with dependency lines between components, and the components placed at the wrong stage for how they are treated are named.
Requirements on the material
| Property | Requirement type | Requirement |
|---|---|---|
| Unit of analysis | Always applies | requires=topic |
| Appraises source credibility | Applies in some cases | no |
Not restricted on: Structure, Content type, Variable types, Time structure, How the sample was chosen, Level of detail available, Number of sources, Whether sources can be joined, Amount of material, Known data problems, Producer interest, Source dependence, Origin, Document genre, Language, Personal information, Security classification, Licence.
| Minimum material | A defined user and need, the components that meet it, and a judgement of each evolution stage. |
|---|---|
| Additional sources needed | none |
| Not for (rules) | none |
| Not for (text) | Placement on the evolution axis cannot be agreed or evidenced, so the map records opinion only. |
Choosing and ordering
| Kind of technique | Primary technique, runs in step 5.3 |
|---|---|
| Phase tag | analyse |
| Other phase tags | frame |
| Kind of finding | gap; pattern |
| Question answered | what; which option |
| Strongest statement it supports | describe |
| Needs as input |
|
| Makes as output |
|
| Must exist first | None |
| Loop target | return to analyse |
Library checks by stakes
Each stakes level includes the checks of the level below it. Checks that need a person apply at high stakes only, so the process leaves them out at lower stakes (decision 38). Repeatability: judgement dependent.
| Stakes | Check | Person involved | Counts as a different method |
|---|---|---|---|
| exploratory | spot check | optional | no |
| decision-informing | spot check | optional | no |
| decision-informing | assumption and limitation statement | none | no |
| high-stakes | spot check | optional | no |
| high-stakes | assumption and limitation statement | none | no |
| high-stakes | expert review | needed | no |
| high-stakes | independent review | needed | no |
Failure modes and limits
| Model suitability | human judgement required |
|---|---|
| Typical model failure | Places components on the evolution axis from assumption and presents the map as if it recorded fact. |
| Error sources | input data; coder or rater judgement; language model |
| Certainty limits | Critics say the map can turn assumptions into apparent facts; no independent evaluation was found, so evolution placements carry risk of bias. |
Related techniques
- pairs with DM-04 Value chain analysis (Porter): A value chain gives the activities that the map places by stage
- pairs with DM-17 Process mapping (flowcharts, swimlane diagrams, value stream maps): Process mapping gives the dependencies between components
Evidence and tag basis
Practice. The source page has notices about self-published sources and unsupported statements; critics say it can turn assumptions into apparent facts; no independent evaluation found. (Wikipedia, Wardley map)
Tag basis: input profile inference; selection inference; sequencing inference; robustness inference. All tag values are inference unless a source is named.