ProductSetupAI-generated

Roadmap Narrative

Wrap a roadmap in a compelling "why" story that gets stakeholders aligned

What it is

Wrap a roadmap in a compelling "why" story that gets stakeholders aligned

Drafts a written narrative for a product roadmap — a "north star" story that explains the strategic theme, why now, and how the planned work connects to business goals. Calibrated to the audience so executives get strategy and engineers get context.

What you'll get

Custom instructionsCompiled from your answers, editable before you export.

Roadmap narrative frameworkA five-section narrative template with audience calibration notes and trade-off framing so every roadmap tell is structured, strategic, and audience-appropriate.

Export bundle for Claude ProjectsCopy-paste blocks with a guided walkthrough.

Try it on

Write an executive roadmap narrative for an onboarding themescenario · built in

Claude should produce a five-section narrative written for executives — business-outcome led, no technical implementation detail. Section 2 must explain why onboarding is the bottleneck now (using only provided context). Section 4 must use the specific 7-to-under-2-day metric as a target. Section 5 must explicitly name something deferred. Claude must not fabricate activation rates, churn data, or competitive context.

Write an engineering team roadmap narrative for a stability themescenario · built in

Claude should write for an engineering audience — the sequencing rationale in section 3 should explain why reliability work ships before new features (e.g., incidents reduce velocity more than pausing feature work does). Section 5 must name specific feature work that is deferred and why. The tone should be collaborative and technically grounded. Claude must not fabricate incident counts, SLA figures, or engineering velocity metrics.

Compiled preview

You write roadmap narratives for {{productName}}. Time horizon: {{timeHorizon}} Primary theme: {{primaryTheme}} Audience: {{audienceType}} Write a roadmap narrative with the following structure: 1. Where we are now (1–2 sentences grounding the reader in the current state) 2. Why this theme, why now (2–3 sentences: the business or user problem driving this direction) 3. What we are building and in what order (connect the roadmap items to the theme — do not just list features) 4. What success looks like by the end of {{timeHorizon}} (2–3 specific, observable outcomes) 5. What we are not doing and why (explicit trade-offs made to stay focused) Audience calibration: - Executive leadership: …