The Wardley Map PR is in draft, working through code review. Here’s what’s on the roadmap.
Immediate: Regions
The most requested feature. Regions let you group components into market segments or areas of focus:
wardleyMap
region "Core Platform" [0.3, 0.4, 0.8, 0.9]
component api "API" [0.5, 0.7]
component db "Database" [0.6, 0.5]
This requires grammar extensions and renderer updates to draw bounded areas behind components. High priority.
Pipelines
Horizontal groupings at the same visibility level. Common pattern for showing multiple implementations of the same capability:
wardleyMap
pipeline "Data Storage" [0.6]
component postgres "PostgreSQL" [0.7]
component mongo "MongoDB" [0.5]
component custom "Custom Store" [0.2]
Annotations
Notes, callouts, movement arrows. Strategic maps need context:
wardleyMap
component legacy "Legacy System" [0.8, 0.6]
note legacy "Migrating Q2"
movement legacy [0.4, 0.6]
Inertia Indicators
Show resistance to change. Critical for strategy discussions:
wardleyMap
component erp "ERP System" [0.75, 0.5] inertia
Beyond Wardley: Cynefin
Cynefin is another strategic framework - different axes, different purpose. Four domains: Clear, Complicated, Complex, Chaotic.
Same architecture pattern. Different grammar. Could share rendering infrastructure.
cynefin
domain complex
item "AI Strategy"
item "Market Entry"
domain complicated
item "System Architecture"
This would be a separate diagram type, but the learnings from Wardley apply directly.
The Plan
- Get Wardley Map PR through code review
- Merge core implementation
- Add regions in follow-up PR
- Community input on pipelines vs annotations priority
- Cynefin as separate proposal
Open source means this roadmap can shift based on what people actually need. Once the core lands, the real feedback loop begins.
Let’s make strategic thinking native to where we work.
