User Story
A short description of a feature from the user's perspective, following the format "As a [user], I want [goal] so that [benefit]."
Definition
A user story captures a requirement from the end user's perspective. The standard format is: "As a [type of user], I want [action] so that [benefit]." User stories are intentionally brief - they're a placeholder for a conversation, not a specification. They're typically written on index cards or in project management tools, prioritized in a backlog, and estimated in story points.
Good user stories follow the INVEST criteria: Independent, Negotiable, Valuable, Estimable, Small, and Testable. They include acceptance criteria that define "done."
Why it matters for founders
User stories keep development focused on user needs rather than technical implementation. They prevent over-engineering by forcing you to articulate who benefits and why. They also facilitate better sprint planning and prioritization.
Example
Stripe's early user stories might have included: "As a developer, I want to accept payments with a single API call so that I don't have to build payment infrastructure from scratch." This story defined Stripe's core value proposition and guided their legendary developer experience.
How Foundra helps
Foundra's MVP Scope card essentially generates the highest-priority user stories for your product, defining what to build first and what value each feature delivers.
Start your free trial→Related free tools
Related terms
Sprint Planning
The process of selecting and committing to a set of work items to complete in a fixed time period.
Minimum Viable Product (MVP)
The simplest version of your product that lets you test your core hypothesis with real users.
Product Roadmap Planning
The strategic process of prioritizing features and defining the sequence of what to build and when.
Jobs to Be Done (JTBD)
A framework that defines products by the "job" customers hire them to accomplish.