UX testing product demo

About this film

See the UX testing workflow in the Sunzu web app. The recording shows how a team can review a design and explore usability findings, helping identify friction while changes are still quick to make.

Read the ux testing benchmark and its scope or explore the research methodology.

Transcript

With usability testing, you can test different design flows. As before, we choose an audience. If you have custom audiences, they'll be available in your workspaces and you can select them to participate in the test. I can test a single page or journey or I can compare different journeys against one another. That's if I have two different ways of doing the same thing, I might want to see which version of the user interface is best at performing the action for the user. Let's start off by testing a single design today. We support Figma, Protopi and HTML prototypes as well as prototypes available via URL. I put the Figma link in here and the password in here. Sunzu is now exploring the prototype, creating a graph of all the interactions and user journeys. Then Sunzu is going to go and design its test and that means going and collecting some characters to participate in the test who will then navigate the prototype, find all the issues, bugs and frictions and then Sunzu will report back. Let's get the test running. I need to give it a clear brief. Let's go. And once again you can see the characters participating in the test here. Because Sunzu is a humanistic platform, we put our characters at the center of every study. They have lives, ideas, interests, or values and attitudes and they bring all of this to the usability test that we're currently running. It will determine how successfully they navigate around, how quickly and easily they can figure out what they need to do. And ultimately, this will construct the usability test results. Let's now look at a report. The key headlines are captured, the user journey pictured, and the number of participants that successfully completed the task is documented. And that's those that completed it easily, with hesitation, or failed to complete the user journey at all. Headlines on what's working, and recommendations as to what to do next. A key breakdown by individual, and then a deeper dive into what worked and what didn't. Any ad hoc questions I asked will be answered here. Screen -by -screen recommendations as to what to do next. Key themes that kept coming up in the interviews. And a breakdown of how each individual did. These are all of our characters who actually physically navigated the user interface. The number of steps it took them, that's forwards and backwards journeys captured. Some quick quotes from those who participated. And as before, the transcript of every interview. You can see that Freddie, once again, was not too communicative. And Rachel more extensively explores the prototype. And this is what we mean when we say it's not an LLM averaged out persona. Each character has its own individual abilities, its own digital literacy and its own competencies. And that's reflected in the number of friction points and also the number of steps each character took when navigating the prototype. And this gives you clear user feedback for your audience. So we understand user needs. We've developed concepts and tested features so we know what we want to build. We've run our usability test so we can now make sure we're building the right thing in the right way And now we want to communicate that concept to market. So let's do some ad testing