You’ll need to recruit testers that meet your persona from either a panel or on your own. This test is best done with a clickable prototype, because you are certainly going to learn and want to make changes. Unmoderated is NOT helpful for learning Real Life Usability. Thus you can really only learn UI Usability. However, you can’t ask follow up questions and dig deeper while a user is being tested. You can get large volumes of responses while you are working on something else. The major benefit is that it’s quick because it is asynchronous. You set up a test, send it out to people and record their interactions, and often their voices, as they attempt to complete certain tasks. If you don’t have time or budget for 5, then 3 is better than zero. It would be good to speak with 5 testers per persona. You’ll need to recruit testers that meet your persona & schedule a time to do a live session run the tester through a prototype and ask them to complete specific tasks ask Real Life Usability questions, noted above take notes and record the session to share important aspects with stakeholders. This type of test is best done using a prototype because it’s easy to make changes. However, this type of testing is a bigger time commitment. You can follow up and ask questions when a user mentions something and dig deep. The benefit of Moderated testing is that you learn deep insights on how a customer will use a feature design. You can also learn UI Usability with Moderated testing. It can be remote or in person, but you are live with the customer asking them to try a prototype or already built feature and asking them Real Life Usability questions (noted above). ![]() Moderated Testing means testing with a customer in real time. With this basic understanding of the goals of user testing, the next part is how. Customers have to see something visually and try it out to tell you if they would use it. Simply gathering “requirements” in interviews is not good enough. Until you put a prototype of a new feature in front of a customer, there is NO WAY to determine whether it meets the customer’s requirements to actually use it. I can go on and on about the questions that help predict the success of a feature design. What do they view as alternatives to that feature? What do they like about that alternative? What do they hate about that alternative? What will make them switch from that alternative?.How will they use the feature in their daily life? How frequently? In which circumstances?.Some example questions for when testing Real Life Usability are: What a customer says they will do, what a customer says they did and what a customer actually does are three different things. Remember this one thing when testing Real Life Usability: As simple as it sounds, there is a lot that goes into that answer. This test type answers whether a user will actually use the feature in their real life. Can someone go from page 1 to page 2 to page 3 to page 4 without getting confused? ![]() When you are testing a new feature design, you want to learn 2 things: I’ll explain user testing using this grid: It is impossible for a designer or a product manager to sit in a room and guess how a customer wants to use a feature/product. Real needle moving stats and it is wide spread. Meaning, re-coding an existing feature to better reflect customer requirements or to make it more usable.
0 Comments
Leave a Reply. |