---
title: "User scenarios"
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-scenario}

1. Determine a few [personas]({{ "/methods/decide/personas/" | url }}) or user groups to focus on. Consider what scenario(s) might be the most critical for that user, including scenarios in which users face limited [accessibility]({{ "/accessibility/" | url }}).
1. For each user, list out their goals, motivations, and the context/environment in which they interact with your product, service, or website.
1. Put the details you came up with in step 2 into a story format that includes the following information:
    * who they are (persona or user group)
    * why they are using your site (motivations)
    * where they are (context)
    * what they need to do (their goal)
    * how they go about accomplishing the goal (tasks)

    Keep in mind, the more realistic details you add, the richer and more useful your story becomes for helping to understand your user’s behaviors.

1. Share the user scenarios that you’ve written with the user group (and other relevant team members) for validation, feedback, and refinement.
1. Examine your product, service, or website in light of these user scenarios and identify opportunities to make adjustments that would improve users’ experiences.


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

## Government considerations{#con-user-scenario}

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