User Story Statements

by Mar 22, 2023

As a User I want to push a button So that it is pushed”

I cringe at these kind of user stories. This one is over the top, but I see user stories often looking like this.

This is the template:
As a [type of user/persona], I want [an action] so that [a benefit/a value]

So, a User is not specific enough. Is it the System Administrator or the receptionist? This is an enormous difference in knowledge of the user doing the action.

Push a button is just one implementation to perform an action. Don’t describe the implementation, but the action you want. Like ‘Delete a Contact’ or ‘Send Survey to a Contact’.

The last part of the User Stories is usually the most interesting part, but often neglected. It tells the “Why”. The benefit or value for the company, customer, or user.

Don’t neglect this part and try to write the real reason who is benefiting from this user story.

Subscribe to
The Daily Friction

A daily newsletter on automation and eliminating friction

Related Content

I can’t read it anymore!

I can't read it anymore! You know those old guys with MASSIVE text on their phone or laptop. I have joined the club. I am 47 now and I started to pinch my eyes more and more. Today I increased my font size on my phone and laptop. I increased my text-size to 110% and...

read more

The Scrum ticket system

The Scrum ticket system You're churning out tickets, classified as 'features', that strongly resemble clean-up tasks. Are all team members solely focused on their own individual ticket? This surely isn't the Agile methodology that was initially pitched to you....

read more

5 reasons NOT to automate.

5 reasons NOT to automate. This might sound odd coming from me, a staunch advocate of automation. However, beware! If you're handling a process for the first, second or third time, don't rush to automate it immediately. Patience is key. Why? 1️⃣ Automation works best...

read more
Share This