User stories help us make sure that the products we're creating are aligned with the needs of a user. They can act a guidelines for building a product and as a checkpoint for making sure we're in sync with what users are looking for.
A user profile might have multiple user stories that are inspired by different tasks, decisions, and responsibilities that a user has. Creating multiple stories for a single profile can outline different directions and potential priorities for a project.
Breaking Down the User Profile
Before writing the story, it can help to break down the user's "profile" into their daily routine as made up by tasks, decisions, and information they need.
For this example user profile of a Region Fire Chief:
ROLE: Regional Fire Marshall
BACKGROUND: The Fire Marshall wants to get a better understanding of callouts and what issues are requiring the services of the region's fire support. There might be an opportunity to reallocate resources depending on what is learned about utilization and performance.
We can identify a list of tasks for this example user:
- Report on station performance against targets
- Identify areas of the city needing more support or resources
- Analyze the breakdown of what the service is used for
- Work with station managers on staffing and rosters
And decisions:
- Purchase equipment or hire staff/volunteers
- Reallocate resources between fire stations
- Decide on areas to increase training and public awareness campaigns
- Authorize changes to staffing and shift patterns
User Story Building Blocks
Breaking down a user story into role, actions/decisions, insights, and interactions
- The User Role: This is about who they are in a professional context. It covers their industry, what they are specifically concerned about, and who they have to report to.
- Actions and Decisions: What is the user actually trying to do? They might be looking to manage a budget, make hiring choices, or analyze operational costs.
- Actionable Insights: This focuses on what you can help them see that they might have missed—like specific trends, data outliers, or significant changes over time.
- Process and Interaction: This considers the best format for the user. Depending on their role, they might prefer a dashboard, a summary email, or a presentation deck.
Sentence Template
A common way to structure these elements into a single sentence is by using a format like this:
As a [Role], I need to [Actions and Decisions], so I can discover [Actionable Insight] by analyzing [Process/Interaction].
Summarizing Goals Back to the Client
User stories are also useful for confirming you’re on the right page with a client. This is a potential framework to explain the logic of your work back to your client:
- Because... (This is what you want to achieve)
- I’ve Done... (This is the feature or data I've prepared)
- This Will Help You Discover... (The specific info needed for decisions)
- Allowing Your... (The final action or decision you need to make)