Product Roadmap
Build the next 12-month product roadmap, with the board wanting clear revenue attribution per major bet
No card required
What this brief specifies
Business Context
$6M ARR growing 25% year over year, down from 40%, across 3 product teams and 12 engineers.
Strategic Question
Whether to double down on the core PM persona or expand to an adjacent persona, customer success managers.
Known Risks
A biggest competitor just shipped a feature this team has been promising for 6 months.
What makes this hard
Growth has already decelerated from 40% to 25% year over year, and the roadmap has to decide between doubling down on the persona that produced that slowing growth or diverting a stretched 12-engineer, 3-team org toward an entirely new persona, customer success managers, whose needs haven't been built for yet. That decision is being made under the shadow of a competitor that just shipped a feature this team has publicly promised for six months, which adds pressure to close the gap on the existing persona even as the roadmap is being asked to consider walking away from it. On top of the persona fork, the board wants revenue attributed to each major bet individually, a level of clarity that's hard to produce for a brand-new persona with no revenue history, on a team that is, by its own account, already overloaded before any of these new bets are added.
Frequently asked questions
Once the current growth trajectory, the persona fork, and the specific competitive gap it's racing against are captured as one connected picture instead of three separate conversations, the same picture carries into next quarter's roadmap review or the next persona debate, so the team argues from a shared, current read of where things stand instead of rebuilding the context every time the question comes back up.