How To Build Now, Next, Later Roadmaps (With Examples)
It won’t surprise you that a Now, Next, Later roadmap consists of three columns. In its most basic, feature-driven form, it might look something like this:
A Guide To User Story Mapping (With Examples) | Aha! software
User story mapping is a visual exercise that helps product teams define the work that will create a delightful user experience. Learn how to create your own user story map.
With stories prioritized from the top down, teams can see the work that will deliver the most value in the shortest time and group these stories into development sprints and product releases. Teams will create horizontal “slices” across the map, grouping stories by priority within each critical user activity. It is important to consider that this is not about identifying what is required for a minimum viable product; rather, it is critical for identifying the most important work to be completed to create a delightful customer experience.
Measuring Customer Value in a Software Product | Blog | Folding Burritos
As Product Managers we focus on delivering value to our users. But customer value is a measure of benefits vs costs. How can we translate that to software?
Getting started with User Story Mapping - Jeff Patton on The Product Experience
There's nothing more useless to a product team than a big backlog. Bringing backlogs to life—making them usable, relevant, and getting value from them—is something that transforms ordinary teams into extraordinary ones. To guide us on how to do that, we asked Jeff Patton, creator of User Story Mapping, to join us on the podcast.
RACI is vague, hard to use, and reinforces the "what the hell is happening here" status quo. DICE is specific, easy to use, and shines a bright light on dysfunction.
Download printable versions of our hypothesis framework here. Experiments are the building blocks of optimisation programmes. Each experiment will at minimum...
Prioritization is a challenge for any product manager. How do you decide what to work on first? Here is a simple scoring system to help prioritize well.
What is the Kano Model? The Kano Model is an insightful way of understanding, categorizing, and prioritizing 5 types of Customer Requirements (or potential Features) for new products and services. It was created in the early ’80s by Japan’s professor Noriaki Kano but continues today to be an essential tool for all organizations independent of industry […]
The HEART framework is a methodology to improve the user experience (UX) of software. It helps a company evaluate any aspect of its UX with 5 core metrics.
A Guide to User Story Mapping: Templates and Examples (How to Map User Stories) | Planio
Backlogs are exciting. Seeing all those potential features, updates, and bug fixes all in one place, just full of potential… Yeah, sure. Right about now you probably think I’m full of something other than potential. The truth is that backlogs can be confusing.
Free Agile Guide that explains What is User Story Map and How to Manage Stories with Story Map. It also consists of a full list of backlog item description: theme, user feature, epic, user story, tasks. Completely FREE. Check out for details.
Why you should stop using product roadmaps and try the GIST Framework
Why product roadmaps don't work, and how to use the GIST framework - Goals, Ideas, Steps, Tasks, to drive truly agile planning and execution.
“We have a goal to deal with in-product collaboration by end of Q3. I can’t say exactly how it will work yet — we’re considering a number of ideas and keeping things agile, but we should have an MVP by end of Q2. Would you like to be an early tester and give us feedback?”
No split of ideation, planning and execution — they all happen concurrently all the time
Goals rather than solutions or vague strategy statements.
Idea banks rather than product backlogs.
Short sub-quarter step-projects rather than long multi-quarter/multi-year projects.
No betting on just a few big ideas that take forever to implement — we test many ideas quickly and pursue the ones that work.
Iterations — we revisit every part of the plan regularly and systematically and stay agile at all levels.