by Christian Bisson, PMP, PSPO, PSM
In agile, users are everything. So it only makes sense that users—anyone who will use or interact with your product—should be a team’s main focus. In order for the product to be viable, whatever is produced must bring them value.
But it’s perhaps too easy to forget users when you build your backlog. We often jump too quickly to features, assuming “the users will use this.” But what if we took a step back? Consider taking the following steps:
First, for whom is this product intended? Identifying a target audience will help you determine who you’re building for.
For example, if you expect users who aren’t tech-savvy, then you need to be mindful of how complex the interface or even the wording are throughout.
It’s important to describe these users. One common practice is to create “personas,” which are fictional characters that represent the users. These will help you better understand your audience.
Now that we know our audience, what are they trying to achieve? Instead of jumping from personas to features, stop and think about their goals.
Are they trying to purchase something online? Are they trying to fetch information? Are they trying to plan a trip? The answers to these questions will shape your direction.
We know who is trying to achieve what. The next key step is to define “how” the users are going to achieve their goals.
Let’s assume the user wants to purchase a toy. That user will most likely need to:
- Search to find toys
- Be able to view the toys
- Add a toy to a cart
- Make the official purchase
Let’s keep it simple. We can extrapolate that this user might be interested in items related to this item, or many other scenarios, but for now, the above is our user’s steps.
Once this is clearly defined, it is much simpler for:
- Our product owner to create user stories clearly stating what the user needs and for what: “As a customer, I want to search for products by categories so I can more easily find what I am looking for.”
- Our development team to understand why this (these) features matter, and how we’ll architect them, because we understand why we are doing it.
I’ve seen too many teams skip these important steps. Often, people are so quick to execute what is instructed by managers, or by assumptions from the team, that they forget to think about who they are building the product for. The user, of course, will ultimately decide the product’s success. That’s why it’s so important that our product brings value to users.
What do you do to focus on users? How do you verify if you are bringing value to them? Share!