User Story Generator

Edit an example, or write your own.

Just want a blank template?

As a [role], I want to [goal], so that [benefit].

Acceptance criteria:
- Given [context], when [action], then [outcome].
- Given [context], when [action], then [outcome].

Start from an example

Your stories (1)

Acceptance criteria (Given / When / Then)
CRITERION 1
CRITERION 2
CRITERION 3
Must have3 pts

As a returning customer, I want to pay with a saved card so that I can check out in under a minute.

ACCEPTANCE CRITERIA

  • Given I am signed in and have a saved card, when I reach the payment step, then my saved card is selected by default
  • Given my saved card is selected, when I confirm the order, then I see an order confirmation with a reference number
  • Given my card is declined, when I confirm the order, then I see a plain-language error and can pick another payment method

INVEST self-check

Nothing flagged. A quick read is still worth it.

  • IIndependentLOOKS OKCould a team build and ship this without waiting on another story?
  • NNegotiableLOOKS OKDoes it say what the user needs, leaving how to build it open?
  • VValuableLOOKS OKWould the user, or the business, notice if it was missing?
  • EEstimableLOOKS OKDoes the team know enough to size it?
  • SSmallLOOKS OKCan it be built within a single sprint?
  • TTestableLOOKS OKCould someone check, yes or no, that it works?

Export all your story

The CSV has Summary, Description, Acceptance Criteria, Priority and Story Points columns, ready for a Jira or Trello import.

What is a user story

One need, in one sentence.

A user story is a short description of something a person needs from a product, written from their side. It's a conversation starter for the team, not a spec.

As a

The user

A real type of person, not "the system".

I want to

The goal

What they need to do, not how to build it.

So that

The benefit

Why it matters. The part most people skip.

Not sure who the "user" is yet? Start with the User Persona Builder.

Questions

FAQ

What is a good user story template?

The standard one is: "As a [type of user], I want to [do something] so that [I get this benefit]." The "so that" is the part people skip, and it's the most useful bit, because it tells the team why the story matters and lets them suggest a better way to get there. Add a priority, an estimate and a few acceptance criteria and you have a story a team can pick up. This tool builds exactly that.

How do I write acceptance criteria?

Use Given / When / Then. Given is the starting situation, When is what the user does, Then is what they should see. Write each one so a tester can answer yes or no. "The page loads quickly" can't be checked; "the order confirmation appears within 3 seconds" can. Most stories need three to five, and if you're past six it's usually a sign the story should be split.

What's the difference between a user story and a use case?

A user story is a short note about one need, written from the user's side, and it's deliberately light so the team talks it through. A use case is a longer, more formal document that spells out actors, preconditions, the main flow and the alternative flows step by step. Agile teams mostly use stories; use cases show up more in regulated or contract-heavy work.

Learning UX yourself

Beginner UX (AI) Design starts 14 October 2026.

Tools help you do the work. They don't teach you the judgement behind it. Beginner UX (AI) Design is taught live online by working UX professionals, built for career-changers with no design background.

Book a callSee the course

Working in a team rather than learning on your own? We run in-house UX training built around your own product, and we can talk it through on the same call.