Rewrite roadmaps as outcome-focused plans
transform-roadmapcommandsetup L1★11,239
phuryn/pm-skills ↗What it does
Rewrite feature roadmaps as outcome-focused statements
Best for
Product teams transitioning from output-focused to outcome-focused planning, especially before executive presentations or quarterly planning.
Inputs
- · Feature list or backlog items
- · Roadmap document (Now/Next/Later format)
- · Product goals or OKRs
- · Target audience for roadmap
Outputs
- · Outcome-focused roadmap with success metrics
- · Feature-to-outcome mapping table
- · Transformation summary document
Preconditions
- · Current roadmap or feature list available
- · Product goals defined (optional but recommended)
Failure modes
- · Struggles with vague feature descriptions
- · May assign wrong outcomes to multi-purpose features
- · Assumes outcome-first thinking is desired without validation
Trust signals
- · Before/After transformation examples provided
- · Outcome format template: [Verb] [metric/experience] for [user segment]
- · Grouping strategy for related features under single outcome
- · Follow-up offers (OKR alignment, risk identification)