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

Improving Optimization?

Improving Optimization? The traditional steps of Optimization: 1. Eliminate 2. Automate or 3. Delegate What if we added a missing element? Simplify. Before automating a convoluted workflow or delegating a tangled task, strip away the unnecessary. Make processes leaner...

read more

Unit tests for Dataverse plugins?

Unit tests for Dataverse plugins? I must admit, I almost never write unit tests for Dataverse plugins. Plugins are often quite simple, testing them in isolation is not particularly useful. Often you only test a couple of if-statements. Unit tests don't bring a lot of...

read more

New Dynamics 365 browser extension

New Dynamics 365 browser extension I'm trying out the new -Power Roles- extension and it looks very promising. You browse to a Dynamics 365 (or Power Apps) app and then you press -record-. It will then monitor all the action you do in the app and propose which...

read more