Smithery is now a part of Arcade.dev! Read more in our announcement here
Master product roadmaps including roadmap types (timeline, outcome-based, Now-Next-Later), communication strategies, and prioritization...
Frameworks for building, communicating, and managing product roadmaps that align teams, guide execution, and drive strategic outcomes.
A roadmap is a strategic communication tool that:
NOT: A list of features with dates BUT: A strategic narrative about the future
Good roadmaps: Outcome-oriented, flexible, strategic, audience-appropriate, actionable
Bad roadmaps: Feature lists, hard dates, everything for everyone, disconnected from strategy, stale
Auto-loaded by agents:
roadmap-builder - For Now-Next-Later, theme-based, and outcome roadmapsUse when you need:
Structure: Three buckets without dates
## NOW (High confidence - actively building)
- [Initiative]: [Outcome] — Owner: [name], Status: [in-progress]
## NEXT (Medium confidence - validated, queued)
- [Initiative]: [Outcome] — Target: [quarter]
## LATER (Low confidence - exploring)
- [Initiative]: [Outcome] — Needs: [validation step]
When to use: Maximum flexibility, minimal commitment, high uncertainty
Benefits:
Template: assets/now-next-later-template.md
Complete template with examples, confidence levels, updating guidance
Structure: Strategic themes with grouped initiatives
Organize by themes (e.g., "Enterprise Readiness", "Customer Experience") rather than features.
When to use: Communicate strategic focus areas
Benefits:
Structure: Lead with results, not outputs
Focus on customer/business outcomes (e.g., "Reduce churn by 50%") with flexible approaches.
When to use: Results-driven teams, goal-driven culture
Benefits:
Template: assets/outcome-roadmap-template.md
Includes outcome format, examples, comparison with feature roadmaps
Structure: Initiatives plotted on calendar/quarters
Visual timeline showing sequencing and dependencies.
When to use: Internal planning only, complex dependencies
NOT for: External communication (creates date expectations)
Choosing the right type: See references/roadmap-types-guide.md for detailed comparison and selection criteria.
Different audiences need different roadmaps:
Focus: Strategy, business outcomes, resource needs Format: Themes + outcomes, annual + quarterly Detail: Low (strategic)
Focus: Value delivery, transparency Format: Now-Next-Later with problem framing Exclude: Internal work, hard dates
Focus: Deal enablement, competitive positioning Guidance: "Commit to Now, position Next as likely, describe Later as exploring"
Focus: Execution, technical detail Format: Timeline with dependencies Detail: High (sprint-plannable)
Focus: Company alignment, transparency Frequency: Quarterly updates
Comprehensive guide: references/roadmap-communication-guide.md
Includes communication tactics, update formats, anti-patterns
Step 1: Establish Strategy (company goals, product strategy, market position)
Step 2: Gather Inputs (customer feedback, business priorities, technical needs, competitive intel)
Step 3: Prioritize (RICE, Impact/Effort, Strategic Fit)
Step 4: Define Themes (3-5 customer-centric, strategic themes)
Step 5: Sequence (dependencies, resources, timing, value delivery)
Step 6: Validate & Align (exec, engineering, sales/CS, customers)
Step 7: Communicate (audience-specific views, all-hands, documentation)
Detailed guide: references/roadmap-building-guide.md
Includes detailed steps, outputs, prioritization frameworks, maintenance cadence
Tell the story of your roadmap - where, why, how:
Structure:
Template: assets/roadmap-narrative-template.md
DO:
DON'T:
Common mistakes:
Weekly (30 min): Current work on track? Adjust "Now"
Monthly (60 min): Progress on quarter, validate "Next", refine "Later"
Quarterly (Half day): Build next quarter roadmap, review outcomes
DO update:
DON'T update:
When roadmap changes materially:
Roadmap Update: [Date]
What Changed: [Change + Why]
What Stayed: [Core themes still priority]
Impact: [Who this affects]
Frequency: Only material changes
Simplify:
Timeline: 4-6 hours for quarterly roadmap
Key: Simple beats perfect. Better a clear 1-page roadmap than elaborate 20-page deck nobody reads.
Lightweight (Early stage):
Purpose-Built (Growth):
Custom (Enterprise):
Recommendation for solo/small teams: Start with slides, upgrade only when pain is real.
Copy-paste these for immediate use:
assets/now-next-later-template.md - Most flexible format, complete exampleassets/outcome-roadmap-template.md - Results-focused formatassets/roadmap-narrative-template.md - Storytelling structureWhen you need comprehensive guidance:
references/roadmap-types-guide.md - All types compared, selection criteriareferences/roadmap-communication-guide.md - Audience-specific roadmaps, communication tacticsreferences/roadmap-building-guide.md - 7-step process, prioritization, maintenance"Stakeholders treat the roadmap as a commitment": You're using a timeline roadmap when you should use Now-Next-Later. Switch formats. If you must use dates, add confidence levels (high/medium/low) and present ranges, not fixed dates.
"My roadmap is a feature list": Reframe around outcomes. Instead of "Build notifications feature" write "Reduce churn by 15% through proactive user re-engagement." Features are implementation details, not strategy.
"The roadmap is outdated within a week": Your review cadence is too infrequent. Set a monthly review rhythm. Also check if you're putting too much detail on the roadmap -- keep it at the initiative level, not the task level.
prioritization-methods - Prioritization frameworks (RICE, ICE, Impact/Effort)product-positioning - Strategic positioninggo-to-market-playbooks - Launch planning and GTM strategyFor your first roadmap:
assets/now-next-later-template.mdFor quarterly planning:
Key Principle: Roadmaps are strategic communication tools, not commitments. They show direction and rationale, enabling alignment while maintaining flexibility. Good roadmaps create clarity without over-committing. Update regularly, communicate changes, focus on outcomes.
