A product roadmap is a powerful tool to describe how a product is likely to grow & to align the stakeholders.
Identify & Define all your business goals or metrics, such as…
Anything built in product must have required impact on a core metric or goal. Also, a primary factor to prioritise features.
Do give a catchy & unique name to a feature — helps bring emotion in to execution
Couple of lines to describe the feature, should help anyone in company to relate and understand the feature.
Every feature should have a related micro level metric, may be adoption or repeat usage.
Used to prioritise features, define experiments, design features, track feature’s success.
Feature Fallacy is a myth that the next feature to be shipped will change the game for you.
Never ship or prioritise a feature which do not clear feature fallacy test.
Who is the target of this feature? — Core User, Non-User or New User
What kind of investment required by the user — Deep or Lesser
Pass features where target segment is above average size & requires lesser investment from user
Always prefer or prioritise features with virality impact.
Put ‘Yes’ or ‘No’ in the column to signify as value.
Consider Tech Team Inputs on Sizing & Velocity on shipping a feature. No need to mention — Its also a key to prioritise features.
In the end, roadmap is all about Priority. so, lets generate an output in form of buckets — #Now , #Next & #Later
Feedback or query ? — please comment. Do recommend or share for karma :-)
Create your free account to unlock your custom reading experience.