Example Mapping Template
Create a shared understanding of a new product feature.
About the Example Mapping Template
Example mapping (or user story mapping) helps product managers and their teams quickly break down product backlogs. Ideally, example maps help a cross-functional team (for instance, a product owner, tester, and developer) build up a shared understanding and language for why product features need to be added or changed.
Team leads can offer strategic direction toward a cohesive digital transformation (or timely upgrade) so your team has the relevant technology to stay competitive.
What is example mapping?
An example mapping session is a great way to develop structured, concrete user stories. Each example uncovered can help teams explore problem areas for customers and decide on acceptable criteria to build a new feature.
There are a few key elements that an example mapping tool can delineate:
Rules that sum up examples or agree on the scope of the user story
Questions or assumptions about situations where no one knows the ideal outcome
New stories that should be discovered or left out of the final scope
Example mapping also relies on a color-coded system to shape the scope of a user story:
Yellow sticky notes are for defining stories, such as “change of delivery address”
Blue sticky notes are for defining rules, such as “ETA is updated”
Green sticky notes are for defining examples, like “New address is out of range”
Red sticky notes are for questions, like “what if the customer lives outside the free shipping zone?”
This color-coded system helps steer the conversation in the right direction and keep the discussion on track. You can use a blank example mapping template to quickly and easily begin filling in the relevant fields to get the conversation started.
When to use example mapping
Example mapping is a collaborative method that can help your team define what accepted user behavior looks like for different scenarios. An example mapping tool can be a useful way to align your cross-functional teams toward:
Empathy for the customer and the team. Everyone should understand why new product features are needed, and what the customer may be struggling with as far as conflicts between stories and rules.
Shared understanding of the industry or product. By the end of the example mapping session, the team should leave with a shared language and appreciation for what’s at stake.
Small yet impactful potential for change. Think big and act small as a team. How soon can each recorded user story be translated into a real feature?
Rules and examples that follow logic. Specific rules and scenarios should back up every user story.
Create your own example map
Making your own example map is easy with Miro's template. Get started by adding the example mapping template to a new board, then take the following steps to make one of your own.
Understand the problem. Ask your product owner to define the user problem on a yellow sticky note, then explain how this translates to a need for a change in the product features. This helps the team better understand the problem.
Challenge the problem by asking follow-up questions. Collect all your team’s questions on red sticky notes, starting with “What if...?” These questions will live under your user story (the yellow sticky note).
Figure out the rules. Find the rules in the answers to the questions on red sticky notes. Each rule is your acceptance criteria for new product features. Make sure that every new rule can stand on its own. Ideally, it shouldn't be confused with or too similar to another rule.
Describe situations with relevant examples. Green sticky notes are where you record and collect interesting potential cases or instances. Keep the discussion going, and engage your team’s critical thinking skills by checking if you’ve reached the boundaries of the rule of your examples, as well as considering what happens if the rule fails.
Identify outcomes, impacts, and success metrics. What do you hope to accomplish with a new product feature, and how does it contribute to your business objectives? Consider how you might track and test the success of each proposed feature – what behavior you’ll be looking for and measuring.
Turn your stories into action items. These stories can be turned into a development plan for a new feature or product. They can also form the basis of a minimum amount of features needed to be valuable to your customer.
What is an example mapping technique?
The example mapping technique is a helpful method for creating detailed and specific user stories. By identifying examples, teams can delve into customer pain points and set criteria for new feature development. This technique was developed by Matt Wynne, who is the co-founder of Cucumber. It allows product managers and their teams to prioritize and refine product backlogs. Ideally, example maps promote shared understanding among cross-functional teams, such as product owners, testers, and developers, regarding the reasons for adding or changing product features. Through this collaborative approach, teams can define the expected user behavior across different scenarios. Effectively using an example mapping tool helps align cross-functional teams toward common objectives.
Get started with this template right now.
PEST Analysis Template
Works best for:
Ideation, Strategic Planning, Business Management
No business operates inside a vacuum, so if you want to succeed, you have to successfully deal with local laws, government regulating bodies, the health of the local economy, social factors like the unemployment rate, average household income, and more. Use the PEST Analysis Template to help you explore how the world impacts your business and how you can work around it.
UML Sequence E-commerce Checkout Template
Works best for:
UML
The UML Sequence E-commerce Checkout Template in Miro is a versatile tool for visualizing and analyzing e-commerce checkout processes. It provides a step-by-step visual representation of system interactions, is highly customizable, supports real-time collaboration, and is suitable for various e-commerce platforms. It serves as an efficient documentation tool, fosters team collaboration, and contributes to a more streamlined checkout experience for customers.
UX Research Plan Template
Works best for:
Market Research, Desk Research, User Experience
A research plan communicates the fundamental information that stakeholders need to understand about a user experience research project: who, what, why, and when. The plan ensures everyone is aligned and knows what they must do to make the UX research project a success. Use the research plan to communicate background information about your project; objectives; research methods; the scope of the project, and profiles of the participants. By using a UX research plan, you can achieve stakeholder buy-in, stay on track, and set yourself up for success.
Look Mock Analyze Template
Works best for:
Design, Desk Research, Product Management
Doing your homework (aka, the research) is a key step in your design process, and the Look, Mock, Analyze approach helps you examine, structure, and streamline that step. With this powerful tool you’ll be able to identify your strengths and weaknesses, what you did right or wrong, and whether you spent time efficiently. Our Look, Mock, Analyze template makes it so easy for you to discover inspiration, mock up designs, and get feedback — you can start by setting up your board in less than a minute.
Scope of Work Template
Works best for:
Project management, Planning
The Scope of Work Template from Miro brings structure, clarity, and efficiency to project planning. It's more than just a template—it's an adaptable and dynamic platform that adapts to your unique project needs. Join thousands of satisfied users and make the Scope of Work Template a part of your project management toolkit.
Spider Diagram Template
Works best for:
Diagramming, Mapping
Perfect for brainstorming sessions, project planning, or simply organizing thoughts, the Spider Diagram Template allows you to create 'legs' branching out from a central idea, representing related topics or subtopics.