How do you write a good user story?
Model answer
Model answerA good user story is a unit of value, not a unit of work. The classic format — 'As a [persona], I want to [action], so that [outcome]' — is useful but often misused. The 'so that' is the most important part: it forces you to articulate the actual benefit. Bad user stories describe implementation ('add a button that does X'). Good ones describe intent ('so that users can complete checkout without re-entering their address'). I'd also add acceptance criteria: a clear, testable definition of done that eng and design agree on before work starts.
Framework · User Story Framework
- PPersona first
As a [specific persona]' — not 'as a user'. Specificity makes the story testable - AAction is the want
I want to [do something]' — describes the behavior, not the feature - OOutcome is the why
So that [benefit]' — the most skipped part. If you can't write this, the story isn't ready - AAcceptance criteria
Testable conditions that define done — agreed by PM, design, and eng before work starts
Related questions
- How would you prioritize building for power users vs. new users?
- A major competitor just launched a feature you were building. What do you do?
- How do you align stakeholders when they disagree on the roadmap?
- How would you evaluate the ROI of a product investment before building it?
- How would you evaluate a potential acquisition target from a product perspective?