outcome-definition

Shifts thinking from feature delivery to measurable user or business outcomes. Use before building a feature, during roadmap planning, or while defining success metrics to ensure work ties to real results.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "outcome-definition" with this command: npx skills add pratikshadake/claude-product-management-skills/pratikshadake-claude-product-management-skills-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

  1. Define the desired user behavior change.
  2. Select a measurable success metric.
  3. Establish the current baseline.
  4. Set a realistic target improvement.
  5. 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.

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

General

value-vs-effort

No summary provided by upstream source.

Repository SourceNeeds Review
General

launch-readiness

No summary provided by upstream source.

Repository SourceNeeds Review
General

user-segment-prioritizer

No summary provided by upstream source.

Repository SourceNeeds Review
General

roadmap-reality-checker

No summary provided by upstream source.

Repository SourceNeeds Review