For change managers & strategy consultants
Wardley maps that come out as actual maps
Run a Wardley session with your team. Harmonica places components on the evolution axis based on what the participants actually said. Output is standard Mermaid syntax: correctable, portable, ready for the deck.
Why running a Wardley session is hard
Three problems strategy work keeps hitting
Maps that stay in someone's head
A Wardley conversation needs everyone in the room, but the map almost always gets drawn afterwards by one person who synthesizes notes. By the time it's shared back, the people in the conversation don't quite recognize it, and the map's authority is whatever they're willing to grant the person who drew it.
Async coordination is harder than sync, not easier
Strategy work spread across time zones loses the live argument that produces a good map. Async Miro boards turn into sticker piles. Async docs turn into bullet lists. Nothing that ends up looking like a Wardley map.
The artifact gets trapped in your tool
Maps drawn in a SaaS mapping tool live and die in that tool. Pasting a screenshot into a deck strips the structure; exporting rarely produces something a future facilitator can keep working on.
How Harmonica helps
A map built from what the group said, not what one person remembered
The map is built from what the group said
Harmonica runs the Wardley conversation as a structured session: each participant contributes through the same flow, the AI facilitator presses where reasoning is thin, and components are placed on the evolution axis based on the words in the transcript. Every placement traces back to a quote, so the map is checkable, not asserted.
Async-first, with sync as a finishing pass
Participants join in their own time, in their own language; the synthesis converges as they go. Use the live workshop for the calls that need a room, not for catching up on what the team already covered.
Output is Mermaid, not a picture
The map renders in Mermaid's Wardley syntax (v11.14.0+): standard, portable text. Correct placements directly when something is off, then drop the map into any tool that renders Mermaid — your docs site, your strategy deck, your engineering wiki. The artifact survives Harmonica.
Built for this
Why Harmonica works for Wardley
Standard Mermaid Wardley syntax. Portable text, not a picture trapped in our tool. Drop the same map into Notion, your docs site, a strategy deck, or any tool that renders Mermaid.
Direct map correction. Fix component placement or evolution stage in one edit; everything around it updates. No round-trip through a separate diagramming tool.
Quote-backed placements. Every component carries the participant words that put it where it sits. The map is auditable, and disagreements have somewhere to land.
Chained sessions for multi-stage strategy. Pair the Wardley session with a follow-up (bottleneck identification, doctrine review, climatic-pattern surfacing) and the context from each stage carries into the next.
Cross-pollination across participants. On Pro, emerging themes are shared between conversations in real time, so the map converges instead of fragmenting into N personal versions.
Saved with the Project. The map sits alongside the session it came from in the host's Project view, with the participant summaries one click away.
Stop drawing maps after the conversation
Run your next Wardley session with the people in it, get a real map at the end, and take it anywhere Mermaid renders. Free tier available, no credit card.