# User story

Concept · [Product](https://ecosystem.samcarlton.com/product)

Also called: user stories, story, use case, requirement

One short sentence describing something a user needs to do and why, written from their point of view. It helps the people building the product understand the goal, not just [the screen](https://ecosystem.samcarlton.com/front-end).

**For example:** As a parent, I want to see today's pickup time on the first screen so that I am not late.

## Connects to (6)

- [Scope](https://ecosystem.samcarlton.com/scope): The agreed list of what a project will include and what it will not.
- [Backlog](https://ecosystem.samcarlton.com/backlog): The running list of new abilities, fixes and ideas waiting to be worked on, usually in order of priority.
- [Wireframe](https://ecosystem.samcarlton.com/wireframe): A simple outline drawing of a screen that shows where things go, without colors or finished design.
- [Spec](https://ecosystem.samcarlton.com/spec): A written description of what is being built and why, for work too big to finish in one session.
- [User journey](https://ecosystem.samcarlton.com/user-journey): The sequence of steps a person takes to reach a goal with a product, from first contact to done, including what they think and feel along…
- [Product requirements document](https://ecosystem.samcarlton.com/product-requirements-document): A document that explains what a product or feature should do, for whom and why, so the team agrees before building.

Map view: https://ecosystem.samcarlton.com/user-story