outcome-definition
Outcome Definition Framework
Purpose
Shift thinking from feature delivery to measurable user or business outcomes.
When to Use
- Before building a feature
- During roadmap planning
- While defining success metrics
Steps
- Define the desired user behavior change.
- Select a measurable success metric.
- Establish the current baseline.
- Set a realistic target improvement.
- Define the evaluation timeframe.
Output
Desired Outcome
Success Metric
Baseline
Target
Timeframe
How Success Will Be Measured
References
See worked example for a complete scenario.
More from pratikshadake/claude-product-management-skills
prd-critic
Evaluates PRD quality for clarity, testability, and build-readiness across problem clarity, scope, acceptance criteria, edge cases, and metrics. Use before sharing a PRD with engineering to catch gaps early.
20launch-readiness
Audits whether a feature or product is truly ready for launch with a structured checklist and readiness status (Ready/At Risk/Not Ready). Use before any product launch to catch critical gaps.
18experiment-design
Designs fast, reliable validation experiments with hypothesis, method, success metric, and decision rules (Ship/Iterate/Kill). Use when you need to validate an assumption or test a product hypothesis before committing resources.
18assumption-mapper
Exposes hidden risks by identifying and ranking assumptions across desirability, feasibility, and viability categories. Use when evaluating new products or features to surface the highest-risk assumption to test first.
17roadmap-reality-checker
Detects unrealistic planning and hidden delivery risks like overcommitment, missing dependencies, resource mismatches, and undefined metrics. Use when reviewing quarterly roadmaps or sprint plans.
17problem-clarity
Evaluates whether a proposed idea addresses a genuine user problem worth solving. Use when assessing new feature ideas, startup concepts, or vague user complaints to determine if the pain justifies building a solution.
16