From the course: UX DesignOps: Measuring Success
Join today to access over 25,300 courses taught by industry experts.
Outcomes to product requirements
From the course: UX DesignOps: Measuring Success
Outcomes to product requirements
- [Instructor] We want outcomes, not outputs. It's something that makes Agile so frustrating for us. What we have to concentrate on is what we know. Understanding the context of use, specify the user requirements, design the solution, and evaluate against the requirements we've established. An outcome for UX is simply putting the user first. Think about what you want to accomplish but frame it around your target audience and what they need to accomplish. The tasks or workflow to accomplish what they need overall or specific tasks. A requirement when framed by product often includes the solution and not framed is what the problem is for the user. At work, I often sound like a broken record as I'm always saying what problem are we trained to solve for our clinicians? When an epic or feature is framed like this, it allows for user experience to explore and figure out how it can be solved. User experience works out the how…
Download courses and learn on the go
Watch courses on your mobile device without an internet connection. Download courses using your iOS or Android LinkedIn Learning app.