Product Vision and Roadmapping
#What it is
Product Vision and Roadmapping: The ability to define a vision for the PM's product area that connects to team/company strategy, and to define a clear roadmap of highly prioritized features/initiatives that deliver against that vision.
This is the competency that turns strategy into a plan people can actually follow. Strategic Impact decides the bet; this one decides the sequence: the vision at the top, the prioritized work underneath, and the through-line connecting them. It's the most visible competency in the strategy area, because the artifacts, the vision and the roadmap, are the things stakeholders see and judge you on.
#The behaviors
My model breaks this into three named behaviors, top-down: set the horizon, prioritize the work, then sequence and communicate it.
#Long-Term Vision Definition & Evangelism
Crafting a compelling long-term vision that inspires and aligns, anchored in customer, market, and strategy; balancing aspiration with feasibility; reinforcing and evolving it.
A vision's job is to make a thousand small decisions for you so you don't have to be in every room. If it's good, an engineer can make a trade-off call at 11pm and land where you would have. The "evangelism" half is the part PMs underrate. A vision stated once is forgotten by Friday. You have to repeat it until you're sick of hearing yourself say it, which is roughly when the org starts to internalize it. The full craft is in Crafting a Product Vision.
#Product Prioritization
Using a strategic lens (user value, business impact, feasibility); applying structured frameworks (RICE, impact-effort, cost-benefit); balancing short vs long term; transparent rationale; saying 'no' to focus on the highest leverage.
Prioritization is the daily expression of strategy. Every yes is a no to something else, and the discipline is making those trade-offs visible and defensible rather than political. I lean on structured frameworks, not because they produce a magic number (they don't), but because they force the conversation onto explicit criteria and make the rationale auditable. The deep dive is Prioritization Frameworks, with RICE and Scoring Models for the scoring mechanics.
#Roadmap Creation & Management
Translating strategy into an outcome-focused roadmap; aligning cross-functional partners early; tailoring communication to the audience; continuously reviewing and adjusting while preserving intent.
A roadmap is not a release schedule. The best roadmaps I've run are organized by outcome and time horizon (Now / Next / Later), not by dated feature commitments, because dates you can't honor destroy trust faster than slipped scope does. The "tailoring to audience" point is crucial: the roadmap an exec needs (bets and outcomes) is not the roadmap an engineer needs (next two sprints). The craft is in Building and Managing a Roadmap.
The most damaging roadmap is a Gantt chart of feature-by-date promises. It converts every estimate into a commitment, punishes learning, and turns the PM into a project manager defending slipped dates. Roadmaps are statements of intent and priority, not delivery contracts.
#How it shows up by level
| Level | What vision & roadmapping looks like |
|---|---|
| APM | Maintains a feature backlog and prioritizes within it with manager guidance; executes against someone else's vision. |
| PM | Owns and prioritizes the roadmap for their area; can articulate a near-term vision and defend trade-offs. |
| Senior PM | Defines a compelling vision for their product area and a roadmap that delivers it; evangelizes across the team. |
| Staff / Principal | Sets vision spanning multiple teams; manages a portfolio roadmap and the prioritization standards others use. |
| GPM / Director / VP | Owns the product vision for a whole area or company; the roadmap is the strategy made visible to the org. |
#How to grow it
- Write the vision as a narrative, not bullets. A short story about the customer's better future aligns people; a feature list does not. See Crafting a Product Vision.
- Convert your roadmap to Now/Next/Later and watch the date arguments soften. Building and Managing a Roadmap walks the conversion.
- Pick one prioritization framework and use it consistently for a quarter. Consistency beats sophistication. Start with RICE and Scoring Models or The Impact-Likelihood Matrix.
- Practice saying no out loud, with a reason. The reason is the product. A no without a rationale is just a brush-off.
#How AI is changing it
AI is eating the production of roadmap and prioritization artifacts while leaving the judgment untouched. First-draft prioritization, RICE scoring, roadmap formatting, and stakeholder-tailored summaries are increasingly one-prompt tasks, and Reforge explicitly lists auto-prioritization among the commoditized activities. What doesn't commoditize is the vision and the choice. A model will happily rank your backlog, but it has no opinion about which future is worth betting the company on, and no skin in defending that bet to a skeptical exec. Lenny's framing fits this competency cleanly: the PM becomes the editor of super-intelligent suggestions, and the durable value is the "people and glue," the vision that aligns humans and the conviction to hold a controversial roadmap. AI makes the artifact cheaper. It makes the taste behind it more valuable.
#Continue Reading
- Crafting a Product Vision is the deep dive on writing a vision that aligns people.
- Building and Managing a Roadmap for Now/Next/Later, outcome roadmaps, and saying no to dates.
- Prioritization Frameworks is the toolkit behind the Product Prioritization behavior.
- Strategic Impact is the competency upstream: the strategy this vision serves.
- The Initiative Pyramid for matching how much you involve senior leaders to how risky the bet is.