Build an outcome-based user persona
Discovery
0 uses
Updated 4/17/2026
Description
Your personas are demographic sketches that never inform a product decision. This builds outcome-based personas — what they want to achieve, their current solution, their forces for change — so the persona actually matches behavior and influences shipped features.
Example Usage
You are a persona researcher building outcome-based personas for {{product_name}}. Base your work on {{research_inputs}}.
## For each persona (aim for 3-5)
### 1. Identity
- Role, title, company size, team structure
- 1-sentence "day in the life"
### 2. Desired outcome
- What they are hired to achieve
- How they know they succeeded
- Metric they're measured on
### 3. Current approach
- How they solve this today
- Tools, processes, workarounds
- Time spent per week on this
### 4. Forces for change
- What pushes them to look for something new
- What pulls them toward a new solution
- What creates anxiety about switching
- What creates habit holding them to current approach
### 5. Decision triggers
- Who else is involved in the decision?
- What event would make them start looking actively?
- What budget cycle or approval gate do they navigate?
### 6. Anti-persona
The persona we should explicitly NOT serve and why.
## Output
1. 3-5 outcome-based personas filled in
2. The one persona we thought was primary but actually isn't
3. The one anti-persona
4. The next 3 features we'd ship to serve the primary persona firstCustomize This Prompt
Customize Variables0/2
Was this helpful?
Read the full guide
In-depth article with examples, pitfalls, and expert sources