Stakeholder Roadmap Template for Product Planning

No. Create audience-specific versions. Executives need strategic context and outcome metrics. Sales needs confidence levels and talk tracks. Customers need theme descriptions and broad timelines. Use this template as a base and adjust the detail level, language, and appendix for each audience. The [Stakeholder Management Handbook](/stakeholder-guide) covers tailoring communication by audience.

Redirect to confidence levels. "SSO is Committed for Q2. That means resources are assigned and we expect to deliver within Q2. I cannot give a specific week because the engineering work has not been fully scoped yet. I will update you as we get closer." If they push harder, ask: "What decision are you trying to make that requires an exact date? Let me help you plan around a range instead." The [guide to building a product roadmap](/guides/how-to-build-a-product-roadmap) covers expectation management in more detail.

Quarterly for board and executive audiences. Monthly for sales teams (because deal cycles are shorter and they need current information). Ad hoc for customers (typically when there is a meaningful change to a theme they care about). Never present a stale roadmap. If the last update was 3 months ago, refresh it before presenting.

Say: "That is not on our current roadmap. Here is why." Then explain what is on the roadmap and why it is higher priority. Log the request. If the same request comes from multiple stakeholders, it signals a gap in your prioritization model. Use the [RICE Calculator](/tools/rice-calculator) to score the request against current items and see where it ranks.

No. Do not frame your roadmap as "catching up to competitors." Frame it as "solving the problems our customers care about." If a customer asks "Competitor X has feature Y, will you build it?", answer with the relevant theme from your roadmap. If the feature aligns with a theme, say so. If it does not, explain what you are prioritizing instead and why. ---