Clickable Prototype and Usability Script – Team Badger

Prototype: 

https://www.figma.com/proto/6LYFqgdyyZtbI1UEJaC69h/unrot?node-id=146-8&t=zgcZUW4lESZE6Q3Y-1&starting-point-node-id=146%3A8

Introduction

Introducing UNROT: an app that helps you improve and decrease your AI usage, targeted toward Gen-Z-savvy students, that is more experience than app. It tracks your AI usage and reflects it back to you with a brain character that you can personalize yourself.

In this usability test, we aim to test the overall flow of the app: for example, how intuitive the “home” button feels or the “stats” button. We also want to test the flow of the onboarding and how intuitive it is. Moreover, we are interested in improving the quality and kind of the statistics/feedback that the character gives. 

Script

Hi, ___________. My name is ___________, and I’m going to be walking you through this session today.

Before we begin, I have some information for you, and I’m going to read it to make sure that I cover everything.

We’re asking people to try using our web extension, UNROT, an app designed to help you improve and decrease your AI usage. It tracks your AI usage and reflects it back to you with a brain character that you can personalize yourself. The end result is meant to be embedded in your native AI workflow, i.e. as a web extension on ChatGPT or Claude. Right now, we have built a prototype (and not the full working thing), which means that there are some technical limitations that I will elaborate on later on.

For now, I just want to let you know that we are especially interested in testing the overall flow of the app – whether each button’s destination feels intuitive – and the overall “delightfulness” of the app. 

The first thing I want to make clear right away is that we’re testing the app, not you. You can’t do anything wrong here; if it’s wrong, it’s our responsibility. In fact, we are interested in the kinds of “mistakes” which would make the app unintuitive. 

As you use the extension, I’m going to ask you as much as possible to try to think out loud: to say what you’re looking at, what you’re trying to do, and what you’re thinking. 

Also, please don’t worry that you’re going to hurt our feelings. We’re doing this to improve the app, so we need to hear your honest reactions.

If you have any questions as we go along, just ask them. I may not be able to answer them right away, since we’re interested in how people do when they don’t have someone sitting next to them to help. But if you still have any questions when we’re done I’ll try to answer them then. And if you need to take a break at any point, just let me know.

With your permission, we’re going to record what happens on the screen and our conversation. The recording will only be used to help us figure out how to improve the app, and it won’t be seen by anyone except the people working on this project.

Do you have any questions so far? 

Survey questions

Before we look at the app, I’d like to ask you just a few quick questions.

  1. How often do you use AI?
  2. What do you use AI for? 
  3. What platforms do you use?
  4. Are you interested in improving your AI usage?

Test

Okay, great. We’re done with the questions, and we can start looking at things.

Pull up the prototype on a full screen.
Start the screen recording (Command + Shift + 5 will open up the toolbar)

We’re going to test 2 scenarios. The first is the onboarding flow, and the second is the “normal” work flow.

First, let’s begin with the onboarding flow. You are a brand new user, and you have installed the extension, and you have just opened Chat after installing the extension. Please try to use Chat for 1 session: meaning, finish the onboarding flow from start to finish.

As a reminder, this is a Figma prototype, which means that you can’t enter any text. If you see a text box, you may click on it, and it will pre-populate with a pre-written text; this is meant to simulate you writing the text. Otherwise, please interact with it as if it were a normal website. There may be some limitations that I’ll explain verbally when it occurs.

As a reminder, please try to think out loud as much as possible – try to be as honest as possible.

Give them the computer to begin with the onboarding flow. Let them click around. 
Once they reach the stage where Barry is saying stuff, and they can’t click on stuff anymore, tell them that here, you would proceed with interacting with ChatGPT as normal: the different Barries are meant to be there to illustrate Barry’s capabilities.

Now, let’s proceed with the second scenario. You are a returning user, and you have just opened Chat.

Give them the computer to begin the second flow. 
Once they reach the stage where Barry is saying stuff, and they can’t click on stuff anymore, tell them that here, you would proceed with interacting with ChatGPT as normal: the different Barries are meant to be there to illustrate Barry’s capabilities.

Final questions

Okay, now I want to ask you some questions about the overall product.

  1. How intuitive did the flows feel?
  2. Was there anything you were particularly confused about?
  3. Do you have any suggestions for how we could improve our product?
  4. How did you feel about the character itself: Barry?

Conclusion

Thanks, that was very helpful. 

Do you have any questions for me, now that we’re done?

Stop the screen recorder and save the file.
Thank them.

Avatar

About the author

Varsha is a senior at Stanford studying Computer Science with a focus on Human-Computer Interaction and coterming in Artificial Intelligence. She is eager to deepen her understanding of product management—both through foundational concepts and real-world applications.

Comments

Comments are closed.