Q&A: What’s the best way to focus teams on outcomes not outputs?
I’m asked questions about product management from time to time. Here’s one I’ve answered recently:
What’s the best way to help agile teams move away from feature delivery to focus on outcomes not outputs?
From my experience, the elephant in the room seems to often be we don’t know enough about the problem and we haven’t done enough research. The team is eager to build stuff and are clearly worried about the unknown of the discovery process.
How can we get better at doing research to find opportunities in an agile environment?D
Each week, go (with your team if at all possible) and have open chats with your users about how your product fits into their lives. It would be rare not to come back with at least one insight that changed your perspective.
With permission, record your users using your product in their real-life context (i.e. not in a lab) to see where they make mistakes, get frustrated or simply have to work around your product’s workflow to get what they need done.
Take those human responses to heart – both you and your team.
Decide as a team how you’re going to take some of that stress and hassle out of your users’ lives.
Figure out what you’re going to try first, and put it on your product backlog. Check whether it worked.
Now you’re working towards outcomes.
Get articles when they’re published
My articles get published irregularly (erratically, some might say). Never miss an article again by getting them delivered direct to your inbox as soon as they go live.