Skip to content

borghei/Claude-Skills / project-management/execution/roadmap-communication

roadmap-communication

Verified

Produce executive, customer and internal versions of one roadmap with consistent framing and the right detail and risk language for each. Use when publishing the quarterly roadmap, a board packet or a customer or sales roadmap.

references/roadmap-variants-playbook.md

View on GitHub
# Roadmap Variants Playbook

> Read this when building the three roadmap variants: the variant comparison tables, the "right-size the roadmap" principle, outcome-vs-feature framing, the detailed structure for each of the executive / customer / internal variants, the authoring workflow, troubleshooting, and success criteria. (For the origin of Now/Next/Later and full worked examples, see `roadmap-communication-guide.md`.)

## The three variants

| Variant | Audience | Time horizon detail | Risk framing | Format |
|---------|----------|---------------------|--------------|--------|
| **Executive** | Board, exec team, investors | Outcome-led; quarterly | Confidence levels (high/med/low) | 1-page narrative + simple visual |
| **Customer** | Customers, partners, sales prospects | Theme-led; "this year / later this year / next year" | No risk language; "exploring", "in development", "shipping soon" | Themes + benefit statements, no dates beyond current quarter |
| **Internal** | Engineering, design, support, account teams | Feature-led with dependencies | Explicit risks with mitigations | Detailed table with owners, dependencies, links to PRDs |

### What changes across variants

| Element | Executive | Customer | Internal |
|---------|-----------|----------|----------|
| **Granularity** | Outcomes (3-7 items) | Themes (5-10 items) | Features (15-50 items) |
| **Time horizon** | This quarter / next quarter / H2 | Now / Next / Later (themes only) | Sprint-by-sprint for "Now"; quarter for "Next" |
| **Dates** | Quarter only | Quarter only for "Now"; "later this year" for "Next" | Specific sprint and release dates for "Now" |
| **Risk** | Confidence per outcome | None (use language like "exploring" / "shipping soon") | Explicit: tigers, mitigations, dependencies |
| **Owner** | Exec sponsor per outcome | None | PM, EM, design lead per feature |
| **Metric** | Outcome metric + target | Benefit statement | KR + leading indicator |
| **What's NOT here** | Implementation detail, risk discussion | Risk, dependencies, internal team names | Marketing language, exec framing |
| **Visual** | Now/Next/Later 3-column or Gantt-summary | Themed cards or simple Now/Next/Later | Detailed table or Gantt |

## The "right-size the roadmap" principle

Marty Cagan's observation: **forecast confidence drops sharply with time horizon**. A 2-week commitment can be 90% confident. A 1-quarter commitment is maybe 70%. A 1-year commitment is 30% at best. Pretending otherwise (by promising features 9 months out) trains customers to disbelieve every roadmap you publish.

The Now / Next / Later structure encodes this honesty:

- **Now (this quarter):** Specific features with committed dates. Build is in flight or starting imminently. High confidence.
- **Next (next 1-2 quarters):** Themes with named outcomes, but specific features are not committed. Medium confidence.
- **Later (beyond):** Directions, hypotheses, big bets. Deliberately fuzzy. Low confidence by design.

Each audience needs this honesty calibrated:

- **Executives** want confidence ratings on each item (so they can plan).
- **Customers** want forward visibility without firm dates (so they can buy with confidence in the direction).
- **Internal teams** want explicit dependencies and risks (so they can execute).

## Outcome-based vs feature-based roadmaps

A second axis: **outcomes vs features**. Cagan and Torres both argue for outcome-based roadmaps -- the roadmap promises a customer outcome ("reduce onboarding from 14 days to 3 days"), not a feature ("ship guided onboarding wizard"). Outcomes survive scope changes; features become commitments that bind you to wrong solutions.

| Variant | Default orientation |
|---------|---------------------|
| Executive | Outcome-based always |
| Customer | Mix: themes (outcomes) for Next/Later; specific features for Now (when they are committed) |
| Internal | Feature-based for execution, but each feature must trace to an outcome |

The translation from feature to outcome is the highest-leverage move a PM can make in roadmap communication. "We are shipping X" is a feature. "Customers can now achieve Y" is an outcome.

## Variant 1: Executive Roadmap

**Purpose:** Build confidence that the team is solving the right problems and is on track.

**Length:** 1 page (slide or memo).

**Structure:**

1. **Header:** Quarter, sponsor, the one-sentence strategy this roadmap serves.
2. **Now (this quarter) -- 3-5 outcomes:** Each outcome named, with metric target, confidence rating (High/Med/Low), and lead PM.
3. **Next (next quarter) -- 3-5 outcomes:** Theme-level. No specific features. Confidence is implicit (Medium).
4. **Later (H2 directions) -- 2-3 big bets:** One line each. Deliberately fuzzy.
5. **What we are explicitly NOT doing this period:** 2-3 items. Builds credibility by showing tradeoffs.

**Voice:** Direct, plain, confident-but-honest. No marketing adjectives. No "leveraging" or "synergizing." Bezos memo style.

**Visualization:** Now/Next/Later 3-column or a slim Gantt of the 3-5 Now-quarter outcomes. Avoid swim-lane explosions.

## Variant 2: Customer Roadmap

