Hi all,
We've been discussing different roadmap views lately and I wanted to jump in and share some of my thoughts about how the audience matters when creating roadmaps. Sending a granular timeline to a stakeholder who only cares about quarterly outcomes is probably going to lead to more questions than answers.
But as a PM, I know we're being asked to do more and more and the the thought of manually keeping multiple roadmap views up-to-date is simply not an option.
The great news is that you don't have to do this manually. airfocus makes it super easy to create different views of the same data for different stakeholders or audiences. And, these views all stay up to date as you and your teams work.
Here's some of the ways I use airfocus different view types:
- For the "Big Picture" Stakeholders: I use the airfocus board view to show a kanban-style view of high-level initiatives by quarter. Then, I choose to just show a few key fields shown like "status" and "team" on the cards.
- For my engineering teams: I use another board view, but instead set the columns to "Status". This helps them to see the work in terms of what's ready for development or still in-discovery.
- For other product managers in the org: I created a table view of our initiatives with information like estimated timelines for features and the team working on it. Since we have our roadmap items connected to these high-level initiatives, they can easily click to see the child items contributing to each initiative and ask questions directly on the items with comments.
I know learning a new tool can be daunting and that's why we also created some roadmap templates so you can get started quickly with popular roadmap styles. Check those out here!
Work smarter, not harder.
Cheers!
Spencer Cowley - Product Manager - airfocus
Your privacy choices
