Can I pick your brain about product roadmaps?

Can I pick your brain about product roadmaps?

I’m asked questions about product management from time to time. Here’s one I’ve answered recently:

Hey Jock,

I would love to pick your brain about product roadmaps.

To give more clarity to my team (which is working on two mandates/sub-projects), I would like to empower them with a roadmap/timeline of the project. We already have one, on Confluence that I’ve printed next to our whiteboard. But it’s not “ours”.

Any recommendation in terms of shape/content? Should it be extremely detailed or high level? More generally, how to craft the best roadmap/product timeline for my team?

And for its creation? Any convenient tool or Excel template for this?

Thanks so much for your help!

Read on for my reply.

Hi P,

Thanks for letting me know how you’re getting on.

Teams should have their own roadmaps. If a team is working on multiple products or components, then the roadmap should show at a high level (i.e. this item will take a team a sprint or more) everything they’re working on (including housekeeping tasks) in the same place. If it takes up the team’s time, put it on the roadmap. The product manager should update the roadmap at least once a week.

You should probably have some kind of short roadmap update session every couple of weeks with all the teams together.

I favour no timescales on roadmaps, just now / next / later. Items have in ‘now’ have more detail, a bit less on the ‘next’ and minimal detail on the ‘later’ (which may not even happen).

Finer detail (the breakdown of a sprint-sized item into smaller tasks as needed) on what’s been worked on right now should be in the backlog. This should be kept up to date by the team itself several times a day, and reviewed every day at team standup.

Your roadmaps and backlog need to be highly visible. You can have your team roadmaps and backlogs on a big screen or up on a physical board, or both. It doesn’t matter as long as the team and passers-by can see them easily at all times. If your teams are remote from each other, you have to work extra hard to achieve this.

There are plenty of roadmapping and backlog tools out there. I’ve always tended to use physical boards + post-its, combined with Trello or ProdPad, as they give me lots of flexibility. Just make sure you lock down the access to anything sensitive, particularly in Trello.

Hope that helps. I talk more about roadmaps on the blog: The secret behind meaningful roadmaps



Get articles when they’re published

My articles get published irregularly (erratically, some might say). Never miss an article again by getting them delivered direct to your inbox as soon as they go live.  

Read more from Jock

The Practitioner's Guide to Product Management book cover

The Practitioner's Guide To Product Management

by Jock Busuttil

“This is a great book for Product Managers or those considering a career in Product Management.”

— Lyndsay Denton

Jock Busuttil is a product management and leadership coach, product leader and author. He has spent over two decades working with technology companies to improve their product management practices, from startups to multinationals. In 2012 Jock founded Product People Limited, which provides product management consultancy, coaching and training. Its clients include BBC, University of Cambridge, Ometria, Prolific and the UK’s Ministry of Justice and Government Digital Service (GDS). Jock holds a master’s degree in Classics from the University of Cambridge. He is the author of the popular book The Practitioner’s Guide To Product Management, which was published in January 2015 by Grand Central Publishing in the US and Piatkus in the UK. He writes the blog I Manage Products and weekly product management newsletter PRODUCTHEAD. You can find him on Mastodon, X (formerly Twitter) and LinkedIn.

Leave a Reply

Your email address will not be published. Required fields are marked *