Remote User Testing With Figma & Maze | Max Brinckmann | Skillshare

Playback Speed

  • 0.5x
  • 1x (Normal)
  • 1.25x
  • 1.5x
  • 2x

Remote User Testing With Figma & Maze

teacher avatar Max Brinckmann, Researcher and Designer

Watch this class and thousands more

Get unlimited access to every class
Taught by industry leaders & working professionals
Topics include illustration, design, photography, and more

Watch this class and thousands more

Get unlimited access to every class
Taught by industry leaders & working professionals
Topics include illustration, design, photography, and more

Lessons in This Class

9 Lessons (55m)
    • 1. Intro

    • 2. UX Snack

    • 3. How Everything Works Together

    • 4. Tutorial: Figma

    • 5. Tutorial: Maze

    • 6. The Test Click Dummy

    • 7. Evaluate

    • 8. Feedback

    • 9. Your Class Project

  • --
  • Beginner level
  • Intermediate level
  • Advanced level
  • All levels
  • Beg/Int level
  • Int/Adv level

Community Generated

The level is determined by a majority opinion of students who have reviewed this class. The teacher's recommendation is shown until at least 5 student responses are collected.





About This Class

Working from home, which can be both - burdening and rewarding, has changed how we do things that used to be absolute no-brainers: Where do you hold your meetings? Of course together in a room! Where do you do your user testing sessions? In the office and in-person, of course! All of that needed to change needed to be adapted.

Let me in this course give you an in-depth look at how to conduct fully remote user testing sessions for your interactive prototypes, both qualitative and quantitative and how I did A/B tests fully remote, with the usage of Maze and Figma.

In this course you will learn:

  • How the tools play together and what their synergies are
  • How to use Maze for qualitative and quantitative research
  • How to prepare your Figma prototype
  • How to set up your Maze test case
  • How to evaluate the insights in Maze

I have spent many hours in the preparation and production of this course, and I really hope that you enjoy it and are able to make the most of it for your career and professional life!

About Max: I am a Senior UX Designer and User Researcher and I am a huge fan of believing in never stopping to learn. I want to share my knowledge with you and give back to the community that brought me to where I am now.

Music by Chillhop:
Mo Anando. - In Bloom:

Meet Your Teacher

Teacher Profile Image

Max Brinckmann

Researcher and Designer


Hello, my name is Max and I'm a Senior User Researcher and Digital Designer with more than ten years of professional experience. I love to write and to talk about UX related topics. Besides that, I am occasionally recording music.

Throughout my career, I was and still am privileged to work for many different clients from different industries like automotive, IT, food, healthcare, or life science. Having worked both for agencies and in-house, I am able to share from my broad set of knowledge that is based on successful projects of almost all possible places of action for UX and digital product design.



So far, my online courses have been watched by 30,000 students across all channels. Sharing is caring, and ... See full profile

Class Ratings

Expectations Met?
  • Exceeded!
  • Yes
  • Somewhat
  • Not really
Reviews Archive

In October 2018, we updated our review system to improve the way we collect feedback. Below are the reviews written before that update.

Why Join Skillshare?

Take award-winning Skillshare Original Classes

Each class has short lessons, hands-on projects

Your membership supports Skillshare teachers

Learn From Anywhere

Take classes on the go with the Skillshare app. Stream or download to watch on the plane, the subway, or wherever you learn best.


