User Story Components: Personas and Goals
You'll learn how to identify specific users and their concrete goals instead of writing vague, generic user stories.
Why Generic "Users" Don't Work
When writing user stories, it's tempting to write: "As a user, I want to..." But which user? Your application might serve completely different people with different needs. A "user" could be a customer, an administrator, a guest, or a power user—each with distinct goals.
The Persona: Who Is This For?
A persona is a specific type of user with particular characteristics and needs. Instead of "user," think:
- "As a new customer..."
- "As a content moderator..."
- "As a billing administrator..."
- "As a mobile shopper..."
The persona should reflect a real role or user type that matters to your system. This helps everyone understand whose problem you're solving.
The Goal: What Are They Trying to Accomplish?
The goal portion answers: "What does this persona need to achieve?" It should be specific and outcome-focused:
❌ Poor: "As a user, I want to use the search feature"
✅ Better: "As a returning customer, I want to find my previous orders so I can track shipments"
Notice how the better version tells you WHO (returning customer) and WHY they care (tracking shipments), not just WHAT feature exists.
Making Them Work Together
Think of personas and goals as a pair: the persona provides context about who's using the system, while the goal explains what success looks like for that person. Together, they replace assumptions with clarity.
Key Takeaway: Replace generic "user" descriptions with specific personas and concrete goals to make user stories clear, actionable, and focused on real needs.