For software teams & product managers
Map user stories before they explode in the sprint
Run an async Example Mapping session with your three amigos — product, dev, and test. Harmonica guides each role through the conversation, surfaces rules and concrete examples, and captures the questions nobody can answer yet.
Why refinement keeps failing
Three problems requirements conversations keep hitting
Three people, one timeslot, zero alignment
Scheduling the three amigos is a coordination tax teams pay every sprint. When product, dev, and test can't find the same window, the story skips refinement and goes straight into the sprint — carrying everyone's different assumptions with it.
The conversation wanders
Without structure, a requirements meeting turns into a roundtable where the loudest voice shapes the story. Scenarios get debated instead of mapped. Questions nobody can answer eat up the time. Teams skip refinement because it costs too much and produces too little.
Stories that explode three days before demo
The price of skipping or rushing refinement shows up mid-sprint: scope assumptions that don't match, edge cases the tester found on day three, a rule the product owner meant differently. Big fat stories that felt ready aren't.
How Harmonica helps
A structured conversation your three amigos can have async
Async, role-aware, time-boxed
Each amigo contributes on their own schedule. Harmonica runs a three-step chain — Story Framing, Rules & Examples, Readiness Check — and advances only when all three roles have responded. No scheduling required; no one left behind.
The facilitator knows which amigo you are
When you're the product owner, the facilitator guides you to articulate the business intent and author the rules. When you're the tester, it asks you for concrete examples and edge cases. Same session, different lens per role — so every perspective gets drawn out, not flattened.
Rules, examples, questions — structured output
Step 2 produces a shared map: rules the group agrees on, rules where interpretations diverged, examples organized in the "The one where…" format, and open questions captured rather than debated. Step 3 layers a readiness verdict from each role on top: ready, ready with conditions, or not yet.
Built for this
Why Harmonica works for Example Mapping
Three-step chain that builds in layers. Story Framing surfaces misaligned mental models before the rules conversation. Rules & Examples builds the map. Readiness Check confirms the story is sprint-ready. Each step inherits the structured output of the one before.
Intentional role assignment. You choose who holds each amigo perspective at session launch. The three amigos pattern only works when the roles are deliberate — Harmonica makes that explicit.
Questions captured, not debated. When the outcome of an example is unclear, the facilitator redirects: capture it as an open question and move on. The "red card" discipline from Example Mapping is built into the facilitation, not left to the group to enforce.
Friends-episode naming, no Gherkin. Examples are captured as "The one where…" — the low-friction format Matt Wynne recommends. Gherkin authoring is a separate activity; the session stays at the shared-understanding level where it belongs.
Readiness verdict per role. Step 3 closes with a qualitative signal from each amigo — yes, yes with conditions, or not yet — plus their reasoning. Not a score; a checkable decision the team made together.
Saved with the Project. The full conversation — rules, examples, open questions, and readiness votes — sits alongside the session in the host's Project view, accessible after the sprint for retrospective or QA reference.
Stop pulling stories you haven't mapped
Set up an Example Mapping session, assign your three amigos, and get a shared understanding of rules, examples, and open questions before the sprint starts. Free tier available, no credit card.