User Story
A short, informal description of a feature written from the user's perspective in the format: As a [type of user], I want [action] so that [benefit]. User stories capture requirements in terms of user value rather than technical specifications.
User stories serve as placeholders for conversation rather than detailed specifications. They deliberately omit implementation details to encourage the team to discuss the best approach during sprint planning. The three Cs capture the essence: a Card with the story, Conversation about the details, and Confirmation criteria that define when it is done.
For AI features, user stories help teams maintain focus on user outcomes rather than technical complexity. Instead of writing a story about implementing a neural network, teams write stories like As a content marketer, I want article summaries generated automatically so that I can process industry news faster. This framing ensures the team evaluates success based on whether the user's need is met rather than whether the model achieves a particular accuracy score. Growth teams write stories focused on the growth loop: As a new user, I want to see AI recommendations immediately so that I experience the product's value before the trial expires. These stories connect AI capabilities directly to acquisition and activation metrics.
Related Terms
Product-Market Fit
The degree to which a product satisfies strong market demand. Achieving product-market fit means customers are actively seeking, using, and recommending your product because it solves a real and pressing problem for them.
Jobs to Be Done
A framework that defines customer needs as functional, emotional, and social jobs people hire products to accomplish. It shifts focus from demographic segments to the underlying progress customers are trying to make in specific circumstances.
Minimum Viable Product
The simplest version of a product that can be released to test a core hypothesis with real users. An MVP delivers just enough functionality to gather validated learning while minimizing development time and cost.
Minimum Lovable Product
An evolution of the MVP concept that emphasizes delivering enough quality and delight that early users genuinely love the product. It balances speed-to-market with the emotional engagement needed to drive organic word-of-mouth growth.
Design Sprint
A five-day structured process for rapidly prototyping and testing ideas with real users. Developed at Google Ventures, it compresses months of debate into a focused week of mapping, sketching, deciding, prototyping, and testing.
Lean Startup
A methodology for developing businesses and products through validated learning, rapid experimentation, and iterative releases. It emphasizes reducing waste by testing assumptions before building fully-featured solutions.