---
name: "Outcome definition framework"
repo: https://github.com/pratikshadake/claude-product-management-skills
source: https://github.com/pratikshadake/claude-product-management-skills/blob/HEAD/skills/outcome-definition/SKILL.md
license: "MIT"
install: "npx skills add pratikshadake/claude-product-management-skills --skill outcome-definition"
page: https://100xlab.com/resources/agent-skills/pratikshadake-claude-product-management-skills--outcome-definition--1ir1jj5
---

# 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](references/example.md) for a complete scenario.

---

## Supporting file: references/example.md

# Example: Outcome Definition — AI Meeting Notes

## Desired Outcome
Founders consistently capture decisions and action items automatically.

## Success Metric
% of meetings with recorded summary + actions.

## Baseline
~10% (manual notes only).

## Target
70% within 30 days of launch.

## Timeframe
30 days post-release.

## How Success Will Be Measured
Product analytics tracking summary generation per meeting.