---
title: "User stories"
source: 18F Guides
source_url: https://github.com/18F/guides
licence: CC0-1.0
domain: engineering
subdomain: 18f-guides
date_added: 2026-04-25
---

## How to do it{#how-user-stories}
1. Start by defining the project’s [epics](https://tech.gsa.gov/guides/glossary/#epic){.usa-link .usa-link--external}—typically the larger, high-level “themes” or bodies of work that make up the initiative.
1. Break down each epic into pieces of work that can be independently estimated, developed, and tested. These will become your user stories.
1. For each piece of work you identified, write a story from the user’s perspective of who they are, what they want to do, and why. User stories typically follow this template:
    <p>
      As a < type of user >, I want < some goal > so that  < some outcome >.
    </p>
    <p>
      Note: Only make the type of user as specific as you need to. If the piece of work is needed by all your users, it’s ok to say “as a system user.” That way when it is specific (“as a first-time applicant”) it’s clear that this is a group with particular needs.
    </p>
1. Consider possible harms to the user, the system, or external to the system by adding a second part of the sentence:
    <p>
      …while avoiding < potential negative impacts > to  < the user, the system, or external to the system >.
    </p>
1. User stories can be the basis for tickets—a tool to manage and track work for the solution you’re building. These tickets should include the story, a brief description, and a list of [acceptance criteria]({{ "/agile/agile-lexicon/#how-we-talk-about-the-work" | url}}){.usa-link .usa-link--external}.


<section class="method--section method--section--additional-resources" markdown="1">

## Additional resources{#add-personas}

- [Agile — 18F Guides]({{ "/agile/" | url}}){.usa-link .usa-link--external}
- [Agile software development — 18F De-risking Guide]({{ '/derisking-government-tech/principles/#principle-1-modern-software-development-practices' | url}}){.usa-link .usa-link--external}
- [Writing Effective User Stories — Tech at GSA](https://tech.gsa.gov/guides/effective_user_stories/){.usa-link .usa-link--external}
- [User Story Examples — Tech at GSA](https://tech.gsa.gov/guides/user_story_example/){.usa-link .usa-link--external}
- [Government Product Managers Play a Key Role in UX — Digital.gov](https://digital.gov/2015/11/27/government-product-managers-play-a-key-role-in-ux/){.usa-link .usa-link--external}

</section>

<section class="method--section method--section--government-considerations" markdown="1" >

## Government considerations{#con-personas}

No PRA implications. No information is collected from members of the public.
</section>
