Example Mapping Template
Create a shared understanding of a new product feature.
Trusted by 65M+ users and leading companies
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?
Example mapping is a collaborative process. Ideally you should gather your team and agree on the scope of your example mapping and which questions or assumptions should be discussed. Once these agreements have been defined, you can use an example mapping template to fill in the color-coded stickies and workshop together as a group.
Get started with this template right now.
Mad Sad Glad Retrospective
Works best for:
Brainstorming, Ideation
It's tempting to measure a sprint’s success solely by whether goals and timelines were met. But there’s another important success metric: emotions. And Mad Sad Glad is a popular, effective technique for teams to explore and share their emotions after a sprint. That allows you to highlight the positive, underline the concerns, and decide how to move forward as a team. This template makes it easy to conduct a Mad Sad Glad that helps you build trust, improve team morale, and increase engagement.
Executive Summary Template
Works best for:
Leadership, Project Management, Documentation
Pique their curiosity. Get them excited. Inspire them to keep reading, diving further into your proposal details. That’s what a good executive summary has the power to do—and why it’s a crucial opening statement for business plans, project plans, investment proposals, and more. Use this template to create an executive summary that starts building belief, by answering high-level questions that include: What is your project? What are the goals? How will you bring your skills and resources to the project? And who can expect to benefit?
Low-Fidelity Prototype Template
Works best for:
Design, Desk Research, Wireframes
Low fidelity prototypes serve as practical early visions of your product or service. These simple prototypes share only a few features with the final product. They are best for testing broad concepts and validating ideas. Low fidelity prototypes help product and UX teams study product or service functionality by focusing on rapid iteration and user testing to inform future designs. The focus on sketching and mapping out content, menus, and user flow allows both designers and non-designers to participate in the design and ideation process. Instead of producing linked interactive screens, low fidelity prototypes focus on insights about user needs, designer vision, and alignment of stakeholder goals.
Customer Touchpoint Map Template
Works best for:
Desk Research, Product Management, Mapping
To attract and keep loyal customers, you have to truly start to understand them—their pain point, wants, and needs. A customer touchpoint map helps you gain that understanding by visualizing the path your customers follow, from signing up for a service, to using your site, to buying your product. And because no two customers are exactly alike, a CJM lets you plot out multiple pathways through your product. Soon you’ll be able to anticipate those pathways and satisfy your customers at every step.
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.
Impact/Effort Matrix Template
Works best for:
Project Management, Strategic Planning, Prioritization
Growing organizations have countless to-do’s and only so many hours in a day (or weeks before a big launch) to get them done. That’s where an impact effort matrix comes in. It gives you a quick visual guide to help prioritize your tasks and know exactly what’s worth doing. Using our template, you can create a matrix that organizes your activities into four main categories: quick wins that are low effort, effort-intensive projects that provide long-term returns, fill-ins that are low effort but low value, and time-wasters.