Can we talk about roadmaps for a minute?

Matt O'Connell
5 replies
In product circles there is a ton of talk that has been circulating for some time now about shifting how we think about work. Less focus on outputs (the actual task) and more focus on the outcomes we want to achieve (our goals). When thinking about outcomes & roadmaps, it's kind of funny to me that roadmaps are essentially a list of features (outputs). At the end of the day, the 'things' that are being prioritized are still the individual outputs. I'm curious how teams, that are actually working in outcomes, connect features to outcomes on their roadmaps? I can kick it off with what I've seen - Create a wiki page and add a link to an epic level ticket in (jira, github, monday, asana, productboard, trello, etc...) Anything else?


Maxwell Davis
It's kind of the same thing with Vision-Strategy-Projects. For example we're creating a new Twitch Extension to help streamers with audience engagement. We have a bunch of "product features" that deal that align to that but we've also got some strategic things - like making our product "sticky". We have launched yet so keen to hear the thoughts here...
Matt O'Connell
@maxwellcdavis I think if I interpret you correctly you have some "product" outcomes and those are the features that users actually care about and you have "business" outcomes that your business cares about (reduce churn, increase MAU). Is the question around getting thoughts on aligning those two ideas to better prioritize what to do next?
David Babins
A few roadmap resources that might help with a good overview on things worth considering... :)
Matt O'Connell
@david_babins Thanks for the links. There is some good stuff in there, but some things still don't sit well. This ides of frequently updating the roadmap (productplan post). If I'm outcome led, I'd prefer to have to not constantly update the roadmap when outcomes are adjust. If features are related to de-prioritized i'd rather just not see them until I re-prioritize that goal. Aha has this strategy view which get's a little closer (I suppose) by grouping "TODO" s under a goal and only after plotting on value effort matrix? Still all seems highly focused on the work and less so on the goals and discovery that leads to high value work. Appreciate the links!
Daniel Leal
I strongly recommend the approach of the book inspired and this article from Alexander Torrenegra, a Colombian entrepreneur: