User Stories & Acceptance Criteria

Summary

A user story frames a requirement from the user's perspective ('As a [user], I want [goal], so that [reason]'); acceptance criteria define exactly when that story is considered done.

How to Learn This

1Write 5 user stories for a feature, each with 2-3 acceptance criteria.
2Practice the Gherkin 'Given-When-Then' format for acceptance criteria.
3Learn why vague acceptance criteria cause the most PM-engineer friction.

Writing a PRD (Product Requirements Doc)

Epics vs Stories vs Tasks

More topics in Requirements & Documentation

Writing a PRD (Product Requirements Doc)Epics vs Stories vs Tasks One-Pagers & RFCs Edge Case Thinking Non-Functional Requirements Wireframing Basics Writing Feature Specs Writing for Engineers vs Executives

Stuck on this topic? Ask an Insider

Get 1:1 guidance from people who've walked this exact path — free on the InsideEdge app.

Download