# Use Case

> One way someone uses a product to reach a goal. It is written as steps.

**Field:** Business & Startups  
**Category:** Product Management  
**Also known as:** Use Cases, Business Use Case, AI Use Case

## Think of it like

It is like a recipe card for one meal. It says who cooks, what the meal is, and each step.

## Definition

A use case describes one way a person uses a product or tool to reach a goal. It names the user, the goal and the steps between them. It also says what happens when a step goes wrong. Teams write them to agree on what a product must do. In business, the word also means one task where a tool earns its place, such as AI sorting support emails. Ivar Jacobson brought the idea to software in 1987.

## Example

A bank writes a use case for a customer who lost a password. It lists the steps from the reset link to the new login, and what happens if the link has expired.

## Example code

```text
Use case: Reset a lost password
User: Customer
Goal: Log in again
1. Customer taps Forgot password.
2. Customer opens the reset link in the email.
3. Customer sets a new password.
If the link has expired: the app sends a new one.
```

Who, the goal, the steps, and what happens when one step fails.

## Why it matters

It makes a team agree on the whole path, failures included, before anyone builds. Missed failure paths are where many bugs come from.

## Common mistake

Writing only the path where everything goes right. The steps for what goes wrong are often where the real work is.

## Three principles

- **User and goal.** Who wants what, in one line.
- **Steps in order.** Each step the user and system take.
- **Plan the failures.** Say what happens when a step fails.

## Related terms

- [User Story](https://learn.benibix.com/term/business/user-story)
- [Product Requirements Document (PRD)](https://learn.benibix.com/term/business/product-requirements-document)
- [Unified Modeling Language (UML)](https://learn.benibix.com/term/development/uml)
- [User Scenario](https://learn.benibix.com/term/design/user-scenario)
- [Happy Path](https://learn.benibix.com/term/design/happy-path)

## Told apart from

- [Use Case vs User Story](https://learn.benibix.com/compare/use-case-vs-user-story): People think a use case is just a long user story, and it is not. A user story is one short line about what a user wants and why. The details come later, in talk. A use case writes out each step to the goal, plus what happens when a step fails.

## Taught in

- [Product Requirements Document](https://learn.benibix.com/learn/business-product-management/product-requirements-document): Product Management, 2/13

![A customer on the left, then three steps in a row: tap Forgot password, open the reset link, set a new password, ending at the goal, logged in again, in the accent colour. A dashed arrow drops from the second step, marked if it fails, to a dashed box that says link expired, send a new one, and loops back into the third step.](https://learn.benibix.com/diagrams/biz-use-case.svg)

---

Source: https://learn.benibix.com/term/business/use-case
Author: Behnia Zarei (a developer in Vienna, Austria, who builds and teaches data, AI and business intelligence at BENIBIX)
Publisher: BENIBIX Learn (https://learn.benibix.com/)
Last updated: 2026-11-19
Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Quote freely with attribution.
