Build an outcome-based user persona

Outcome-Based Personas Beat Demographic Sketches

Demographic personas ("marketing manager, 32, urban") produce no product decisions. Outcome-based personas — centered on what the user is trying to achieve and how they know they succeeded — map to features. Teresa Torres' discovery writing and JTBD.info's foundational framing both argue that demographic sketches are residue from marketing and not useful for product prioritization.

How the Build an outcome-based user persona Prompt Works

The prompt structures personas around outcomes, current approach, forces for change, and decision triggers — with an anti-persona as the explicit out-of-scope check. The "persona we thought was primary but actually isn't" output is the reality check; most initial personas don't survive the first round of switch interviews.

When to Use It

• Demographic personas exist but don't inform decisions.
• A new market or segment requires persona work.
• A new PM is onboarding and needs persona grounding.
• A prioritization debate keeps happening because nobody knows who we serve.
• A marketing or sales team is asking for clearer customer definitions.

Common Pitfalls

• Demographic persona as primary artifact. Age and role don't predict behavior. Outcomes do.
• No anti-persona. Without anti-persona, the team will try to serve everyone. Anti-personas create focus.
• Personas without research backing. Made-up personas produce made-up features. Ground every persona in research.

Sources

• Continuous Discovery Habits — Product Talk (Teresa Torres)
• What is Jobs-to-be-Done? — JTBD.info
• Opportunity Solution Tree — Product Talk (Teresa Torres)
• Assessing Product-Market Fit — Silicon Valley Product Group