**Purpose:** Help customers and prospects make confident purchase or expansion decisions; help sales sell direction without overcommitting.

**Length:** 2-5 themed cards (web page or 1-2 slides).

**Structure:**

1. **Header:** "What's coming in [year]" -- positions roadmap as a window, not a contract.
2. **Now (this quarter) -- 3-5 themes with named features:** "Workflow automation: Connect tasks to your CRM with built-in triggers. Available this quarter."
3. **Next -- 3-5 themes, features unnamed:** "Reporting: deeper drill-down across teams and saved-view collaboration. Coming later this year."
4. **Exploring (Later) -- 2-3 directions:** "Exploring: AI-assisted task creation from meeting notes. Early experiments underway."

**Voice:** Benefits-led, customer-perspective. No internal team names. No release versions. No risk language. Use directional language ("exploring", "in development", "shipping soon") instead of dates beyond the current quarter.

**Visualization:** Themed cards (Notion / Productboard / Cards format). Avoid Gantt -- it reads as a commitment.

**Important caveats to repeat on the page:**

- "This roadmap is directional and may change as we learn from customers."
- "Items in 'Exploring' are not commitments."
- "Dates are based on current planning and may shift."

## Variant 3: Internal Roadmap

**Purpose:** Coordinate execution across teams; surface risks, dependencies, and capacity issues; enable detailed sprint planning.

**Length:** Detailed table or multi-tab spreadsheet/wiki. No length limit.

**Structure:**

1. **Header:** Quarter, sponsor, strategy reference, link to NSM and OKRs.
2. **Now (this quarter) -- features by team:**
   - Feature name, PM, EM, design lead, status, target sprint/release, KR mapped, dependencies, risks
3. **Next (next 1-2 quarters) -- themes with candidate features:**
   - Theme, PM, EM, target quarter, dependencies expected, open questions
4. **Later (H2) -- directions and hypotheses:**
   - Direction, sponsor, what we'd need to be true to commit
5. **Cross-cutting dependencies:** Platform changes, infra work, external vendor work
6. **Capacity view:** Team commitment vs available capacity per quarter

**Voice:** Direct, candid, complete. Risks named explicitly. Mitigations specified. Dependencies traced. This document trains trust internally and is the source of truth for the other two variants.

**Visualization:** Detailed table (sortable by team, quarter, status). Cross-link to PRDs (`create-prd/`), OKRs (`brainstorm-okrs/`), NSM (`north-star-metric/`), and PR/FAQs (`prfaq/`).

## Workflow

1. **Author the internal variant first.** This is the source of truth. All fields, all risks, all dependencies. Use the template in `assets/internal_roadmap_template.md`.
2. **Derive the executive variant.** Strip implementation; promote each Now item to its parent outcome; assign confidence ratings; remove dependencies; cap at 1 page.
3. **Derive the customer variant.** Translate features into customer benefits; strip dates beyond current quarter; remove risk language; use "exploring / in development / shipping soon."
4. **Run a triangulation check.** Pick one item in the Now bucket. Trace it from the internal feature to the executive outcome to the customer benefit. The three should be consistent -- different framings of the same thing.
5. **Distribute with named recipients.** Each variant has a distribution list. The internal variant is wiki-published; executive is in the board packet; customer goes on the public site or in sales decks.
6. **Re-publish on a fixed cadence.** Quarterly is standard; monthly for fast-moving startups.
7. **Update the customer variant LAST.** Customer-facing language outlives the items; surprise changes erode trust more than slow updates would.

## Troubleshooting

| Symptom | Likely Cause | Resolution |
|---------|--------------|------------|
| Sales reps quote internal roadmap dates to prospects | One roadmap is being used by all audiences | Publish three variants; restrict internal-variant access; train sales on the customer variant |
| Executives say "I do not understand what's changing" between roadmap updates | Executive variant is feature-level instead of outcome-level | Rewrite Now items as outcomes; cap at 5 items per quarter |
| Customers feel misled when a "Later" item never ships | Customer variant uses commitment language for Later items | Use exploratory language ("exploring", "early experiments"); add the standard caveats line |
| Engineers feel managed by the customer variant | Customer variant lacks risk and the team feels accountable for the marketing version | Make the internal variant the operational source of truth; route engineering planning off internal only |
| The three variants drift apart over the quarter | No re-publication cadence; only updated when there's "news" | Publish on a fixed quarterly cadence; force the triangulation check at each update |
| Customer variant has 30 items | Mistaking comprehensiveness for transparency | Cap at 5-10 themes. More items dilute the signal and increase the surface area for "we never shipped X" |
| Internal variant lacks owners/dates | Created as a marketing asset, not as an execution tool | Make ownership and dates mandatory fields; reject roadmap entries without them |

## Success Criteria

- Every Now-quarter item exists in all three variants with consistent identity (same ID, different framing)
- The executive variant fits on one page and has 3-5 outcome items per Now-quarter
- The customer variant uses no internal team names, no dates beyond current quarter, and includes the directional caveats
- The internal variant has owner, dependencies, risks, and KR mapping for every Now item
- The triangulation check passes for every published roadmap (each item traces consistently across variants)
- Roadmaps are republished on a predictable cadence (quarterly minimum)
- A customer reading the customer variant 6 months later does not feel misled
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall