Example Mapping

Purpose

Example Mapping uses four colours of cards to turn a vague user story into a clear specification in under 30 minutes. By the end, the team knows the rules, has concrete examples, and has surfaced all open questions.

At a glance

How to run

1. Place the story (1 min) — Write the user story on a yellow card and place it at the top.
2. Identify rules (10 min) — What business rules govern this story? Write each on a blue card. Place them in a row below the story.
3. Add examples (10 min) — For each rule, create concrete examples on green cards. Place them below the relevant rule. Use Given-When-Then if helpful.
4. Capture questions (5 min) — Anything unclear goes on a red card. These must be answered before development starts.
5. Assess readiness (4 min) — If there are too many red cards, the story is not ready. If rules are clear and examples are sufficient, the story can enter the Sprint.

Materials needed

• Four colours of index cards or sticky notes (yellow, blue, green, red)
• The user story with initial acceptance criteria
• Table or digital board

Pitfalls & common mistakes

• Going over 30 minutes — If the conversation runs long, the story is too big. Split it.
• Too many rules — More than 5–7 rules per story suggests the story should be split.
• No examples for a rule — A rule without examples is not understood. Always illustrate.
• Ignoring red cards — Questions must be resolved before development. Do not start coding with open questions.

Inclusion & accessibility

• Use both colour and shape or text labels for card types (not colour alone for colour-blind participants).
• Share the story in advance so everyone can prepare.
• Allow participants to write examples in their own words.

Variations

• Digital Example Mapping — Use Miro or a similar tool with coloured sticky notes.
• Example Mapping + Three Amigos — Combine the two for a structured refinement session.
• Example Mapping for bugs — Use the format to specify reproduction steps and expected behaviour.

When NOT to use this

• For stories that are already crystal clear with well-defined acceptance criteria.
• If the team cannot assemble the right people (business, dev, test) — the conversation requires all three perspectives.

Source & further reading

• Wynne, M. (2015). "Introducing Example Mapping." cucumber.io
• Adzic, G. (2011). *Specification by Example*. Manning.