# Outcome definition framework Human Guide

## What This Is For
Shifts thinking from feature delivery to measurable user or business outcomes. It gives the agent a clearer input/output frame for outcome definition framework: what context to ask for, what decisions to make, and what usable artifact to return.

Use this as a human-readable version of the Outcome definition framework agent skill. It is meant for marketers, operators, founders, and other non-coders who want the workflow without reading agent-specific implementation instructions.

## When To Use This
- Use this when you need a repeatable process for outcome definition framework.
- Use this when the task needs judgment, examples, constraints, or a clear output format rather than a one-off prompt.
- Use this when you want to hand an AI assistant enough context to produce a usable marketing artifact.

## When Not To Use This
- Do not use this when you only need a quick factual answer.
- Do not use this when the work depends on private data you cannot share with the assistant.
- Do not use this as a replacement for legal, compliance, financial, or medical review.

## What You Need Before Starting
- The goal or business outcome you want.
- The audience, customer segment, or market context.
- Any source material the assistant should respect, such as notes, briefs, examples, URLs, or brand guidance.
- Constraints such as tone, length, channel, deadline, region, or approval requirements.
- A clear definition of what a good final answer should look like.

## Step-By-Step Workflow
1. State the job clearly: "Use the Outcome definition framework guide to help me with..."
2. Add context: audience, goal, offer, channel, source material, and constraints.
3. Ask the assistant to identify missing inputs before producing the final output.
4. Have the assistant follow the skill-specific guidance below.
5. Review the result against the final checklist and ask for revisions where needed.

## Skill-Specific Guidance
- While defining success metrics
- Define the desired user behavior change.
- Select a measurable success metric.
- Establish the current baseline.
- Set a realistic target improvement.
- Define the evaluation timeframe.

## Decision Points And Nuance
The original skill emphasizes: Purpose, When to Use, Steps, Output, Desired Outcome, Success Metric, Baseline, Target, Timeframe, How Success Will Be Measured.

Use these questions to steer the work:
- What is the intended audience or buyer?
- What source material must be preserved?
- What should the assistant optimize for: clarity, persuasion, accuracy, speed, creativity, or conversion?
- What examples represent the desired quality bar?
- What should the assistant avoid?

## Common Mistakes
- Starting without a clear audience or goal.
- Asking for a final artifact before sharing examples or constraints.
- Accepting a generic first draft without checking it against the intended use.

## Copy-And-Paste Prompt
```text
Use the Outcome definition framework human guide.

My goal:
[Describe the business outcome]

Audience:
[Describe who this is for]

Context and source material:
[Paste notes, examples, links, or existing copy]

Constraints:
[Tone, length, channel, timeline, must-include items, must-avoid items]

Before producing the final output, ask me for any missing information that would materially improve the result.
```

## Final Checklist
- [ ] The output matches the original goal.
- [ ] The audience and context are reflected in the answer.
- [ ] Important constraints and source material were preserved.
- [ ] The assistant made the relevant decisions explicit.
- [ ] The final artifact is ready to use, review, or hand to the next person.

## Source
This guide was generated from the pratikshadake/claude-product-management-skills skill entry for `outcome-definition`.

## Source Skill Notes
These notes preserve the nuance from the original skill. Use them as supporting reference when the workflow above feels too generic.

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