What is Reddit's opinion of Product Roadmaps Relaunched: How to Set Direction while Embracing Uncertainty?

From 3.5 billion Reddit comments

I have really struggled finding a good roadmapping software and I think it has less to do with the softwares itself than with the problem: A good roadmap is always adjusted to the audience and should not just be what you plan to ship in the next X weeks (as you should not commit to shipping specific things in 6 months time but rather focus on the problems you are looking to solve for customers).

A good book on this topic I wish I had found earlier was Product Roadmaps Relaunched

What really stands out here is that whomever requested you do this has no idea what a product roadmap is for at all.

The litmus test for a good product roadmap is that it’s visual, accessible and clear enough for anyone to scan for answers to the following questions:

• What are we doing?
• Why are we doing it?
• How does this tie back to our OKRs?

Things that roadmaps do not include:

• Sprints
• Releases
• Deadlines or timelines

What you've been asked to provide is not a roadmap, it's a release plan, which is very different. A release plan does include capacity planning, sprints, releases, timelines, etc.

I recommend the following further reading when it comes to product roadmaps:

• How to build a roadmap everyone understands
• Myth busting: Why date driven roadmaps are not roadmaps
• How to Sell Your Boss on Roadmaps Without Timelines
• A gantt chart is not a product roadmap
• Roadmapping without dates: Build yourself a better strategic plan
• Drop Feature-based Roadmaps
• Themes: A Small Change to Product Roadmaps with Large Effects 

I would also highly recommend getting this book on Amazon if you can: https://www.amazon.co.uk/Product-Roadmaps-Relaunched-Todd-Lombardo/dp/149197172X

​

In addition, take a look at C.Todd Lombardo's talk at Mind The Product on roadmaps: https://www.mindtheproduct.com/2018/08/roadmaps-are-dead-long-live-roadmaps-by-c-todd-lombardo/

Hey, sure happy to help!

The problem with gantt charts is that they represent a very waterfall way of working. They may have been the right way to work before, but with Agile/Lean methodologies you really need to drop the feature-based and timeline-based approach and focus more on something that's more flexible.

A product roadmap is meant to represent what and why, not how. How is the execution phase, and also takes into consideration other items outside the remit of strategy (such as bugs, fixes, etc.)

There are some really good articles for you here:
https://www.prodpad.com/blog/how-to-build-a-product-roadmap-everyone-understands/
https://blog.trello.com/agile-roadmapping-how-to-think-big-ship-fast
https://www.producttalk.org/2014/04/drop-feature-based-product-roadmaps/
https://articles.uie.com/themes/

And I would highly recommend this book by C.Todd Lombardo on Amazon: https://www.amazon.co.uk/Product-Roadmaps-Relaunched-Todd-Lombardo/dp/149197172X

ok so.. first of all, a product roadmap includes no dates or timelines. This is a release plan, which comes after you have prioritized and planned your strategy. Drop the dates now.

A product roadmap is meant to communicate strategy - what you're doing, why you're doing it, and how this relates back to your product vision.

To answer your specific questions:

What is the typical format of a roadmap - a huge graph with major features embedded?

No, no, and no. A typical roadmap communicates strategy, not execution. Execution comes AFTER, not before strategy. Your roadmap should focus on themes (what, why) not releases (how) and not be based on features you are releasing.

How do I come up with the release schedules (past teams I've worked on do weekly)?

Release scheduling is primarily a dev function, but on smaller teams something the product manager will be in charge of. You need to plan weekly sprints with your team, figure out their workload, and then work in releases. If you're agile, you can release up to twice a week (we do that.) Remember that releases will include both new and existing issues. (features and bugs.)

I've been asked to go up to 8 quarters (!) ahead of time. Is this even reasonable? I know priorities change often, so I'm not really sure how useful it is to go that far. I don't want to fall into the trap of constantly re-working my roadmap by stretching time so far away.

You are absolutely falling into a trap, because again, you shouldn't be planning your product roadmap in terms of releases. You're confusing release planning and product roadmapping, and even trying to attempt to plan your releases 8 quarters in advance is a nightmare.

Any useful resources out there for this (software, templates, articles)?

Yes: Themes: A Small Change to Product Roadmaps With Large Effects by Jared Spool
Drop Feature-Based Roadmaps by Teresa Torres
How to build a product roadmap everyone understands by Andrea Saez
Product Roadmaps Relaunched by C. Todd Lombardo, Bruce McCarthy, Evan Ryan, Michael Connors - available on Amazon

https://www.amazon.com/Product-Roadmaps-Relaunched-Direction-Uncertainty/dp/149197172X

You might like Product Roadmaps Relaunched: How to Set Direction while Embracing Uncertainty.

Absolutely! I've actually written about this in several occasions. Here are a few links for you:

How to build a roadmap everyone understands
Myth busting: Why date driven roadmaps are not roadmaps
How to Sell Your Boss on Roadmaps Without Timelines
Drop Feature-based Roadmaps
Themes: A Small Change to Product Roadmaps with Large Effects

I would also highly recommend getting this book on Amazon if you can: https://www.amazon.co.uk/Product-Roadmaps-Relaunched-Todd-Lombardo/dp/149197172X