User stories
User stories communicate information about users and their needs in more specific ways than high-level statements of user needs.
As user researchers, we need to be able to communicate information about users that is easy to understand. Doing so will enable everyone on the team to work towards building a solution that meets user needs.
User stories
A user need is a broad, high level description of the task the user needs to complete, while user stories help break this down into potential actions and solutions that the team can work on.
As we explained in step 1.4, user stories often describe specific features or content the team will need to create for the service to meet user needs. They include additional information, such as acceptance criteria, level of complexity, and dependencies. This helps teams organise and prioritise work so that they can focus on delivering tangible value for the user.
As you work with your team to design and build the service, you will help develop user stories. These help focus the team during structured, time-boxed periods of work, which are called sprints in agile ways of working.
You may also come across the term epic in agile, which means a big set of user stories.
Epics are written as broad, high-level statements that are very similar to statements of user needs – they represent significant chunks of work that are too big to be completed in one sprint. User stories break down the large, complicated epic into smaller pieces of work that are actionable within a sprint.
Alongside helping teams focus on the users and work collaboratively, user stories are a way of thinking critically and creatively about the problem the team needs to solve. Developing stories can be a way of discussing and agreeing on ideas before the team commits time and energy to building a specific solution.
As stories are completed, the momentum can boost team morale – after all, it can be a great feeling ticking successfully completed tasks off your to-do list!
User stories and personas
User personas can be inserted into user stories to help guide design decisions. As we learned in the previous step, user personas represent groups of users with shared characteristics. They are not real users, but can be used as stand-ins for real users when we write user stories.
Let’s explore this using two of the personas we introduced in step 1.8, Ravi and Angela. When we write user stories, we use this format:
As a [user], I need to [task] so that [reason this matters to the user]
As a driver, I need to ensure my vehicle is compliant with current regulations, so that I avoid fines and can use my car without worry.
Ravi
As a confident digital user with limited English, I need to understand how to pay my vehicle tax online, so that I can complete the process independently without needing help from others
- the service uses plain English and avoids jargon
- key steps are supported by visual cues
- a translation option is available for commonly spoken languages in the UK
Angela
As a person who only uses a smartphone, I need to renew my vehicle tax using my phone so that I can do it easily without the need to speak to anyone
Acceptance criteria:
- the service works smoothly on smartphone devices
- no phone calls or in-person contact is required
- confirmation is sent by email or text message
In these examples, we input information from the persona into the user story. This allows the team to test ideas – if they can come up with potential solutions that meets the needs of Ravi or Angela, it means that these solutions will also work for the users that these personas represent.
User Research in Government: Developing Further
User Research in Government: Developing Further
Register to receive updates
-
Create an account to receive our newsletter, course recommendations and promotions.
Register for free







