Product Management: Foundations to Practice · Agile Product Development
Writing Effective User Stories
A user story's format is not a bureaucratic formality; it exists specifically to keep requirements anchored to real user motivation rather than implementation detail.
A user story is typically written in the format popularized by Mike Cohn: as a type of user, I want some goal, so that some benefit, a structure that keeps a requirement anchored to a real user need and its underlying motivation rather than describing an implementation detail in isolation. The 'so that' clause is frequently the most valuable and most skipped part, since it forces the author to articulate why the goal matters, which often reveals whether the proposed solution is actually the best way to achieve that underlying benefit.
- The 'so that' clause in a user story is the most valuable and most often skipped part, since it reveals the underlying motivation.
- Acceptance criteria should be written before development starts, not retrofitted to match whatever was actually built.
- Writing stories from the system's perspective rather than a real user's loses the connection to genuine user value.
- Oversized stories should be split into smaller pieces that each still deliver independently observable user value.