Professional Documents
Culture Documents
Roadmaps Wireframe
Roadmaps Wireframe
Product Roadmaps
What is this?
A strawman of a process that can adapt with the changing needs of the system,
customers/users, and teams.
Why?
Support RR Product Leaders plan and rally their teams around product Planning
Section 3 | What questions will our product answer? Leap of faith assumptions
A compelling story is also important externally to connect with customers, attract talent, and excite
stakeholders.
How?
PAIN GAIN
Fear, frustration, obstacles “Wants” / needs, measure of success,
obstacles
Section 1 | What is our product?
DEFINE
DEFINE LONG METRICS FOR
RR_BMC SUCCESS
TERM GOAL SCALE
METRICS
Section 2 | How we will measure success?
4
fundamental to our revenue
6
1
streams?
7
KEY RESOURCES
What key resources do our value
proposition require?
5
2 CHANNELS
What are the channels do our
customers what to be reached?
3
How are we doing it now? Do they
work?
8
Which key Resources and key activities are the most expensive?
Section 2 | How we will measure success?
With your RR_BMC in place, ask yourself this question: If everything goes
according to plan, what will you be doing six months from now and two
years from now?
Section 2 | How we will measure success?
Quantify your plan. What key metrics will you be measuring your success
on? How much runway do we have to qualify those metrics? Use the
RR_BMC to quantify the desirability, viability, and feasibility of your product.
Section 2 | How we will measure success?
GOALS
KEY
METRICS
of
SUCCESS
Section 2 | How we will measure success?
This section of the roadmap includes the key metrics that ensure the product scales.
Categorize the success metrics by urgency - those that are important to realize over the near, mid, to
long-term time horizon.
With your success metrics clearly defined, now it's time to unpack the riskiest assumptions that will determine
the success of your product.
LEAPS OF DEFINE
PRIORITISE LOFAs ON THE
FAITH SCOPE OF
ROADMAP
ASSUMPTIONS RELEASES
Section 3 | What questions will our product answer?
Definition: Definition:
Value LOFAs Testes whether the new Story/product/service Scale LOFAs Tests how new customers/systems will adopt the
will create value for the system and customer. product process
High
MAGNITUDE OF IMPACT
MAGNITUDE OF TIME
Section 3 | What questions will our product answer?
Most critical LOFAs
MVP1
MVP2
MVP3
MVP..
Section 3 | What questions will our product answer?
Q1 Q2 Q3 Q4
Section 4
The foundation of a roadmap is quite simple: to describe what we will ship and by when.
Getting to this view can be challenging. Start by auditing your existing stories to determine their frequency and
adoption. For the stories that require improvement, create an action plan to increase the Story's value,
frequency, and/or adoption. Lastly, prioritize stories by effort and impact to clarify the sequence of delivery.
PRODUCT
Story Story AUDIT ACTION
RELEASE
BACKLOG PLAN
TIMELINE
Section 4 | What are we shipping and when?
Story backlog
Using the MVPs defined in the previous step, create the core set of Stories that enable the MVP. Feel free to
start with an existing backlog or create Stories from scratch.
Story audit
Using data and analytics for the existing product, plot each Story on this 2x2 to clarify which stories are
delivering value frequently and which are adopted across multiple user groups or systems.. Incorporate the
success metrics from step two as a guidepost for evaluation and prioritization.
**Note: The audit should be plotted considering the product specific impact.
High
frequency
Low
frequency
Section 4 | What are we shipping and when?
Action plan
For the stories prioritized in step above that are candidates to improve, collaborate on an action plan to
determine how best to improve and reimagine each Story by value, frequency, and adoption.
Value improvements:
High performing stories that we can make even
better.
Prioritized Effort vs. impact
Action Plan New Story
Story
High impact / High effort /
Low effort high impact
Frequency improvements
stories that are relevant for a specific job, but
have potential to be used on a broader basis.
Prioritized
Action Plan New Story
Story
Adoption Improvements
Low impact / Low impact /
stories that are relevant for the majority of user low effort high effort
groups, but are only being used by a minority.
Prioritized
Action Plan New Story
Story
Section 4 | What are we shipping and when?
Story
EPIC Story
Story
Story
EPIC Story
Story
Story
EPIC Story
Story