Building the Product Roadmap

I recently talked about creating an effective product roadmap in this Antwak series. 

In one of the earlier posts, I talked about how to make a data-driven product roadmap. Deriving your goals in themes like Acquisition, Conversion, Money/Revenue, Engagement makes things a lot easy for keeping the roadmap data driven. Also, in the previous post, I talked about various brackets in which the features of a software product can be categorized. 

I felt the list of brackets can also help in getting ideas for a comprehensive list of tasks for the roadmap. 

Here's the list of those brackets again with some more details and examples. I'd soon add a link to the template for a product roadmap. (The list is not in any particular order.)

Feature Brackets for a Product Roadmap 

1. Parity Feature

A feature that the competition (if any) already has. The kind of features that you need, to be 'at Par' with them. The kind of features that your prospects will compare and ask questions about when you try to close the sale, especially for SaaS products. In case of consumer products, you wouldn't have loyal users mostly. You can be in good books of consumers as long as you keep providing at least what your competition is providing.  
E.g. Integration with Slack (for a Reporting Software), Price comparison (for e-commerce), Video call (for chatting app), Panic button (in a ride-hailing app) etc.  

2. Expected feature 

A feature that's naturally expected from your product. It's generally the USP, but also, includes conversion and revenue related features. In 2012, importing contact book was a disruptive feature by WhatsApp, as of 2017 importing the contact book is an expected feature for a chat application. 
E.g. Signup/Login, Home Page, Subscribe (for content-based product), Purchase module (for SaaS/E-Commerce)

3. Advanced feature 

A feature that only a power user would love. Usually, a first time user may not get it, or care about it. For someone new to youtube, it doesn't hurt that you can't filter a certain type of videos. But, as a parent and longtime consumer of Kid Video, I strongly feel the need for it. Youtube hasn't heard me yet. [Update: Youtube does have a Youtube kids app, however, a filter would really help so much more]
E.g. Customisation options like Themes, Font Settings, Filters 

4. By-products 

What perhaps 3rd parties are providing on top of your solution. It may also be an unexpected use of your product. Check my last post for more details. 
E.g. Facebook for Business, Google Tez, Youtube-kids (special app for kids) 

5. Unexpected feature 

Unsolicited, clever add-on features that can delight users in certain situations. 
E.g. Panic button in Ola (a cab hailing app), Forgot attachment notification on Gmail. 

6. Repayment feature 

Most of the time you are hacking stuff to get it out of the door. You should plan it such, that all the stuff that you kept for "later", don't get too late. Reducing technical debt, legal debt, doing compliance related stuff. 
E.g. Technical Architecture, Optimising performance, Documentation, creating really useful terms and conditions, Disclaimers, EULA, Security certifications, Government licenses and approvals etc. 

7. Engagement feature 

A cab-hailing app also allows you to store frequently visited places as favorites. An e-commerce website also allows creating a wishlist. These are not the primary use case, nor do they awe the users. They just give a sense of completeness to the product. Engagement is about providing a complete ecosystem for the user to feel connected with the product. Obviously, these features have the potential to hold the users longer, bring them back often. 
E.g. "You may also like", Favorites, Cashback, Leaderboards, Newsletter Subscription 

8. Viral feature 

Will get you more users. More often they are targeted for providing exceptional growth for a limited time. 
E.g. Referral Schemes, Incentive to Add your contact Book etc.   

9. Security feature 

Keeps your product, your users and/or your data safe. Some basic security is always appreciated by the users. Nothing is hack proof but you can ensure that it's not easy for a school kid to put you to shame - at least in the early days.  
E.g. OTP verification, Https, Pattern lock on your phone, Captcha, Re-Login 

10. Instrumentation feature 

Features that help you measure and monitor the growth/health of the product. If you are not measuring you are not improving. 
E.g. Integration with basic Analytics, integration with advanced analytics, integration with   

To understand which feature bucket is more important at which stage (early, growth, maturity etc.) of your product you can have a look at this previous post. This should provide a good reference to make sure your feature list and roadmap is both comprehensive and stresses on the right areas at the right time. 

Thoughts? I'd love to know your thoughts and comments. Please take a moment to write them.  




If you have reached this far you should totally leave a comment about how you liked it and share this post with others.  

Product Prioritisation - More than Impact v/s Effort

I recently had a nice long discussion with a product manager friend working for an e-commerce giant. Among other things we talked about prioritisation and how we do it in our respective organisations. I had some interesting thoughts and I talked to PMs in a dozen startups in India to understand how they are prioritising for their products. I realised that other than the famous impact versus effort analysis, there is an invisible framework we use to determine impact at different stages of product life cycle.

This is how the standard Prioritisation chart looks like:

1. high impact, low effort - slam dunk! obviously, go for low hanging fruits

2. low impact, low effort - I personally love these micro-optimisations. They can quickly add up to become high impact

3. high impact, high effort - the bigger projects. See if you can release them piece meal and turn them into a mix of 1 & 2.

4. low impact, high effort - why would you ever want to do these? Well, sometimes you have spare resources. Also, sometimes these are Parity or Expected features and you need to have them for the sake of completeness.

In my research, though I found more layers of complexity involved in making a decision. Notably, at different stages of product life cycle, the prioritisation is managed very differently. Whatever methods are being followed, almost no one was "consciously" considering the prime responsibility of product management - balancing business, users and tech. It was being done rather instinctively. I also figured that for most products, all their features can be grouped under certain brackets.

I found that if articulated, the framework can act as a very helpful reference while prioritising features for any B2B, or B2C product roadmap or even for doing backlog refinement for sprints. I showed it around and most PMs could relate very well to it.

