# 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.

- Skill: `pratikshadake/outcome-definition` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add pratikshadake/outcome-definition`
- Raw SKILL.md: https://api.skillmd.com/api/skills/pratikshadake/outcome-definition/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- Author: pratikshadake (https://skillmd.com/u/pratikshadake)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/pratikshadake/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](references/example.md) for a complete scenario.