/
Published on 02.02.2026
TLDR: Example Mapping is a 25-30 minute structured conversation technique using colored cards (yellow for stories, blue for rules, green for examples, red for questions) to collaboratively break down user stories and uncover misunderstandings between developers, testers, and business stakeholders before implementation begins.
Example Mapping is a deceptively simple yet remarkably powerful technique created by Matt Wynne that should be far more widely adopted in software development teams. At its core, it's a facilitated conversation format where a small group—typically a developer, a tester, and someone from the business side—gathers together to discuss and break down a user story in approximately 25-30 minutes. The brilliance of Example Mapping lies in its structured simplicity, using only colored cards or sticky notes to organize and visualize the conversation.
The technique employs four types of cards, each representing a different aspect of the discussion. Yellow cards represent the user story itself—the feature or capability being discussed. Blue cards capture the rules: the business logic and acceptance criteria that define how the feature should behave. Green cards are for concrete examples that illustrate each rule, making abstract requirements tangible. Red cards represent the questions that nobody can answer right now—the unknowns and gaps in understanding. Throughout the session, the group continuously asks "what's an example of that?" to ground abstract rules in concrete, real-world scenarios and cluster examples under the rules they demonstrate.
The real value emerges from what this conversation reveals. Misunderstandings between business stakeholders and technical team members are expensive—they lead to wasted weeks of development effort building the wrong thing. When multiple people attempt to describe the same rule using real examples, discrepancies in assumptions surface immediately. A 30-minute conversation can prevent two weeks of misdirected coding. Beyond conflict resolution, Example Mapping serves as an effective readiness check. Too many red cards signal that the story isn't sufficiently understood. An abundance of blue cards suggests the story is too large and should be broken down further. When examples emerge easily and everyone nods in agreement, you have a strong signal that the work is ready to begin.
For architects and technical teams, Example Mapping provides a structured approach to requirements gathering that bridges the gap between business language and technical implementation. It ensures that acceptance criteria are not just documented but collectively understood before development begins. The examples captured on green cards often translate directly into acceptance tests, meaning the session produces not just clarity but also test specifications. This transforms Example Mapping from a simple conversation technique into a lightweight specification engine that naturally produces testable, concrete requirements.