A requirement can sound clear until the team asks what should happen in a particular case. Example Mapping makes those questions visible before development begins. In a short, collaborative workshop, participants arrange a user story, its rules, concrete examples, and unanswered questions into a map. The aim is a shared understanding of the expected behavior, not a quick agreement that “everything seems clear.” section 2.5 section 2.7 section 2.6.6
Four card colors give each contribution a place:
- Yellow holds the user story. Discussion may reveal that part of it should become a smaller story or wait until later. section 2.5
- Blue holds rules: groupings of examples around a condition, sometimes called acceptance criteria or business rules. section 2.5
- Green holds concrete examples that show each rule in action. A rule needs at least one illustrative example. section 2.5 section 2.7
- Red holds questions that block progress. Keeping them visible prevents repeated debate; each should have an owner by the workshop’s end. section 2.5
Changing a delivery address
Suppose a customer wants to change an order’s delivery address after placing the order. The team identifies two possible checks: whether the new address is too far from the current one, and what status the order has reached. Those statements are not yet enough to settle the behavior. Asking for particular orders, addresses, and expected outcomes helps the team test its proposed rules; any answer it cannot establish becomes a visible question. section 2.2 section 2.6.6 section 2.5
Start with the ordinary path before exploring exceptions. If talk becomes abstract or excessively technical, ask for another example. Challenge the data in an example, compare positive and negative cases, and look for different outcomes. Pause for silent writing when people need time to think. These moves help a group discover ambiguity without letting corner cases or unresolved questions consume the meeting. section 2.6.6
The map can also help when a feature comes from a fixed-scope specification. Mapping its rules and examples before implementation gives the team a better view of the feature and supports explicit scope decisions against its budget. Afterward, illustrative examples can be formulated as scenarios that drive implementation. Example Mapping does not remove gaps in a specification; it helps expose the decisions needed to work through them. section 4.6



