 just all of the different ways that you can prototype and how you might test them. So one of the things we talked about, and it sounds like some of you all are doing, are paper prototypes, things that are on physical objects. So it requires those paper physical objects. And you're having the participant review and verbalize their anticipated interactions. So again, remembering that usability testing is task-based. So you're going to, you know, say from here, what would you do next and see where they would click or go? And it's up to the facilitator to sort of advance the prototype. So you're kind of like shuffling through your screens and things to kind of put the next one in front. And obviously, because of that, it's much better suited for in-person and moderated usability testing. Then there is now you're moving into the digital space, but just static. So pretty similar. Actually, you just have like the screens or the things, the different pages or versions that you want to test. Does it require some form of a device to have those images like displayed? And it has all those digital images of the solution. But still requires you as a facilitator to advance based on where the participant is like verbalizing and saying that they would interact with your solution. And again, better suited for moderated. Then you're kind of stepping it up. And now you have a clickable digital prototype. And a lot of the tools that we shared with you last week help you get to this more clickable version. So again, it's images on a device, but the difference is they're linked. So you can have hotspots. If someone decided to click here, it would take them to this other page. If they click here, it'll take them to a different page. So it's like a linked a bunch of images, but they're all linked together through hotspots. And so that's exactly what happens. The participant is responding to the task. They would click on a hotspot area. The prototype itself advances to the next page. Still better suited for moderated because you know, kind of linked things don't work. You got to get them back to an initial starting spot. So that's clickable digital prototypes. And functional prototype. So this is now stepping it up once more. This is not just images, but you're actually having like HTML webpages, partially developed solutions. And this, and this is much more robust, like to be tested, right? So participants reviewing, interacting with the prototype, the prototype advances based on the interactions. It works really well for unmoderated because everything kind of is hooked up, how it's supposed to be hooked up. And I really want to drive this point home best for accessibility. So if you are, if you think about it, right, when you have paper prototypes or static images or linked images, even their images. So if someone has low vision, maybe they can't even be part of your testing because they can't see the image. But with HTML, you can set it up so that a screen reader can read through the elements on the page. And they can actually go through and do those tasks with you. And it's the same, like on an image, you can't type into a box. So for someone who's used to using their keyboard or whatever, you can't do that with an image. So functional prototype, if possible, is kind of the place you want to get to at some point in your process so that you can test it. So on the right, I just have like quote unquote throwaway coded prototypes. And there's tons of frameworks out there so that you can quickly spin up something that's functional so that you can use it. And I say throwaway because it's really just for the purposes of testing. And that may not be what your, you know, organization ends up using to build the solution, but is necessary for doing like functional prototypes. Last one is live prototypes. So this is a fully developed solution. And again, you may get to this, I think maybe one point to say here is that each one that I'm showing you is kind of leveling up the level of prototype and you can decide at any stage in that where you want to go. Do you want to go straight from, you know, paper prototype sketching to a linked one, to a fully functional one, to a live one, it's really up to you and based on where you are in your process and what you want to test. So this is maybe one of the final stages. And also to say that you should test multiple times. I do a few rounds of usability testing on different fidelities of prototypes. So maybe one of the last ones you do is on your live version. So you've done some testing, you're feeling good about it, you actually develop it. And yeah, so then all the steps are the same. The participant is able to review, interact with a prototype, prototype advances, obviously really good for accessibility and works well for unmoderated because you don't have to worry about them kind of getting caught up. And on the right here is an example, I think of a WordPress page. So there's tons like if you're using a content management system, and that's what you're testing. It's possible to create test pages in your existing environment and kind of spin it up that way and have it password protected so that not everyone in the public can see it, but you can use it for usability testing. So when you're doing testing, when and creating prototypes really, these are some of the questions to think about. So what are you testing? Are you thinking about content, navigation, layout functionality? Those mean different things. So if you're doing functionality, it might be tough to test it on paper prototypes, but you can get there. Who would you like to test with? All these things mean different versions of prototypes. So like mobile first, for example, then you would have to go like a mobile testing route and having different devices available and seeing how people interact with those devices. So it's really dependent on what you're testing, who you're testing with, and then limitations that you have. Like, maybe you don't have capacity to get up to a live prototype right now, and you want to just quickly get something out there to be tested with that can be done on a paper prototype. Go with that and put it out there and do some sessions with your paper prototypes. So it really is dependent on your goals, where you are, limitations, who and what you're testing.