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.

assets/executive_roadmap_template.md

View on GitHub
# [Product / Team] -- [Quarter] Roadmap (Executive)

**Strategy this roadmap serves:** [One sentence -- the strategic bet this quarter advances.]
**Sponsor:** [Exec sponsor name and title]
**Last updated:** [YYYY-MM-DD]
**Distribution:** [Board, exec team, investors]

---

## Now ([current quarter])

3-5 outcome-level items. Each item names an outcome the customer or business achieves, not a feature shipped.

| Outcome | Metric (KR) | Confidence | Lead PM |
|---------|-------------|------------|---------|
| [Outcome 1 -- customer-facing or business outcome] | [Specific metric and target, e.g., KR1: latency p95 480ms -> 250ms] | [High/Med/Low] | [Name] |
| [Outcome 2] | [Metric and target] | [High/Med/Low] | [Name] |
| [Outcome 3] | [Metric and target] | [High/Med/Low] | [Name] |
| [Outcome 4] (optional) | [Metric] | [High/Med/Low] | [Name] |
| [Outcome 5] (optional) | [Metric] | [High/Med/Low] | [Name] |

> **Confidence guide:** High = >=80% likely to deliver on plan. Medium = 50-80%; one or two known risks with credible mitigation. Low = <50%; material risks or external dependencies.

## Next ([next 1-2 quarters])

3-5 theme-level items. Outcomes named, but specific features not committed.

- **[Theme 1]** -- [outcome we are pursuing]
- **[Theme 2]** -- [outcome]
- **[Theme 3]** -- [outcome]
- **[Theme 4]** (optional) -- [outcome]

## Later ([H2 or beyond])

2-3 directions or bets. Deliberately fuzzy.

- **[Direction 1]** -- [the bet, one line]
- **[Direction 2]** -- [the bet]
- **[Direction 3]** (optional) -- [the bet]

## What we are explicitly NOT doing this period

2-3 items. Builds credibility by showing tradeoffs.

- [Item we considered but deferred] -- [reason: e.g., "sequenced for 2027 after market signal stabilizes"]
- [Item we considered but rejected] -- [reason]

---

## Notes for executive readers

- Items in "Now" have committed plans; "Next" is directional; "Later" is exploratory.
- Confidence ratings reflect our honest read; we will not inflate to manage perceptions.
- Updates published quarterly on [date]. Material changes communicated within 1 business day.

**Trace back to internal source:** [link to internal variant]
**Trace back to OKRs:** [link]
**Trace back to NSM:** [link]
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