Hey, in this video what we're gonna talk about is  reporting your UX project. So, and whether it's, um, you know, you're gonna have  to report to somebody, whether it's to, uh,  a larger company, we're gonna expect maybe a,  a slightly higher level or maybe just working  with one other person, even if it's for yourself. You need to kind of correlate your data in some way. Now, best is to take notes while you're doing it,  rather than kind of like trying to observe. Um, say you're doing a in person one  or an observational test is  to write notes as you're going along. Write it on post-Its yay we get to write more on post-Its,  but it means that, uh, afterwards it becomes really easy  just to kind of group them together.

So say if you are going to do a really kind of ad hoc, kind  of rough presentation to the gang right  after the user testings, you can start putting some  of the post-its together that are quite similar. Okay. And it makes it really easy to kind of group them  and, you know, and deliver those without having to go off  and rewrite it and retype it  and add a bit of extra work that might not be necessary. Now, on the post-it notes, you'll be writing things like,  uh, maybe questions they had. Okay. Or just quotes they might've,  things they might've said that might be,  um, useful to the team.

Uh, you'd be tracking things like how many clicks it took  to get to that task, okay. Um, where they ended up instead of, okay, uh,  maybe they went somewhere else instead of, um,  and yeah, just kind of like language  that they used when they were kind of talking  or verbalizing some of the problems  or, yeah, things they liked. Now it's really important with the reporting not  to turn it into something  that's maybe bigger than it needs to be. Um, a really good idea is just to  schedule in a meeting right  after your user, um, user profiles are in. Um, so if you're doing in-house stuff, um,  just make sure you know when your last person finishes  and everybody's ready to meet, and hour after that,  or an hour and a half, so you've got time to have something  to eat, and just kind of really sketch up the ideas  because it always gets fuzzy afterwards  and you start thinking about it  and you start adding your own kind of layers to it. And it's better just to get it out while it's raw and fresh.

And it's really easy to recall certain people,  certain things they said, it starts getting a bit blurry  and a bit messy if you leave it too long. So do it straight away is my advice. And that includes, uh, the online testing as well. Know that, um, you know, if you use user testing.com,  they're gonna give you a kind  of a response time and time it takes. You can tell when people have, um, being picked up in terms  of starting it and when they're expected to finish. So you can really, um, you know, tie that down  to really specific timing as well to meet with your team,  even if it's online, just to get the results out.

Now for, uh, maybe a more formal presentation,  it'd still be, um, you'll,  you'll be expected to produce a summary. Now a summary should be really short and brief  and to the point, okay? Do not have a couple of pages. And my advice is one, a four page, but,  but keep it still quite light, even. I don't want a full page of text. What I wanna see is more like a magazine layout.

So if you're a graphic designer, this might come naturally. Um, you know, uh, you're gonna use things like pull quotes,  so some of the quotes to kind of liven it up, add some  of the, uh, questions that they might have asked in kind  of larger, bolder type, uh, photographs  or screenshots with highlighted areas  of the problems they might've been having. And just keep it to a brief summary. Like it, it will depend on your project,  but, um, the best ones are ones  that people are actually gonna read. So, uh, you know, um, 200 words fine. If you start getting to the kind of thousand words  and 2000 words, it gets to a point  where people are gonna grab it, they're gonna say, great,  and then never gonna read it.

So you want it to be more like a magazine, um, you know,  rather than a textbook. Okay? You want people to pick up, grab bits out of it,  and be able to refer to it quite regularly. Now, what you should also do is print it off, print it off  as a poster as well, tape it together  and stick it up places. And you can always refine this. This is not, make sure all the  expectations are set by everybody.

That the summary's not going to be this leather bound thing. It's gonna be a quick, rough understanding of the project. And then you're gonna go around and iterate. Remember, it's all about the MVP,  the minimum viable product,  and that includes the testing as well. Just getting enough done to get step forward,  and then go back and test and then step forward again,  you might end up with five  or six summaries that kind of get closer  and closer to the end, and they become super helpful. All right, let's go check out the next video.