Please enable JavaScript.
Coggle requires JavaScript to display documents.
PRODUCT ROADMAPPING (The purpose of an internal product roadmap is to help…
PRODUCT ROADMAPPING
The purpose of an internal product roadmap is to help teams across your organization align their team-level goals and objectives to your wider product and business goals.
Roadmaps are frequently adjusted by product managers to reflect market changes, internal issues and as customer needs and desires shift. For this reason, the product roadmap is the most up-to-date reference for your product strateg
-
A roadmap represents your product strategy, so it should include the topics you would generally discuss in a product strategy meeting
-
templates
theme based
What problem are we trying to solve?
How do we plan to solve it?
What are our objectives?
benefits
Have way fewer meetings – Your priorities (what and why) are clearly documented on the roadmap. You don’t have to explain things differently to different people.
Foster healthy team debates – Your roadmap can be the reference point team members use to challenge themselves and one another to link their deliverables back to roadmap goals and OKRs.
Make product decisions everyone understands – You’re no longer the bad guy batting down ideas. You can actually discuss customer feedback and ideas through the lens of your roadmap and priorities everyone can see
Objectives - What business goals will this help us meet?
Business case - What value will this provide our customers or end users?
Customer feedback - What have customers been saying about this particular problem? How many customers have brought it up?
User stories - What outcome do users expect when they go through a particular action?
Mockups - What might the solution look like?
User personas - Which of our users are we building for? What are they like?
-
-
-
exercises
-
A/B testing
- What hypotheses are you testing? What have you learned about users through past testing? What do you plan to learn about users? Historical data is a useful starting point.
Customer feedback - What are customers saying? Are there any feedback trends? Are there any interesting outliers? What problems or frustrations have they been calling in about?
Customer behavior
- How are customers using the product? How active are they? Where are they dropping off? What features are they using? If you’ve done any user research or testing, what were the findings?
Product Manager | One of the core responsibilities of every product manager’s role is to define the evolution of the product long term – or rather, to translate the multitude of inputs coming from internal stakeholders, customers and other sources into a (hopefully) visionary product roadmap.
Teresa Torres:
We need to let go of the idea that we can enumerate a list of features that represents what we’ll do in the future. This idea is absurd. Rather than sharing feature lists with the rest of the company, we should be communicating how we will make decisions.dg
-