# Narrative Led Roadmapping

> Shift from managing a spreadsheet of features to leading with a theme-based narrative. Use this when stakeholders are lost in the details of a feature list, when the team feels disconnected from the product vision, or when you need to justify shifting priorities based on new user insights.

- Skill: `samarv/narrative-led-roadmapping` (Agent Skill)
- Install (CLI): `npx skillmds@latest add samarv/narrative-led-roadmapping`
- Raw SKILL.md: https://api.skillmd.com/api/skills/samarv/narrative-led-roadmapping/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Data & Analytics
- Author: samarv (https://skillmd.com/u/samarv)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/samarv/narrative-led-roadmapping

---


# Narrative-Led Roadmapping

Traditional roadmapping often fails because it presents a list of features without a cohesive "why." By treating a roadmap as a narrative story built on strategic themes, you provide the scaffolding necessary for your team to make autonomous execution decisions while keeping stakeholders aligned on the vision.

## The Process

### 1. Identify Your Strategic Levers
Before listing projects, identify the 3–5 high-level "levers" or "themes" that will drive the business forward. 
- Ask: "What is the story we are telling about our users this quarter?"
- Example: Instead of "Improve Login," the theme might be "Reducing Friction for Non-Technical Creators."

### 2. Draft the Narrative Story
Write 1–3 paragraphs explaining the current state of the user, the problems they face, and how the proposed body of work changes their reality.
- Focus on outcomes, not outputs.
- Explain the logic: "Because we learned [Input], we are pulling [Lever] to achieve [Outcome]."
- Ensure the narrative is robust enough that if an individual project fails, the theme still makes sense.

### 3. Build the Theme Scaffolding
Organize your roadmap by themes rather than by date or team. For each theme, include:
- **The Objective:** What does "crushing it" look like qualitatively?
- **The Projects:** A list of high-level initiatives that support the theme.
- **The Inputs:** The data or research (e.g., "we have more power users than expected") that justifies this theme.

### 4. Link to Living Systems
Avoid the "Static Spreadsheet Trap." Use a document (Doc) for the narrative and link out to live execution tools (Jira, Linear, etc.) for the details.
- Use the Doc for the "Why" and the "What."
- Use the Project Management tool for the "How" and the "When."
- This prevents the roadmap from becoming a snapshot that is immediately out of date.

---

## Examples

### Example 1: Technical Platform Roadmap
**Context:** A team is overwhelmed by a backlog of bug fixes and feature requests for a complex design tool.
**Input:** User feedback indicates that while the tool is powerful, it is "janky" and hard to learn.
**Narrative:** "Our power users love our flexibility, but the 'activation hump' is too high. This quarter, we are focusing on **The Polished Professional** theme. We will prioritize performance and keyboard shortcuts over new feature sets to ensure our core experience feels like a pro-grade instrument."
**Output:** A roadmap where 70% of resources are allocated to "Performance Spikes" and "UI Polish," justified by the "Polished Professional" narrative.

### Example 2: Marketplace Growth Roadmap
**Context:** A marketplace needs to increase trust between buyers and sellers.
**Input:** Data shows that users drop off when they can't predict the quality of a listing.
**Narrative:** "The **Radical Transparency** theme aims to eliminate 'listing anxiety.' We are moving away from manual inspections (which don't scale) and toward automated quality signals. By leveraging guest review data, we will give buyers a 100% predictable view of their purchase before they click buy."
**Output:** A roadmap focused on "Review System Overhaul" and "Automated Photo Tagging" rather than "Hiring 50 New Inspectors."

---

## Common Pitfalls

- **The Spreadsheet Trap:** Thinking a RICE-scored spreadsheet (Reach, Impact, Confidence, Effort) is a roadmap. Spreadsheets are prioritization tools; narratives are alignment tools.
- **Lacking a "Go/No-Go" Milestone:** Not defining the point at which you will stop a project if the research doesn't support the theme.
- **Over-Hiring for the Vision:** Hiring a massive team to build a "big vision" before validating the core theme. Keep the team lean until the "tech spikes" prove the path is viable.
- **Solving for the Solution:** Getting attached to a specific implementation (e.g., "We must build a chatbot") rather than the theme (e.g., "Improving User Support"). Always edit the "How" to fit the "Why."