From the course: UX DesignOps: Measuring Success

Helping stakeholders understand measurements

From the course: UX DesignOps: Measuring Success

Helping stakeholders understand measurements

- [Instructor] There are business acronyms that are often thrown around like ROI and KPIs, but in user experience, we often have to decide what the most important measurements will be that we can give our stakeholders about our users. We need to help them understand the pain points and why we make the design choices that we did. What you are building matters here, and when looking at what to measure, a website, for instance, might be more interested in retention of visitors or conversion rates if you're selling something. An application might be more interested in the time it takes to do a task. As usual, we have different levels of stakeholders of our measurements that are meaningful to them and how the UX team and DesignOps can help deliver. Starting with the design team's closest allies, our developers start to show what the measurements we get out of doing usability testing and how it shows them things like how a user actually uses the product or the application, why choosing a design pattern for specific users are necessary, why five to eight participants is usually enough to get those results, why doing testing matters to them. It also opens up communication for how they can help the team set up those metrics. We can help the product managers and the business analysts with epics and features by adding in what measurements of success are for the user. What problem are you trying to solve for the user? How will you get what you need? Will you do usability testing? Will you use feedback tools, screen recording tools, other analytics? What measurement is right for the problem we are trying to solve? To understand how to measure success for the major stakeholders, you have to understand what their KPIs are and how to turn those into UX outcomes. Focus on what the measurement for the users mean to their bottom line. Turn those business requirements into measurements of success for the user in epics and features. Help them understand the vision and the scope and how to make sure everyone is on board and understands what those things are. In the next chapter, we'll look at different types of frameworks to help you measure.

Contents