EditorialDiagramProduct & Planning
Editorial Wardley Map Designer — No Shadows, No Mermaid Slop
Map an eight-component value chain against Genesis, Custom-built, Product and Commodity. Explore an illustrative search capability moving toward product maturity while keeping commodity infrastructure in the background.
Take it with you
Free PNG includes an EditorialDiagram watermark.
Layout Grammar & Anti-Patterns
Four rules for this diagram
- 01
Use qualitative evolution bands on the horizontal axis and user visibility on the vertical axis. Position is the data; neither axis is a numerical maturity score.
- 02
Draw components as small circles with centered names above them. Stack vertical-axis words horizontally rather than rotating the text.
- 03
Use thin, straight dependency links without arrowheads. These links are the explicit exception to orthogonal runtime-architecture connectors.
- 04
Reserve accent for one evolving component and its dashed right-pointing movement arrow. Explain the movement in a bottom legend, not a redundant label over the arrow.
Three mistakes to avoid
- Treating evolution as a 0–10 score implies measurements that the map does not contain.
- A left-pointing evolution arrow contradicts movement toward commodity.
- Using request/response arrows and protocols turns a strategy value chain into an inaccurate architecture diagram.
Engineer vs. Executive
The two renders use the same illustrative source. Executive mode groups detail deliberately; read the captions before using an overview for a technical review.
Eight positioned components expose the complete illustrative value chain and nine dependencies.
Five components retain the strategic search narrative without the secondary infrastructure detail.
When to use another diagram instead
System Architecture Diagram
Use architecture when the question is runtime connectivity or service topology.
Gantt Chart
Use a Gantt chart when a build-or-buy decision needs a dated implementation plan.
Sankey Diagram
Use Sankey when the decision depends on measured budget allocation rather than qualitative evolution positions.
Questions about this diagram
Does the map measure maturity numerically?
No. Genesis, Custom-built, Product and Commodity are qualitative evolution stages, and vertical position represents visibility in the user’s value chain. The sample positions are illustrative strategy assumptions. They are not market research, a maturity score or a claim about your organization.
Why are dependency links diagonal when other tools use orthogonal routing?
A Wardley component’s horizontal and vertical position carries meaning. Moving it just to fit an elbow would change the map. The reference therefore allows straight dependency links with no arrowheads; only the dashed evolution arrow points right toward a more commoditized stage.
What is retained in the Executive value chain?
The overview keeps Customer experience, Product search, Ranking model, Catalog and Compute at their existing map positions. Checkout, Identity and Database detail are summarized. The evolving search component and its right-pointing movement remain visible in both views.
Worked examples use illustrative data. Edited sources require an AI provider; cached previews are ready immediately.
Cached examples are free. Starter Pack is $9.9 once; Pro Pass is $8.9 per month. Every generation costs 10 credits, including one automatic geometry repair. Pricing