outcome-roadmap
SolidTransform an output-focused roadmap into an outcome-focused one that communicates strategic intent. Rewrites initiatives as outcome statements reflecting user and business impacts. Use when shifting to outcome roadmaps, making a roadmap more strategic, or rewriting feature lists as outcomes.
Install
Quality Score: 93/100
Skill Content
Details
- Author
- phuryn
- Repository
- phuryn/pm-skills
- Created
- 3 months ago
- Last Updated
- 5 days ago
- Language
- N/A
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
roadmap
Build or update a living product roadmap artefact (themes → outcomes → initiatives, Now/Next/Later horizons, confidence + gate metrics + dependencies). Trigger on: "build the roadmap", "update the roadmap", "create a roadmap", "roadmap for [quarter/product]", "what's our roadmap". Produces/maintains the roadmap ARTEFACT. To communicate it use comms (roadmap modes); to rank what goes on it use prioritisation.
roadmap-planning
Create outcome-based roadmaps using Now/Next/Later instead of Gantt charts. Use when asked to create a roadmap, plan quarterly, organize milestones, or figure out what to build over the next few months. Anti-date, anti-feature-list, pro-outcome.
outcome-orientation
Reframe work around measurable outcomes using OKRs, KPIs, and the outcome-vs-output distinction. Use when the user asks to define success criteria, write OKRs, set KPIs, clarify what "done" means in terms of impact, distinguish outputs from outcomes, or make a goal statement measurable and time-bound. NOT for ranking or scoring features by priority (use prioritization). NOT for systemic feedback-loop analysis (use systems-thinking).