Team leads can leverage example mapping to provide strategic guidance, ensuring smooth digital transformations or timely updates that keep the team equipped with competitive technology.
What is Example Mapping?
Example mapping is a structured approach to developing clear, actionable user stories. During an example mapping session, teams identify specific examples that help explore customer problem areas and determine the criteria for building new features.
Key elements an example mapping tool highlights include:
- Rules that summarize examples or define the scope of the user story.
- Questions or assumptions about uncertain situations where the ideal outcome is unclear.
- New stories that emerge or should be excluded from the final scope.
Example mapping uses a color-coded system to organize the scope of a user story:
- Yellow sticky notes for defining stories (e.g., "change of delivery address").
- Blue sticky notes for rules (e.g., "ETA is updated").
- Green sticky notes for examples (e.g., "New address is out of range").
- Red sticky notes for questions (e.g., "What if the customer lives outside the free shipping zone?").
This color-coded structure keeps the conversation focused and ensures the discussion stays on track. A blank example mapping template makes it easy to begin filling in the relevant fields and kickstart the discussion.
When to Use Example Mapping
Example mapping is a collaborative technique that helps teams define accepted user behaviors across various scenarios. It can be especially valuable for aligning cross-functional teams by fostering:
- Empathy for the customer and the team: Example mapping helps everyone understand why new product features are needed and highlights any conflicts between user stories and rules from the customer's perspective.
- Shared understanding of the industry or product: By the end of the session, the team should develop a common language and a unified appreciation of what’s at stake.
- Small but impactful opportunities for change: Example mapping encourages thinking big but acting small, helping teams prioritize which user stories can quickly be turned into real features.
- Logical rules and examples: Each user story should be backed by specific rules and examples that ensure consistent and logical behavior across the system.
Create Your Own Example Map
Creating your own example map is simple using FigJam's template. Follow these steps to get started:
- Understand the Problem
Begin by asking your product owner to define the user problem on a yellow sticky note. Then, explain how this problem translates into a need for changes in product features. This helps the entire team gain a clear understanding of the issue.
- Challenge the Problem with Follow-up Questions
Encourage your team to ask follow-up questions, starting with “What if...?” Collect these questions on red sticky notes and place them beneath the user story (the yellow sticky note). This process helps uncover edge cases or uncertainties.
- Establish the Rules
Identify the rules based on the answers to the questions on the red sticky notes. Each rule will serve as acceptance criteria for the new product features. Ensure that every rule is distinct and stands on its own without overlapping with others.
- Record Relevant Examples
Use green sticky notes to capture interesting examples or situations that illustrate the rules. Keep the discussion flowing by probing the boundaries of each rule and considering what happens if the rule fails. This step ensures clarity and helps validate your rules.
- Identify Outcomes, Impacts, and Success Metrics
Clarify the goals of each new feature. How does it align with your business objectives, and what outcomes do you expect? Identify how you’ll measure the success of the feature—what behavior you'll be tracking and evaluating.
- Turn Stories Into Actionable Items
Finally, transform your user stories into a development plan for a new feature or product. These stories can also define the minimum set of features needed to deliver value to your customers.
