Skip to content

Product Journey Map

Product Journey Maps are a great tool to identify the list of capabilities customers care, prioritize them in multiple releases, and clearly visualize what the MVP should look like. It’s a tool that can be used by product managers, startup founders, and anyone interested in planning a new product or service. In addition, they create alignment and transparency among all the people involved in a new product development project, providing a space to have conversations about priorities and trade-offs.

Product Journey Maps - 5D Vision

How to build a Product Journey Map

To build a Product Journey Map you follow these steps:

1 – Start with a Mind Map. This helps you (and everyone on your team) to download the initial ideas, assumptions, and beliefs on a piece of paper.

2 – Understand your customers by creating User Personas. This is usually the result of ethnographic research, empathy interviews, and observations with your (existing or potential) customers. You may learn about their inner needs, aspirations, and beliefs. And use this information to design a better solution for them.

3 – Draw a Customer Journey Map. There is no right or wrong way to do this, and the format depends on the particular project and activities your customers do. You need to map out all the steps of a customer’s journey with your solution, identify the key activities and touchpoints, and jot down the customer’s emotional status while they go through the steps.

4 – Once you have all the steps identified, you and your team can brainstorm a list of features you’d like to build for each of the steps. Go for quantity at this point, and defer judgment at a later stage.

5 – It is time to define how your MVP will look like. What’s the goal of your MVP? What are the key hypotheses you need to validate for market-solution fit? What key elements on the technology, business and human side should you include in your MVP to deliver a full customer experience that validates your hypotheses? You may choose to have more than one MVP, if you need to validate a large, or incompatible set of hypotheses. Use the MVP Ideation Canvas to define your key MVP elements.

6 – Once you have a better understanding of what your MVP should look like, you need to prioritize your work so that only the features that are really necessary to deliver the core experience of your MVP should be at the top of your list. All others should move down to a later stage.

7 – Draw a physical line using a blue tape on the wall to separate the MVP features from everything else. Having this line visible makes it harder to change the feature list – for you or your stakeholders. It’s just a mental barrier and forces everyone to consider the consequences of changing the priorities.

8 – You may draw an additional line to identify Version 1.1, and so on. However, in an Agile world, planning more than 1 or 2 releases ahead may not prove a good use of your time as things may change before you get there.

I have found Product Journey Maps a useful tool to provide visibility to everyone – including the CEO and executives – about the roadmap and what to expect from the MVP. They are also a useful tool to maintain focus on the MVP, and avoid adding features as you go – or risk scope creep.

Product Journey Map
Product Journey Map

Download the Guide to Product Journey Maps below.


Please enable JavaScript in your browser to complete this form.
Would you like to receive updates?