1. Intro: Runs smoothly online user testing sessions with Figma and male. Hello, my name is Max and I am a senior user researcher and user experience designer. With ten years of professional experience, worked in various industries and for a multitude of clients and the different user groups throughout this time. And I want to welcome you to this class on running successful online user testing sessions using Figma and maize. Not only did the pandemic bring many challenges to our lives, we had to change many of our habits, adapt to new situations, refrained from a lot of things that we like. It also highlighted some of our societies weaknesses. Working from home, which can be both burdening and rewarding, has changed how we do things that used to be absolute no-brainer. Where do you hold your meetings of costs together in a room. Where do you do your user testing sessions? In the office. And that person, of course, all of that needed to change, needed to be adapted. Many great initiatives and tools arose and accelerated the movement towards remote work and collaboration. Of course, there are many products and companies that put a great deal of attention on remote work even before the pandemic, because of many possible reasons, for example, economics or because they wanted to offer their employees most freedom possible. And in fact, the tool maze that I want to show you in this course has been on my list already before 2020. And it just proved to be the perfect fit for remote work and remote user testing. With maze, you can transform your Figma, Sketch, Marvel, or other prototypes into a user test scenario with only very small effort, you can specify a user journey that you want to monitor and at questions to it along the way. So it's also really valuable for quantitative tests and which you would want, send it out to a huge group of test users. I think maize is a great addition to every UX person to a portfolio. So you should definitely check it out and check out this course if you ever are going to do a UI test in the future. And no, I'm not affiliated by maze. So let me in this course gives you an in-depth look on how to conduct fully remote user testing sessions for your interactive prototypes, both qualitative and quantitative. And how I did A B tests fully remote with the usage of Mason Fatma. A. Ready. And let's go. 2. UX Snack: Is it might already know, I'm publishing short UX instructional ads on Instagram that highlight different topics, situations, tools, or anything else that matches what the user experience topic. And calling these posts UX, snag, extremely easy, digestible, and can be consumed like small bite of knowledge. And thereby no means main, meant to be exhaustive, but rather she's awareness about what I want to talk about. And if somebody cares, then that's absolutely great because their main objective is to make myself comfortable with potential upcoming class topics. So that's why I enjoy going through these UAC snacks with you at the beginning of my classes to get us all warmed up and excited and provide you with a rough idea of what's to come. So let's take a look. Sorry. All right, so this should have been called remote user tests with Figma and maize, but somehow the width GOT lost during export. I apologize of that. Well, follow for more exactly, why don't you follow me on Instagram? It's only extremely, very high quality content, of course. So we will start off by making sure that to have an interactive prototype in Figma ready to be shared. As we need the prototype, you're out because through the URL, we will connect our prototype with maize. Importing the prototype, which by the way, can also come from Adobe XD. And sketch Marvel is a pretty breeze and literally are just a matter of pasting the public link into the tool. And once we imported the prototype, we have to click through the prototype in order to root for the journey or our test users have to follow in order to accomplish the test case. So for example, if you want to test an app for ordering pizza online, you would record the journey from selecting the pizza to entering your address and billing information, to sending out your order, and maybe even tracking the location of your pizza. These journeys can be divided into and you can even add a survey type questions, which especially makes a lot of sense for large-scale tests, are simply for cases where your users are working on tests on their own without supervision or guidance. And once you're done, you can send out a new link. So not the thickening of the main link to your test candidates. And they will run a maze user tests than their browser. And at the end, you get a super nice evaluation including cursor, click heatmaps, and so on and so forth. And of course, I will show you all of that in this class. All right, so this will roughly be what you're going to do in this course. We will set up the prototype in Figma, but this will not be a full-blown Figma tutorial. I will however, make sure that you understand how to set up your Figma prototypes in order to get it to work with maize. We will then of course, set up the project would then maize and create a nice user test case. And after that, we will go through the evaluation and how many reports are set up. So are you excited? I hope so. Let's move on. 3. How Everything Works Together: Okay, let's start by understanding how the different software pieces are going to play together and the setup. You will need to sign up to Figma as well as maize. But they are offering free accounts for plans and everything I'm going to show you in this class will be doable using the free accounts. So you have freedom to try it out for your cell. And of course, to work on the class project without any money that you have to pay for license fees. So as you can see, the flow that I drew down here is pretty simple. Save straightforward, but I just want to show you how everything is actually going to work together so that you have an idea of what you can get at the end and what do you need and how it works together. So the first puzzle piece is Figma. In Figma, you will create your prototype. You are, you I prototype and make it interactive. Meaning you will connect the different screens so that you can move through the prototype within Figma already. And they should be then an, a final stage so that you're ready to share it with external people or whoever you want to test it with. The next piece is made. And mains works in a way that it imports the prototypes from the external URLs. So you have to provide maze with the URL of your prototype, which will then be converted into a maze link. Within maze, we'll then set up the missions and the users in the user journey and can add different questions. Um, well, they will be then collected at the end and some sort of report that you can use for your evaluation, which leads us to the third stage. And this fellow symbolizes that this will be the platform that you also do your tests on. So you're not using Figma anymore. In this stage, you are only going to use this main link, which includes your Figma prototypes. And also when you notice that you want to change something in Figma afterwards, it can do that in Figma, then hit a button update and your maize prototype or maize, a test case will be updated. So here, the third layer is the evaluation stream. And you can see just, you can see that there's three different points here. Meaning you will get three streams of insights for your documentation, our evaluation. The first one is something that I highly recommend doing whenever possible. And it's a screen recording, of course, when you're just sending out the link to someone and you are not observing them while they play through that. You cannot record the screen. Obviously, you can maybe ask them to do that and send over a screen recording which is not that convenient for them. But something that I did was sending over the link, but then also sets up a video call and record the screen. So have them share their browser so that I can see what they're seeing, what plane through maze. And I was just recording the screen, which gave me and very nice video documentation of the test. And the second stream is the main report, which is very comprehensive, featuring heatmaps, of course, statistics on the survey, survey results. But also they're doing some number magic and calculating usability score and all that stuff. And the third stream is nodes are very classical approach. Someone may be, you maybe appear, would document the process of your test. Which is of course, also only possible if you're guiding your users during that test. So if you're not doing that and during duty, you're maybe going the qualitative way. The first and the third option would drop away, but you would still end up with a maze results, Results reports, which are very good. And of course I will show them in a pet. 4. Tutorial: Figma: All right, so let's start with the Figma parts. I'm not going to deeply into the details as this is not a Figma tutorial. If you want to have a Figma tutorial, let me know. I'm happy to create one in the future. Here it is about the connection of the different parts. And we can focus on maze, of course. And I would like to, to start off by showing you how to set up the prototype in Figma, how to connect the screen. So it's just a little tiny bit of a Figma tutorial. And then how to get the link which you need for the maze prototype. All right, so here we have a very, very simple mobile interface. Actually know profs girl to myself here I downloaded it from the Figma community, which is a great place for these kinds of assets. Just changed the image here and the profile section. But right now, it's just three synchronous signals screens. So they're not interactive yet. There's something that we need to do. And then I will just try out if everything is working and then we're good to go. As you can see, this sort of finance app. No, surfing on the entire crypto coin wave. And it's very basic. We have home screen here. Then we have an acid overlay, which kinda looks like it's some sort of cards that you can move around. And we have a profile page. You could do many more pages, of course, depending on what you want to test. This is just Example 4, the mechanic. So let's just go ahead and make it interactive. And I would just say that we could link this module here to the asset page and have it on tap. Move up this overlay on top of this page. So we'll just draw the arrow to that side. And instead of navigate to say, open overlay, page, animation would be moving in. From the bottom to the top. 200 milliseconds is just a number. I like to think it's quite nice for animations of many kinds. And that should be already it. Then we will link the clone icon back to this page here. And on click, it will close overlay, and that's already it for the animation. And then we will link these small account icon to the account page onclick navigate to provide screen. The animation will be smart animate because we some elements that are recurring and I don't want them to kind of move or slide in a weird way. So this should hopefully look quite natural. Same goes for the back arrow. Again, we have onClick smarter and emit the same duration. And that's already a very, very simple. By clicking on this present icon here we can try. The trial to, the prototype is working as expected. We can see it starts with the correct page, was unconscious already. Good. Let's check out by clicking on this one here. And it moves up. Very nice. This moves it down again. Let's check this out soon. Nice animation. Actually we had a fade here on the color. The top bars just state as it is. It can move back as well. So we're done on the making of the part of making the prototype interactive. And now what we need is the link which we get by clicking on the blue Share button. Here. Oh, it's important to say that it's available to anyone with the link. If this is somehow restricted to invited people only and you will copy the link, maze cannot access it. So we need to have a public, publicly available copy the link. I think we should just select the first frame just to make sure it's working. Then share, copy the link. It says link copy to the clipboard, and that's it. We now have the link I can just for fun passage here so you can see how it looks like. It's pretty weird, long link. And we will need exactly this link to import it in maize, which we're going to do in the next chapter. 5. Tutorial: Maze: All right, Now that we're done with Figma path, we can move over to me. And let's just make ourselves familiar with the tools cells are before you start actually important importing the prototyped length, right? So this is the website of maize, And I can, I think I can explain or mega bit more understandable what it's all about by just showing you pages here. So at first, this is about the user testing. It's a nice, very nice, It's a visually very nice tool that actually talks your users through the test. So you have to think of a prototype, think of your Figma prototype. But on this side, you would have a bar that has some instructions regarding the current mission. So for example, in our case, it would be open your assets and try to find a way to open the assets within the interface, something like that. And then the user would have to solve this mission. And only if the user succeeds, what provides some sort of success message and enable the user to continue to the next part of the test. And it's, as I said, visually very, very appealing. It's very easy to understand. They of course, paid a lot of attention to their own usability and user experience. So it makes a lot of sense to use this and even for, for quantitative research. Because with this maze link, you can basically just with the survey link, send it out to, I mean, even hundreds of people if you want. And if you do the instructions, if you provide everything your users need, they can basically do the testing on their own and you will see the results drop them. And that's actually quite a nice idea to do that. I must have also used for the qualitative testing in remote scenarios. And it worked really, really well. Because I could also just have used Figma prototype Link centered over to my test peers. Have them share their screens, record everything, and take notes. Then I would have covered two of the three inside streams I mentioned. But I have to say that these reports are quiet, worth the effort of importing everything here, as I said, are, as you can see here, you've got another, a lot of numbers. And numbers are always a nice thing that they convinced very, very well. And stakeholders love numbers. Everyone know loves numbers. So this usability score, which is questionable, I am not really, really sure how they calculate the usability score, but it kind of makes sense in the context of the entire report. You get a lot of evaluations regarding the mistakes because maize knows where the interactive areas are from, your Figma prototypes and then fuses, don't hit that area. This will be counted as a miss click, which will then also be visualized on the Heatmap. It'll be there also these kind of heatmaps here and on this page. So you can see all the different filter options that you have. These kinds of well, bounce rates, visualizations, while whatever, everything is exportable, everything is really presentable actually. So you can send around reporters well, much like in tight form, which I had another class about. So if you want to check out the reporting topic regarding surveys, can check out this course as well. And yeah, I would say without further ado, just jump into the importing rate. I have to log in for that, for that case. And here I have 1, 3, 1 open slots. As you can see, I'm on the free plan. I used to be on the paid plan. So I had multiple projects here which are now all archived. So this is what happens when you use which from the paid plan to the free plan, but you have more than one project which is included in the free plan, then these projects will move to the archive section. So let's go ahead and create a new project. And you can select, if you want to do a major discovery, our user testing and the discovery goes more into the server direction while the Western user testing goes into the interactive direction. So you can see here it just asks for a project name TO that asks for the prototype Link, which I hopefully still have my clipboard. Let's click on Create, and maize will do its magic. So we just have to wait a few seconds, then we should be able to work with a prototype and add all of our questions. So success, this is looking good. Here on the right-hand side, can see that it's preloaded the prototype as we have it on Figma and it's theoretically attractive already. So what's now happening is that we're in the first mission. You can see you can add different blocks here. Missions are parts of the user journey. Then you can add yes and no questions. Can add an opinion scale. You can add multiple choice question, an open tag question. Can add additional contexts. Screens, which I'm just providing more information. So you can add any kind of graphic here or text. Well, a tree test to show how users navigate to find information, card sorting, even crazy, how many different tests are our question types they implemented here? 5, second test and TEA legal cause, the legal screen, the welcome page, the thank you page are things that are not available in the free plan, probably as well as removing the brand. But we don't need this for our case here. So the first mission is, in our case, navigate to your description would be something like trying to find a way of how to open up your assets over view. All right, and now we have to define the expected path, which would be in this case, simply clicking here on the, on the green module. We'll click here. That's already at for this mission. And we just leave it like that. And we can just confront the question afterwards. So what will happen in the prototype is a user will hopefully manage to succeed and complete this mission. And after that, there will be a success message. And then we can continue as the user. We as the user can continue to the next question, our mission and our case. We want to add a yes and no question. The question would be this is just for you for the demo purpose here. Would you say, let's say, Did you like this experience? You don't need any extra notes. And we can switch between icons for the check mark and the cross or emotions or what's my knees? Let's take with the icons. We don't need any additional image, are nodes in our case. And the conditions are also only available in the paid plan conditions you might be from, are already familiar with them from the surveys. Can do conditional linking. Serious. If someone says no, then you could go to a follow up question on that. And I'll just say, see that this is actually German here. So maze, what maize does is it checks for your browser setting. And obviously the language setting for my browser seems to be the German one. Because I'm located in Germany. This makes sense as users who access your prototypes in May, we'll see the correct language right away. But I'm not sure if I really liked this, to be honest, because this is the perfect example because I just don't want to see it in German in this case, but I have to see it and there's no way for me to switch that without changing my user agent. I'm afraid we would just go ahead and create the next mission in this case. So the good thing here is that once you create a new mission, the first screen for the path will be the last creamer screen of your previous mission. And again, it's just the same as before. We're providing the user with a task that's easy and understandable. And in this case, we want to go back to the homepage to solve the task would be closed. The acid over view. And description could be something like find a way to get back to your home screen. And then we would need to define the path which is simply clicking on the X I can appear. And this would finalize this mission. And now again, we can add, I have a question here and the case may be an open question, which would be, please share your thoughts about the conflict flow up to this point. And we just say it's text type. We don't need any image or additional notes. So you can see this here. And it's again, Joan and just says, please enter your answer. This but Knossos and German and it says continuous. So just quick, you know what, this is all about here. And then we would wrap up everything by adding the last, the last mission. In this case, we'll select mission and the last screen that we provide it as the count screen or profile screen. But as the label says account we will of course, also just asked for the account page and the tasks could be something like open up your account page. And again, the description could be something like tried to find a way to access your purse account. And then again, that define the mission by clicking on this button. And that's it. And I hope you had an, you've got an idea of how to use this, of how to configure your prototype. In the next step and the next chapter, I would go through the maze link and discuss how everything is actually looking like when a user would access the link. And after that, we will take a look at the evaluation. So see you soon. 6. The Test Click Dummy: All right, welcome back. Now we're going to take a look at the final main user test case or how ever you want to call it. Everything is already now setup. We finished the Figma prototypes. We imported it into maize, defined our mission to find the correct path and add additional questions. And now it's time to preview the actual result of the test scenario that is also going to be the same now that your users will have. So for this, we can simply click on preview and this will open up a new page and show you how everything's going to look like. And this is just not published yet. But other than that, there's no difference. And of course there's a bar that says there's only a maze. No interactions are recorded. By recording, they mean added to the report and something else. I can just hide this message, but something else that I wanted to show you is the previous chapter. It talks about the language which is defined by the browser settings, which is true. But you can also deactivate. I've changed that. So depending on whether you really want to make sure people see it and specific language. And you can add a snippet tree or you're out, which is defining the language of the entire prototypes. So we can just add question mark LNG equals and then add a language codes. So n would be English, D, I believe would be German. We could just for fun trial FOR which should translate that to French. Were of course the prototypes stays as it is, but just the main content will change to the language. You specify it. But let's go back to English and have a look. So this would be the first page that your test users see. They have a nice introduction here, a nice welcome page. It just explains how this maze test is built up so that users will be guided through the test by missions that will explain stuff and how they use it by, well, basically clicking on this huge blue button and knowledge to start and all this stuff. But obviously important information as we know, not everyone is as familiar with these kinds of interfaces. So let's just get click on Get started to see how it actually looks like. And here you can see a progress bar which shows the progress of the Wouldn't the entire test case, the mission, the first mission, we have our headline, navigate to your app. The description that we entered. So you can see we could have entered a lot, lot more texts if we wanted. Here we see a preview of the screen. So let's start by clicking on Get Started. And this will actually show us a preview of the first screen. It's kind of blacked out so that you understand that it's not active yet. And you can see here the description of the first mission. Here about that, we can see a progress bar which tells the test users and how far they're in the test into the test. And we can see the headline and the description that we provided. And there's a lot of space available, could have provided more descriptive texts if we wanted to. And let's just start by clicking gets started. So you can see we have our interface here. What is not available are these typical bluish highlights. So when I start clicking around at the wrong points, you will see two things. The first thing is no blue indicators showing up. The second one is there's a button saying give up. So whenever uses not managing to complete your mission, he will be able to move on to the next mission and you will get insights and about the fact that the user gave up on this mission. But we of course, know how to continue by clicking here. And that's it. It says, well done, you completed this mission. We're in the next we are on the next page. We can continue to the next question or Michigan or whatever may come. In this case. It's a yes, no question. Did you like this experience? And we say, Yes, Continue. And now we can see that we're here at the next mission which is closed, the acid overview. Find a way to get back to your home screen. Gets started. All right, how to choose the edit by clicking on the exit. All right, Well done. Continue. See the pattern is very easy to understand. Now we have our open text message. These shares parts about the clip flow up to this point. And I would say it may open up your accounts page. The last mission can see the progress bars fill up. This gives us so much motivation to actually finish it. So you can get started by clicking on the account. I can I guess. Well done. Continue. And that's it. There's the thank you page could have been personalized when we were paying for the professional plan. We did not in this case. So still a usable page, even if you're on the free plan. And the data would have been stored here if it was a life prototyped because it was not an order to be able to send it out and collect data. We have to do one thing that's clicked on the blue button that says start testing. Then we would just have to once again confirmed this because once we we switched it to live mode, we cannot do any changes anymore. Because that of course, would influence the data that you will receive in the report. Still you can do changes, but this will then I'm creating a new instance of the same test. And of course, two different streams of reports that you would then have to merge at the end. So let's say sand life. And then we're good to do the actual, actual testing. We can see the patent for copying the link and sending it out to our test users. Here the word will only allow one session per device. Further tests would be then further access. Accesses to that URL will be blocked. And here you can see that you want everything to be tracked. You can of course also switch that off. And here you have to link, can just copy and pasted. Here you can see that you can also hire testers through May. So they also offer the service of recruiting test pupil, which will provide you with a lot of data because it's questionable how valid this data will be since the test users might not fit with your target group. But if you just want a lot of data, that might be a good idea for you. To be honest, I never tried this functionality here. Of course, it's also not for free available. So you can try it out, would be actually interesting if you try it out to, to let, let us know or let me know in the comments how it worked out if you're happy with the results of this recruitment here. Yeah, So there's not much more to say. At this point. We will just have this test here run through by a couple of test persons, affected test persons. And in the next chapter, we will then take a look at the evaluation with a maze. So see you in the next chapter. 7. Evaluate: All right, so let's take a look at the reports. A few test uses went through our maze test case and well, let's just take it out and see how maize displays all the data and have, just have to say it's going to be quite nice. For that. We have now our view here again of our projects is basically the starting point and ARA May profile section. Here we have our instance version one. So as I said, if you want to change something in this figma prototyped that you used or Sketch or whatever, then you would need to do create a new instance of the maze test case once you already imported it and set it to life mode. But in our case, we just have this one here. It was already recording, which is good. So it's still open right now. And you can see already how it looks like for you as the one who's working here. This is not a report that you would share. We'll also take a look at that. But at first, let me explain how everything is built up here. So on the left-hand side you would see and the different blocks that you set up. So we have our three missions. We have a yes or no question, and we have the open test text question. This is called results. Then we also have testers. So we have five testers that went through our thick me. We can go into each different individual here and see how they performed. Here. Up here you can see just an estimation of the, they call it confidence that you can have in the data that you're seeing here, which is a nice feature. But of course it's not stone what they provide here in terms of information. Of course, these are numbers that you can rely on. So they say, if you are testing with five to 20 people, you uncover the most common issues and learn how your designs a form with sufficient participants for accurate results. And if you do 21 to 100, then you can be very confident and even wear sunglasses. And in the third level, more than 100 then yeah. You get the idea. I think still there can be different cases. I mean, not everyone has that many users at hand. Even we don't need them for all the cases. Maybe that's just an app that only has five users. I brought up that example in another class as well. I have seen these cases and why would you then test it with anybody else, right? So this of course, is just to give you a feeling for how many people you wanted. If you want to talk to or share your link with, of course, five to six people should be the absolute minimum. But yeah, that's just to provide you with an idea. So let's get back into the results. Here on the right-hand side, you can see the difference. Well, different information about the block that you selected on the left-hand side. So we are now in the first mission, navigate to your assets. And you can see here some, some information about how it performed. We had direct success rate of 80 percent, which means four out of five testers, where do to complete the mission. And we had 10 pounds, one give up actually on this mission here. And now we can click here to see the heat maps which are very interesting. These are click heatmaps. So here with these, you can also change the visualization from the heatmap to these cross marks for all the different links, the more you get at 1 than a 100 color would change on your, on your heatmap on. So you can just deactivate everything. You can download the view as an image, use it for your presentation or whatever. So here we can see by this heatmap, even if the task was to go to the asset page, a lot of clicks happened here, which is the manual. So many, many users actually wanted to access the assets to the menu. Some even clicked here, are tapped here on the bell icon. And there was just a random tapping around obviously, but also performed quite well. But this could be an issue here and a real, real life example. Then if you see if you take a look at the yes, no question, then you can see it's pretty easy to understand. For testers, said, yes, they like the experience. One testers or 25 cents at nodes is super easy to understand. We even get broken down overview of which test set, what very nice actually. Then here it's the same as slowly. Again, we have the option to take a look at the heatmaps. Now for the next mission, which was very well perceived. So you can see most of the test candidates actually found this the right way in the right spot to click on here. And then we'll just somewhat smaller miss clicks happening. Actually 50 percent. I would say. We would have in a real world example, we would have to take a look into where these cliques came from. If they were just from one person, then by considering that we have five and total would probably be able to not be that concerned about having a mistake rate of 550 per cent because everyone was able to find the correct spot. Here we have our open texts quest question, and we can simply see the different inputs. This is very nice if you want to collect quotes, for example. Can just copy and paste them from here. And it's working quite well. Here you can see the stars. And what they will do is once you, once you activate this star here, besides a quote, it would show up in the report that you can send out to whoever you want. So you can also hide quotes that you don't want to show. Nice feature. I would just leave it or activated for all of the quotes in our case and for the last, for the last mission. Let's take a look here. Of course, the task was to access the, the accounts page. And there was a lot of MS. Clicking here we have a mouse-click rid of 82 percent, which is a lot. Of course here we also see, well, very red is heat map indication for a lot of clicks on the right, I can, but of course this is not very good and would need to be and explored more in depth in a real world example. And now, let's take a look at the public report by just clicking on go-to report. And this is the same information, it's just displayed in a different way. So this is just the introduction to the report is where we start the left-hand side, we have this kind of menu that we can go through, can also just go by that here, click here, or you can use the arrow keys of course as well. Just provides you with an overview. So we have an overall usability score breakdown, right? So that's the summary, summarized usability scraps. It's not that much. Learn how we compute the score. So they actually explain how it's been, it's been done. I would not rely only on this number. It's maybe nice thing to use for your story that you want to tell. But maize is not the only source that can provide you with a rating of the usability. Yeah, That's just put it that way. So let's continue this work. Move onto the next odd like the first mission. And in this case, and we see just a lot of data to get a lot of data from the reports, which is very nice. I love data is the shape of my insights because it's very true. It's undeniable if you provide data from these, from these kinds of sources and no one can argue against them. It's just a very nice thing. This might be a contradiction to the usability score, but this is something that mazes calculating on their own. These are numbers, these are just recorded numbers like the MS click rate, the average duration someone takes or needs to finish the mission, the success rate. These are just numbers that are being recorded that you can use for your own evaluations and for your own. Um, yeah, proof of your assumptions. And you can see the details for the different screens. You can take a look at the heatmap. Of course, there's so much information here that you really have to maybe filtered down and you can download them as images as well. Really think about if you want to show the entire report to your stakeholders or managers. Or maybe you want to download the images that you're interested in and that you'd think that makes sense in, in your, in your presentation may be. So because It's just a lot, it's like the, the, the, it's like the raw data sheet at the raw data of your user tests. And this can be overwhelming. This can also be confusing. So be careful. If you want to discuss this in your team, for example, and you're all familiar with your AKS and how this needs to be interpreted, then totally fine. But maybe not for everyone who is not that deep into the topic tier, we have very similar visualizations of the data that we saw before. And this goes on now for all of the mission, September were very similar. And here we have the not good, we have the free text inputs that we received. And here we have the last mentioned. But again, from a content data content perspective, it's the same that we saw before. Now, one thing I wanted to talk about is AB tests because I mentioned it at the beginning. And as you can see, it's not natively implemented to do these kinds of AB tests. I did them. And it's, it's theoretically possible. I mean, the idea of an AB test is that you want to test two variants of the same thing, that if they will be a button or whatever, and you want to test their performance against each other. So in using maze, you would have to create two projects which are the same but only differ. And this one thing that you want to try or validate against each other. So it's not possible in the free plan. That's the first thing. Because you only get one project in the free plan. Then in the paid plan, you would create these two versions. Then send out the links to different people, and then you can evaluate which one performs better at. This works very, very well because you get the, all the data and you can just put them above each other and compare and see what the differences are and what you might want to turn a bit and which variant you want to choose from. Also, this entire report section can be, as I said, quite overwhelming even for our lot. So maybe it makes sense to check out my courses on user interviews and surveys. As I also talk about the reports or the, the insights and how to work with them, how to boil them down to their essence so that you have something that you can present, that you can build your work up on, right? So might be a good idea to check it out if you haven't already. And other than that, I hope this broad some insights to you. Please do not leave yet. I just want to tell you two things. The first thing would be about feedback and the last thing would be then of course, the class project. So stay tuned and see you in the next chapter. 8. Feedback: As you may know, I'm a fundamental believer and always learning. This is one of the reasons why I'm creating these classes. And in order to share some of my knowledge with you so that the community itself can evolve and become better, of which I will then at the end also been since. But right now, I want to ask you for your feedback. Please tell me your thoughts about this class. What did you like? And what did you absolutely hate sin only by understanding your thoughts and depressions. I'm able to improve. And only by improving a can provide you with better content for each time I'm creating a new class. Thank you. 9. Your Class Project: And that's it for this course. Congratulations for completing all chapters and I hope that you were able to take some new insights away from them. Maybe you already have and mind on where to apply your new knowledge and use the tools and workflow I explained in this class. Now for this class project, I would like you to create your own maze, test and evaluate the results. You can use any prototype that you want. As this class was not so much about the prototype itself, but rather about how you transform it into an interactive tests scenario and haven't been tested. So you're free to use a prototype for any phase. And of course you can use any prototyping software that is compatible with maze. Then create your main test case, setup your missions and a question. Send you a link out to a few test people who can virtually be anyone. If you don't have real test user pool, you could simply ask our friends or family. And you'll be basically good to go take, take a look at your evaluation and send them over your deliverable. And if you want, I can provide you with feedback about the maze test case and what you can improve in order to make it even more effective. So that's it from my side. I wish you a lot of fun with your assignment. See you in the next video and goodbye.