Here it is. I classified different features into various brackets and I could find 10 of them. I tend to feel this is an exhaustive list of the feature classification, but let me know if you can think of more brackets that can be added. (In no particular order)

1. Parity feature - a feature that the competition (if any) already has 
2. Expected feature - feature that's naturally expected from your product. Also, includes conversion and revenue related features
3. Advanced feature - something only power users would love 
4. By-products - what perhaps 3rd parties are providing on top of your solution. Check my last post for more details.  
5. Unexpected feature- unsolicited, clever add-on that can delight users in certain situations
6. Repayment feature- reducing technical debt, legal debt, compliance related stuff
7. Engagement feature- will hold the users longer, bring them back often
8. Viral feature- will get you more users
9. Security feature- keeps your product/users/data safe 
10. Instrumentation feature - helps you measure and monitor health of product

Eventually, you'd have to put features in the Impact versus Effort chart and assess what to build. Impact estimate should cover who is it going to impact, and how much is it going to impact them. Effort estimates are what the tech team says they are (in person-days or person-months).

Practically, in larger teams with enough resources, the effort estimates are less important. 

Sorry for the digression, i know that's politically incorrect. But, I care less, that's a truth. Effort estimates come in handy only when there are competing features that need to be added and may have similar impact. Also, when resources are low and you have to argue with others and fight for your ideas. It happens mostly in early and growth stage, less frequently in maturity stage.

Now, coming to how at different stages the balancing act assigns different priorities to these feature brackets. Here's how it looks:

Early Stage
(Listed in order of Priority for this stage)

1. Expected feature - This is the core of your solution. You build this first, nothing makes sense until this is ready. 
2. Parity feature - What competition already has. When users come to you, they'd want to compare before they pay. You'd need to tell them you have those features and more.  
3. Viral feature- The referral schemes and social elements and network effects that will push you to growth stage. 
4. Repayment feature- It's important to give it enough weight for a stable, scalable future product
5. Instrumentation feature - This is setting you up for next level. You need to start thinking what you want to measure. What you can measure is what you can improve. 
6. Security feature- A stitch in time saves nine. It makes total sense to keep making security audits. You have less data but this is also the time when those sharp early adopters will try to milk your vulnerabilities the most. Particularly promotions and referral schemes. 
7. Engagement feature - less important at this stage
8. Advanced feature - don't even think about these
9. Unexpected feature- don't even think about these
10. By-products - don't even think about these

Growth Stage
(Listed in order of Priority for this stage)

1. Viral feature- create and fuel your growth engine. (Notice the jump?)
2. Parity feature - This is a necessity at this stage. You can't lose out because of these.  
3. Expected feature - You need to make sure early adopters and the early majority get what they expect, if not more. 
4. Instrumentation feature - the better you measure, the better you grow
5. Repayment feature- don't lose sight of this, it is always important
6. Engagement feature- acquisition may be top priority but if they are not being fed back to the funnel you are losing money. 
7. Security feature- Data is increasing and so is your responsibility
8. Advanced feature - you may start throwing in a feature or two for power users if they are low on effort
9. Unexpected feature- only if they are low on effort
10. By-products - don't even think, unless you see that you need to Pivot. 

Early Maturity Stage
(Listed in order of Priority for this stage)

1. Engagement feature- add more channels for engagement, make users sticky, bring the acquired pool back more often (Notice how this comes from #6 to #1)
2. Viral feature- make sure the incoming stream is steady
3. Unexpected feature- great time to innovate, bring in some fresh thoughts to delight your users
4. Security feature- this is getting critical
5. Repayment feature- stability and scalability are of prime importance
6. Advanced feature - hopefully, now you have more power users to care about
7. Instrumentation feature - measure everything, integrate with third party tools
8. By-products - this goes with better qualitative analysis of your customers and take up side projects for up selling and cross selling to the same consumer base
9. Parity feature - hopefully, you've carved a niche for yourself, but keep an eye on where they are heading
10. Expected feature - hopefully, you've nailed most of it by now so you can stop worrying about it for now

Maturity Stage
(Listed in order of Priority for this stage)

1. Engagement feature- engage more, engage better, time to curb churn 
2. By-products - leverage what you have, before others do
3. Unexpected feature- innovate, disrupt yourself before others do
4. Advanced feature - there may substantial subset of users who care about these
5. Instrumentation feature - the last 4 are only possible when your measurement is intensive and extensive
6. Viral feature- growth is still important
7. Security feature- this is critical. Make sure you have tight security, backups and continuity plans in place
8. Repayment feature- reducing technical debt keeps you stable and scalable
9. Parity feature - you should know your customers better than your competition does, parity is less important than engagement and delight. Never lose your edge
10. Expected feature - revisit your core value proposition, make sure you are honest

Decline Stage
(Listed in order of Priority for this stage)

1. By-products - Your users are moving on, your product should too. See how?
2. Engagement feature- will hold the users longer, milk as much as possible
3. Unexpected feature- unsolicited, clever add-on that can delight users in certain situations
4. Advanced feature - give them what they want 
5. Instrumentation feature - you should have mostly figured this out by now
6. Viral feature- you may try innovating with new channels, geographies, consumer sections if something can bring you back in the stable state. 
7. Security feature - be wary of access permissions, disgruntled employees
8. Repayment feature- make sure technology is not coming in the way
9. Parity feature - not just current competition, check what is disrupting the market
10. Expected feature - revisit your core value proposition

It's fun to see how you can simplify your decision making by articulating things that you instinctively do.

Did you find this useful?

Would love to know your thoughts.
Please comment here or share your ideas with me.
And feel free to share the article if you find it worth.




If you have reached this far you should totally leave a comment about how you liked it and share this post with others.