Hello, everybody. Welcome. We're gonna get started. Go through a little quick intro before we get into the workshop, and then we'll get right into what you're all here for today.

Our topic, how to effectively present your research to your team, stakeholders, or anyone else that you have to share it with. So let me just do one final tech check. Just gimme a thumbs up in the chat if you can hear me. That's a lot of thumbs up. Cool. So all good there. So let's get started. My name is Joe. I'm gonna be your. Guide instructor for the next hour.

A senior product designer and researcher and have been for past over 10 years. And currently I'm the design advocate here at lista. So in that role I do a whole bunch of different stuff, but a lot of it is geared towards education workshops like this and creating material. That is going to help people be successful with their research initiatives.

Hopefully using Lyssna but more generally understanding how you can get research off the ground, do it successfully and efficiently, and really use it in a way that's gonna lead to tangible, impactful changes to your product. And we are gonna spend a lot of time talking about that stuff here today, no matter what topic we're talking about what the focus of the workshop is.

My goal is for everyone to leave this workshop with real, tangible skills and confidence. To put the stuff that we do in this workshop into action. I want you to learn a lot. I want you to have some new facts and information in your brain after, after this workshop. But more importantly, I want you to feel like you have something to build on and can easily take the stuff that we're doing here and make some progress or get the wheels turning in whatever you're working on.

I asked two big questions at the end of the workshop. Last thing before we go. Did you enjoy this workshop? I'll ask that right before we sign off. I hope that, if you're dedicating an hour to be here with me, Lyssna in taking notes making some time during your lunch break that you enjoy it, everything's smooth, and it's goes by quickly.

But more importantly, do you feel like a better, more confident designer, researcher, product person than you were an hour ago? So those are my goals for this workshop. I'll ask you those at the end and hopefully I'll see some thumbs up in the chat. All right, some quick tips for getting the most out of our workshop.

First one, I'm gonna share this link with everybody here in the chat and I'll share this again at the end of the workshop. But follow Lista on the Figma community. I'm gonna be sharing. A bunch of a full resource guide from this workshop with the recording, some design templates and a bunch of further resources that'll come in a follow up email to all of you.

And that's something, a new initiative for us with Lyssnaing to get our community on Figma up and running. We have tons of great templates, presentations, useful stuff to help get you started in research. So check that out. Follow Lyssna and either way, I'll be sending out some template files and a full recap recording and resources from the workshop after.

All right. Everything is recorded. So like I said, I'll be sending all of that out after the workshop. You'll probably just get an automated email with just the recording and then I'll send the resources out after. So that being said, you'll have this recording if you wanna come back and check anything out.

If you have to leave early, hop out for a minute. You'll have it all there to come back to whenever you have some free time. So everything will be recorded and you should have that I think, pretty quickly after the workshop's over, you'll get that sent to you. So keep an eye out, keep the chat open and active.

We've already got that covered. I think we've got a very good active chat. If you have questions, go ahead and drop 'em in the chat as we're going. I'll try to get to as many as we can. And if you I'm gonna be throwing out some questions to the group, getting your thoughts on some stuff, opinions maybe a couple.

Quick, one, two minute questions that I'll throw out there to the group and we'll be doing that all in the chat as well as some links and other resources that I'll be sharing with you. So keep it open. I got it, I got my monitor set up better than our last workshop. So I got the chat right in my main view here.

So if anything comes up, drop it in there. I'll see it and get to it as soon as I can. Finally stay comfortable, happy and hydrated. Just a quick workshop today. But still make sure comfortable got some water. If you need to get up and stretch for a second, go for it. We can catch you up on anything that you miss.

And like I said, I'm gonna be sending everything out after if you wanna come back and take another look at it. Sound good everybody? Yes. Nice. All right, so let's get into our topic for today, which is presenting research, our workshop title, how to effectively present research to stakeholders. We're gonna start with something that you might know already or have felt already, but breaking down a little bit further, the challenges and the scenarios that come up when you are presenting, talking about or communicating things that happened in your research process and some of the unique challenges of that.

Okay, so I'm gonna start first with a story about a project that I worked on. This is a project that I use a lot for examples in workshops, but it was a test prep app that I worked on years ago. And it was for students studying for the GRE and GMAT to get into grad school. So basically a test prep app.

This was the best screen recording of a prototype I could find here. So I'll give you the idea. But essentially it was a way for students to study practice and one of the main bits of focus was to really give students a clear idea of how they should be spending their time when studying. So a lot of what to work on, a lot of guidance on the areas that are where you could easily improve or score some points.

And it was a big project and there was a lot of testing involved in it. A lot of all types of studies and methodologies. But particularly what I'll focus on here were a bunch of usability studies watching students actually. Complete these practice tests, create them and give a whole lot of feedback on them.

So I, let's see here. I ran, there was one, probably like a two week period where I was doing usability studies moderated studies. So I was getting on Zoom with students. They were running through the prototype and there were some pretty intensive usability studies. They took a while. There was a ton of feedback.

Say I did about 20 to 25 of them in a two week period. So it was a lot. And when I was finally done, I had a meeting with the client, the team who was hiring me to build or design this. And we had, five or six people from their team. And after those two weeks, they said to me. Exactly what you're seeing here.

Alright, Joe, how'd it go? And this is a look at what I had in front of me except probably even more than this. This is best thing I could find, but I had hours and hours of recordings, notes, transcripts, just a pile of feedback from these usability studies that we were doing.

Literally probably 30 plus hours of recording all with really, packed with feedback about this practice test prototype that we created. And so this is what I looked like here. When, I had a basically a 30 minute meeting to recap all of that, right? I was there for all of it.

I was running those studies, I was talking to people, I was seeing what was going on and I had the material, I had the feedback. And I realized in that moment, as a younger, I. Slightly less experienced designer that this is gonna be tough to, where do I even start to get through some of this stuff?

And this is a challenge that I experienced a lot and still experience when coming back to research. But I think this moment was where I really, it really clicked for me that the research is important, but also how I present it, communicate it and, relay it back to my team or stakeholders is a challenge in itself.

Presenting research is tough, right? For a couple reasons. Research findings are complex, they're nuanced and they're often overwhelming. Just like the example I showed you, there's a lot, right? Even if you're doing, not doing such an extensive usability study and don't have hours of recording, even if you're doing something more simple, there's a lot to cover.

If. Your team says, Hey, what happens in that research study? Give us the breakdown. Chances are that there's gonna be a lot there to go over and a lot of context needed to really understand it and be able to make sense of it. Presenting research can be challenging also because of who you might be presenting it to.

You might be presenting to stakeholders that are more in a business or not as hands-on product or research role. Team members who aren't familiar either with the research initiative that you are doing or just the UX research process in general. So in the example I just showed you, I had a mixed audience of, a product manager and some people who were more familiar with it.

But also the CEO of the company who's coming in totally fresh to this research study and testing that I was doing. And also in a lot of ways to the research process in general. And I think the last, and one of the less, let's say, underrated reasons that it can be difficult is because in a lot of cases, at least, there's a pressure or motivation to produce results or solutions.

A lot of times pro it feels like progress in a product is measured by the output, right? Building new things, creating new features, launching new solutions. And research sometimes can seem like a, a detour to that or a, something that delays that output. Now, as good designers and researchers, we know that.

Research is the shortcut or the best route to a good product. But if you're working on a team that is really focused on delivering and shipping solutions, it can be difficult to present research and maybe raise new questions when it feels like the marker of progress is to ship solutions to them.

So we have all these factors that come into play when we're talking or presenting our research that makes it difficult. And I'd say to sum it up, it's really trying to pack a lot of complex information into a short and concise and clear presentation, not an easy task. So how you communicate and present your research findings or initiatives.

I. Can affect whether or not your work actually makes an impact. If it's done poorly, like the example I showed where I was scattered and a little disorganized or overwhelmed on what to present, then a lot of those good findings and research that you did can go to waste. It can go in the old research stuff folder, even if there are some gems in there, some really potentially game changing insights from users if you're not presenting it effectively.

It's gonna go, maybe not directly in the trash, but it'll slowly fade out until there's no, no real action taken on it. On the other hand, if it's done well it's gonna lead to better decisions, faster action, and start to build a culture of research, buy-in, really getting your team and stakeholders to see the value in research and to see it as a path towards building a great useful product. Not a kind of vague windy road or detour to it.

A lot of times you hear or maybe have said yourself as I have, that you have to fight for resources for research, whether that's time, budget it can often feel like an uphill battle to get that buy-in, get approval for the time needed or the. Budget or resources to run a study. And I wouldn't say that's totally wrong, that you have to fight for resources.

'cause it is the reality in a lot of cases. But to just give you a kind of a different perspective on it, there's another way to get that buy-in, which is to prove the impact of research. So not necessarily just continuously asking your manager or your, your team to let you do this research or trying to find new creative ways to do it on your own or under the table ways that you could get it done.

But more the approach of proving the impact and the way that you communicate and present your work is gonna be a big factor in not just, convincing your team or stakeholders to let you do that research or the value of it but to let them see it for themselves in the impact that it's having on your product.

Okay, so we're gonna go through how to present your research in a pretty simple three step framework. And I'm gonna give a bunch of examples for it so you can see it in action and apply it to your own work. And we're gonna use an example scenario for this workshop so we can have one kind of coherent project or role that we're working on.

So we'll introduce that now and then get into some of the best practices and the keys to presenting your research. So here's our scenario. We're gonna imagine that or you're gonna, imagine you're a product designer, researcher at Airbnb, someone who's doing some research on the product. This is a totally made up scenario, by the way, and a little bit light on the details, but it's gonna work well for some of the examples that we're shown here.

So if there's anything, I don't think you'll need all the details to connect these examples and see it in action, but if you have to use your imagination a little bit, that's okay. We're gonna imagine that in our role doing research for Airbnb, we've conducted. 25 moderated usability studies specifically on the checkout process.

So not checking out of the place that you're staying in, like you would at a hotel, but the checkout, add to cart book, your stay process. So we've, we're gonna imagine that we've done these 25 usability studies. We've observed users, we've given them some tasks, we've watched them browse, we've watched how they select the place to stay, and most importantly, focused on that checkout and payment process.

So just like the example I showed at the beginning, we've got hours of recording feedback, just a ton of information coming out of this. And now also, like my example, it's time to present those findings to your team. The details of this study and the presentation, like I said, not as important because this structure and the steps that we're gonna walk through are really gonna apply to anything.

But the idea here is that we've run our study, we got a big pile of feedback and information, and we have the challenge of being able to deliver that clearly and concisely to our team in a short amount of time or a cl quick presentation. So here's what we're gonna cover for this one. The key is to a great research presentation in order.

I'm gonna start with setting the stage. We'll move into two, focusing on the right stuff, actually delivering the findings from our study and talking about kind of the core of what we learned and what came out of it. And we'll end with our third chapter to a great research presentation, which is making it stick.

Making sure that the research that you've done and the way that you've presented it is gonna build some momentum. It's not gonna end in that old research folder. It's gonna be put into action and really lead to tangible improvements to the user experience and the business as well. Let me pause for a sec and check the chat here. Sure. We're all good.

Also, as I'm sharing here if you guys have any scenarios, things that have come up in your work, presenting research challenges, questions like that or even just experience you wanna put out there that might be similar to what we're talking about here, drop it in the chat. I got it Open and love checking out.

Some of those stories about things that you're working on, or even just a co-sign on some of these challenges that you might have experienced yourself. Whoops. All right, cool. So let's start with the first part of a great research presentation. We've got all of these results recordings, all this feedback and data from our usability studies for Airbnb, and we're thinking about how we want to present that to our team.

The first step, as we saw in the last slide, is setting the stage. And again, no matter how good or insightful your research is, the context that you give at the beginning and the way that you frame it and present it can really make or break what happens with that research after. This starting point is a really important one.

It's simple as you'll see, but it's going to have a huge effect on how well received your research is and whether your team's engaged and onboard with it or overwhelmed, confused, and not really sure where to focus. One of the most common mistakes in starting a or doing a research presentation specifically starting it is what I did in the test prep example that I shared with you, which is too much, too fast or too much too soon in the presentation, basically jumping right into the dense stuff, the data charts, quotes, results, recordings.

It can be, it can seem a good strategy to just get right into it, especially if you have a lot to cover. But an important thing to remember is that while you might have been totally immersed in this research and you might have created and run and conducted these studies, your team may or may not have been involved as much as you have or maybe not at been in, involved at all.

So even though you understand the premise of the study and all the basics around it, your team might not. So if you jump right into stuff like you're seeing here on this slide, right? Feedback, big jams, post-it notes, recordings, that you could lose your audience right from the beginning if you're not setting it up with the proper context.

So what does setting the stage mean? Providing background and goals? Why did you do this research? Sharing the method, what did you do? Connecting it to opportunity and impact. Basically, why does this matter or why should I as a, stakeholder or teammate care about this research? Three pretty simple things to start your presentation.

They can be done in a lot of different ways, depending on the nature or the complexity of your study. But still across the board, it's gonna be the same principles and the same overarching important start, which is making sure that you're giving your team context before you just jump right into the research.

Okay, so let me see if we have a question in the chat here. Aisha, when presenting to stakeholders who might not be familiar with UX or research methods, how do you balance storytelling and persuasion without oversimplifying the insights? Let's see. Slides. Yes, I can share the link to the slides. One sec.

Share these in here. I'm gonna share these after as well. But drop those. Aisha for your question, I'm gonna, I think I'm gonna get into this in, I think this is gonna be answered in the next section. 'cause we'll be talking about actually sharing your findings and how to curate and focus what you're sharing and how you're communicating the actual findings.

So if that doesn't get answered, bring it up again. But I think in the next section, when we actually get into showing the research you'll get an answer to that. Okay. So for our first step setting, setting the stage, we're providing background, sharing the method, giving the overview and context we need quickly to make sure that our team is on board and going to understand some of the more complex or more detailed stuff that we're gonna be showing in the presentation.

So if I were, we'll have some of these slides here, these Airbnb slides where I'll be, I guess acting out as the researcher or product designer here presenting to my team. This is what it might look like to set the stage first. Our title side here, our research study recap key findings and takeaways from our recent round of moderated usability studies.

And then we're getting into the background and research goals. We saw a trend maybe through analytics, through other sources or signals of users browsing, selecting a place, and then dropping off in the checkout flow, especially after seeing the price breakdown and right before confirming their payment.

Simple setup here and maybe oversimplified a little bit for this workshop, but not by much. The idea here is to give a little background about what the reason for this research in this case that we saw a lot of. Browsing engagement, people finding a place that they want to book on Airbnb, but then dropping off right before, right as they got their breakdown and needed to confirm and pay.

We wanted to understand why this was happening, whether it was product related, something we could improve or some kind of hiccup in the checkout process. Environmental, something around their behavior or habits in booking a place to stay or booking travel accommodations or otherwise. We conducted 25 moderated usability studies.

Participants were giving a task of browsing and booking a place, and we observed, recorded them and maybe got some, poked or popped in with a couple questions and prompts for them along the way to observe and Lyssnaed to some of the feedback they had as they moved through the flow. By understanding user motivations and decision making factors to booking, we can identify some friction points.

This will help create a smoother, the idea here is to create a smoother process for booking a smoother checkout process and experience, and also, related to our protocols, increase the conversion rate of new bookings. Okay, so right there, that was a pretty simple overview here, right? And like I said, maybe a little bit more simplified for this workshop, but the idea here is we're setting it up with some of the basic information about the research.

We can't just dive right into quotes videos. Analytics metrics on the studies that we had, and it might seem like something that you could, skip or might seem like something that's obvious, especially if you were in the in it and actually conducting that research yourself. But again, you have to remember that the people on your team might not have been and probably weren't.

So we're setting it up with the context about the study and also getting them bought in, like with something like this on the impact and opportunity. Hey, here's why this matters, right? This is not just for fun to test it out and see if, there's anything interesting that comes up. We're seeing a some signals that this, there are some speed bumps in this process.

We're seeing it affect the conversion rate of people booking an Airbnb. If this is something we can learn more about and improve, that's gonna have a lot of positive impact on the experience and our goals as a company. So don't phone it in with the intro and setting the stage to your research presentation.

Don't gloss over it or just do it on the fly. This is something you really want to spend a little bit of time on before presenting your research. It's simple, it seems obvious, but it is one of the most important things you can do to make sure that everything you present after is gonna resonate, stick, and get put into action.

To put it simply, if you get right into the data from your research, and there are people listening in that don't have the context they need to understand it. They're gonna be lost from the beginning, and it's gonna be very difficult to show the impact or get that buy-in for future research or to put stuff into action coming out of this research.

Let me check the chat real quick. Sorry. We had a couple new chats in here. Let's see. Jay, I'm about to present findings for, oh, you don't have access to the slides. Let me check on that and I'll share with you. I am gonna send them out right after, so I'll make sure everyone has access to them. But I'll do that.

After, right after the workshop, I'm about to present findings from user interview rounds, focusing on understanding our ICPs needs goals, hoping the findings will have a strategic impact on the roadmap. Any advice on how to make the insights lend? Yes, we're gonna talk about that next as we get into the actual insights, but the first step to getting them to land is what we just covered, right?

Making sure that the insights are understood and that the stakeholders or team that you're presenting to have maybe a, an a abbreviated picture of it. They're not. Knowing all of the motivations or details that went into it, but they are understanding the premise of the study. That's the first part.

'cause no matter if you don't do that well, no matter what you present after it's not gonna stick. But in the next section, I'm gonna go into some more specific tips right here about how to present those findings and some tips that I've experimented with and tweaked that have been pretty successful in making sure that it actually gets traction going forward.

Alright, so we got our first part. Simple but important, set the stage. Now we're gonna move into our second part, focusing on the right stuff. We've done a good intro. We've given our stakeholders the context, we've given them the background. Everyone's on board, everyone's following along with our research.

They're not. Lost or getting drowned in statistics right off the bat. Now we're gonna get into the actual findings, what came out of that research, and more specifically how to present it. The goal here is pretty simple to clearly concisely communicate what we learned, and more importantly as we'll see what we want to take action on.

Common mistake for presenting findings is information overload. This is pretty similar to the first one that I talked about of just jumping right into the findings. But with this part, even if you've done a good intro and provided that context, you can still overwhelm and lose your audience if you're packing in.

Every single thing that you learned in your study, right? Here's what happens. And you've got a massive list, or 156 slides like this here detailing every single thing that came out of those usability studies. If everything is a priority, then nothing is. So one of the goals here is not just to present or regurgitate what happens in the study or dump it all in a slideshow, it's to pick and choose and prioritize the things that are really the highest priority to take action on.

As I said, your job's not just to summarize what happened in the research or regurgitate it, but to curate it and prioritize it. So being able to look at a whole bunch of findings and data and things that came out of your research. And choose the ones that you want to emphasize. The high impact, high priority findings.

And as we'll talk about in a second, being able to keep the rest of those findings available. Not just throwing everything out except the top things, but making sure that in your presentation, you're keeping it really focused on the big ones, the things that are most require action to fix a problem, solve a need, or capitalize on an opportunity that you're seeing from your research.

Okay, so this is not a good example of that, right? If we're dumping everything into a messy slide like this one I had a lot of stuff like this for our test prep app. Just tons of feedback. We have some here for our Airbnb example, it took me an extra minute to find my safe places I like that includes pay over time options.

I wish every listing had a video walk through. Maybe someone or a group of people who just really didn't like that red button. In a study where you're getting, especially where you're getting open-ended feedback, you're gonna have a lot of stuff like this. Not everyone is gonna be commenting on the exact things that you're trying to learn about the checkout process.

Now, again, it's not to say that this stuff isn't important, but if your presentation is packed with every single thing that you learned, it's gonna be difficult to focus and redirect on the items that are gonna have the biggest impact on your product. So here are some better, more focused, more higher impact ones to present.

Again, making these up, but, to give an example, in comparison, 19 of 25, users said the final price was more than expected. So people went through the booking process, got to the end screen where they're seeing the price breakdown, and we had some feedback that it was more than expected. It might push them over budget or make them reconsider booking another one here, 67% of users only noticed rules or restrictions at the final step, which caused some friction, some reevaluation, or a decision not to complete the booking.

And this is an actual one I found when I was putting these examples together, that there's, it's like a friendly dog lives there. It might come in your yard or your house, but that's one of the, quirks of of staying at this place. So we see some findings here that people were.

Not noticing, surprised by the price or maybe some of the terms or, rules right before they went to checkout. These two themes or findings that I'm showing here are the ones that I would highlight in this example study. They have a clear tie in to the user drop off, right? We're seeing that drop off at that end screen or confirmation, and we're seeing a overwhelming amount of feedback about some surprise, costs or rules that are happening there at the end. So again, while the other stuff is not unimportant and shouldn't be thrown away, if we're looking to understand why people are dropping off right before the confirmation, these would be some of the things that I want would wanna highlight specifically the overwhelming amount of users who were being surprised by the price and maybe reconsidering booking at it or dropping off right at that last step.

So what about everything else? You're not throwing away your other findings. And I think this is one of the big challenges of presenting research and cutting down the what you're presenting as a researcher, especially if you are actually conducting the research. It's hard to do that, right? Everything feels important and it feels like some feedback that you're getting, even if it's not totally related to the goal or the focus of your study, it's still valuable, right?

So you don't wanna throw that out. You don't wanna leave that out of your presentation. You don't wanna just not bring it up and let it disappear because there could be something useful in it. We're not throwing it out, but we wanna have a home for that research and make sure that it's available.

But again, not taking center stage in our presentation, creating a big mess of findings and a lack of focus. So a great way to strike this balance is. Focus on the big stuff, the high impact findings, the stuff that we saw right here in the presentation. So it's staying focused and you're keeping the presentation on track about the things you wanna take action on.

But for everything else, you wanna have a place for it and to give access to your team if they wanna review that or if it's something that might be important to come back to later. So the recording I have here is one of my favorite features in Lyssna which is Share Results. If you're doing a study on Lyssna you can just create a link to share the raw results page of any study that you're doing.

In this case, it's a preference test, and I've used this a lot for this exact. Use case, right? I'm presenting something in a slideshow or, a more cut down presentation, but I can also generate a link and include that in the presentation basically to say, Hey, here's the big stuff that we wanna focus on.

But there was a ton of other feedback. If you want to go see that, here's a link. You can see everything. If we need to come back to it and discuss it, we can go to that and see the raw results from our study here. So doing that enlist is very easy. And it's a great way to give you peace of mind as a researcher that I can cut things down for the presentation.

I can focus on the big themes that came out of our research without needing to throw out or ignore everything else that came up. I don't know, Aisha, this is where I thought my answer your question from before. S let me see. Lemme come back to that one. So we have presenting to stakeholders might not be familiar.

How do you balance storytelling and persuasion without oversimplifying the insights? Yeah, that, this is kinda what I was thinking here, Aisha, where you're keeping it focused on the big stuff and you are simplifying it in a way. You are cutting it down for the purpose of focus and, gaining momentum and not overwhelming them with the findings, but also having a place where everything else lives, giving access to that and, inviting your team to check it out, discuss it, and bring something up if maybe they have, see another bit of feedback or another theme that came from that you didn't highlight in your presentation.

So lemme know if that helps. I. All right, we're gonna get down to our last piece of the puzzle here. We've done first, setting the stage, giving the context and the background opportunities, the why, getting our team on board, getting everyone on the same page, gone through, sharing our findings and some of the key aspects of doing that.

Being to cut it down to the big high impact ones, not overwhelming them with everything you learned, but also being able to give them access or visibility to some of the other things that came up in your study. The last chapter of a great research presentation is making it Stick, basically. Now that you've heard the findings and understand what came out of this research and some of the big themes, I.

What are we gonna do next? How are we going to not only just digest this information or understand it, but put it into action to lead to real product improvements? What happens next if you do? I said on this slide, even if you do everything else well, but I would say especially if you do everything else well, if you do a good job on those first two sections, then even more so the end of your presentation is going to have your audience thinking, okay, what do we do next?

When I was making this slide, I was thinking of like those old viral, like antivirus ads where it would like scan your computer and say you have a hundred viruses. Buy this product here. If we don't do a good job, if we do a great job of identifying the problems and communicating them to our team, and then just.

Drop off after that. It's like opening up this can of worms of all possible things we could improve, but not really giving the next steps or solution. So the way that you close out your presentation with next steps is really gonna be a key in making sure that there's follow through on it. And the best way to do this is to provide clear next steps.

So you're wrapping up your presentation by making some suggestions or recommendations. Again, this is going to depend on the nature of your study, your role, your team, but as a fundamental part of it, you are trying to leave that presentation with some specific and actionable next steps to put it into action or keep up the momentum.

These are usually could be follow-up research, recommending additional research that needs to be done, design directions or solutions. So maybe suggesting some possible features that you could begin creating to address some of the things that came up in your research. Those are, I'd say the most common ones in terms of next steps and action items, either further research or solutions.

But no matter what those next steps are, the key is that they have to be specific and actionable. So if there are no next steps, your research just vanishes in thin air. Even if you do a great job of presenting everything else, if you don't take your team through what has to happen next and just leave it there, you're, no matter how good that research is, it's not gonna be used to improve your product and.

The next I guess the next best thing is vague next steps, right? You're giving some next steps and saying, Hey, here's what we should do coming out of this research based on these findings but not being specific enough. And if you do this, your research and the outcomes of those findings might not vanish into thin air, but they're gonna slowly fade away over the next few days.

If there's not a specific call to action for follow through on it chances are it's gonna fade out and never really get used to improve the product. Maybe a little bit more slowly, but it'll still be stuck in that old research folder that I showed at the beginning of the workshop. Okay? So going back to our Airbnb presentation here if we wanted to do additional research right, coming out, this is an example of some next steps that are too vague.

Next steps conduct a competitive analysis. Of other checkout flows, it is a next step. It's better than nothing. It could be the right direction to help improve our checkout flow based on these findings. And the key theme of people being su unpleasantly surprised by the last screen, but it's too vague to really get traction.

A much better more specific example of the same thing would be or way to communicate. The same thing would be what we're seeing here. Again, totally made up, but just to give you an idea, the next steps being to choose five similar competitive companies with comparable pricing structures, maybe other sites where you're booking a place to stay.

Next step would be to audit or do competitive analysis on their checkout flows to see how they communicate fees and pricing transparency throughout. Let's screenshot or document key patterns we might be able to adapt to our flow. We might be able to borrow and put into Airbnb and discuss it next week.

This is suggesting the same thing, right? Hey, let's go see how other sites are allowing users to see a clear price breakdown before they get to the checkout. But the way that it's communicated here, it is, 10 times as likely to get put into action, to gain some momentum and to actually result in an improvement to the product simply because it's more specific.

Another example here, if you, your next steps were to work towards a solution to some of the findings that came outta your research, this would be too vague. Let's design a new order summary page based on the feedback. It's a next step, but again, too vague to really get any traction. A much better way to communicate.

The same thing would be something like this let's, wire frame or design or prototype five ideas for a persistent order summary or cart widget. Something that people can see throughout and see a clear breakdown of the pricing. Let's review them and decide on one for usability testing in the next sprint.

Same idea, right? Let's come up with a new, feature to increase price transparency or solve this problem. But the way that we're communicating it, again, 10 times as likely, if you're presenting something like this, that it's going to. Be acted on and eventually result in an improvement to your product.

A couple extra tips for making it stick. First one is assigning action items and owners where possible. So even going a step beyond some of the examples that I just showed you and figuring out who's gonna do what. This can be a small, minor next step. It doesn't have to be, a full redesign of a certain feature, but if it's actionable and you are assigning that to someone, creating ownership a plan, accountability, a timeline in whatever way you can, that's gonna make it more likely that those initial steps of acting on it actually happen.

And again, that it, there's follow through and momentum to turn the, that research into product improvements. Opening the Florida discussion, asking both targeted and open-ended questions to your team. Maybe, Hey, do you guys have any thoughts on other products we could look at to get some inspiration for the checkout flow or for how they're breaking down pricing?

And as I've said a couple times throughout, giving the research and discussions, a home lista is a great place for that, for the results of your research. But fig jams, slack threads, somewhere where there's a space to discuss it. There's visibility over the research and there's a place and, permission and encouragement for your team to participate with it.

So all of these, taking those specific next steps and really putting these little things behind them that are gonna make a huge difference in whether or not. They go in one ear, out the other, or they turn into action and ultimately lead to a better product and solutions to some of the challenges that came up in your research.

All right, let me check the chat here, and then we're gonna do some key takeaways and wrap up for the day. So a lot of good stuff in here. All right. Christina's or Lizette had a good chat here. I always directly connect insights to recommendations because stakeholders always directly want to know how can we fix this, and how much effort will it cost to fix this?

Yes. You got it. listen here, lemme give you the flame emoji on that one too. Yes. And that's what we're talking about here. Now you can play around with the level of depth of the. Chapters or the pieces to a presentation that I'm showing here, but that connection that you're making and the buy-in that you're getting from it, yes, that is a vast majority of the times.

That's what your team is looking for, right? And that's what you're ultimately trying to get to is a fix. How do we improve this? Once you've got them bought in on the importance of it, how do we improve this? What's it gonna take to do it, and how do we get started? So with those recommendations, the closer you can tie them to insights, the better and the closer you can tie them to outcomes that your team or stakeholders actually care about the better as well.

So if you're able to do those things. And you have a formula for doing it or presenting it, that is that's gonna get you a lot further than just leaving them out there and, hoping someone chimes in on what to do about it. See some others. Christina said, my approach to walking team through results is to have a summary slide.

Perfect. What, so what? And now what? Yes. And mine, I had it worded in this presentation as what, basically what, why should I care and what's next? Same idea here. Let's hit that. That 101 for you Christina. Awesome. And lemme just get to Seth's before we wrap up here. Will the recording be sent out later?

Yes. I don't know if you're still here, Seth, but it'll be sent out right after, along with the resources and a shareable link to the slide so all you guys can access that. Excellent. Since we have five more minutes here I wanna go through just our three quick key takeaways before we wrap up. I think this one's pretty obvious, but I'm hoping that you were able to see it through the presentation today.

How you communicate and present your research and your design work really matters. And more specifically, it makes, it's make or break as to whether that research gets used and put into action, or is you're leaving good stuff on the table or in the old research folder. Even if you are doing really good research, even if you're uncovering really potentially valuable insights and problems that you could fix to improve your product.

Taking the time and having a game plan and some clarity to present it using the setup we showed here is, gonna be a major factor no matter how good or useful the research behind it is, prove it and fight for resources for research. Like I said earlier, many times you do have to lead the charge and take it into your own hands to get the resources, budget time, et cetera, for research.

So that's still part of it. I won't say that's something that, completely disappears, but if you can put the stuff we did today into action and deliver some really concise, clear, compelling presentations, and then. See the follow up of it and let your stakeholders see the follow up and the improvements that come out of it.

That's gonna go a long way in not only, getting the results and the benefit from that study that you did, but building that long-term, buy-in, in research, synthesize and focus. So many of the common mistakes and themes and examples I showed here today all came down to the same thing, which was a big information dump or regurgitation of what happened.

It can be tempting to do that because as a researcher you think all of this could be important. There's nothing we wanna, leave out of it. I don't wanna oversimplify it, but. You want to take the time, but if you do that, you're gonna lose the focus and the momentum behind it. So make sure that you're taking time to not only just deliver what happened in the research, but to really highlight the highest priority, highest impact findings that your team can act on.

The reality is if you're showing everything at, it's going your team and everyone's gonna lose sight of what they can take action on. And probably just be overwhelmed with what's next. So you don't have to throw it out. You can have a home for it. You can link them to a Lyssna results page. You can give them access to everything.

But for that presentation, really try to remember that people have limited bandwidth. Your team is not gonna be able to fix or even comprehend all the different things that need to happen. Your job as a researcher is to look at it, take the lead and say, Hey, here's what everything that came out, but here are the big things that really we believe could have the biggest impact on our goals and the reason why we did this research in the first place.

Alright, everybody we're gonna wrap up since we got two minutes left, but let me know in the chat, did you enjoy this workshop? I hope it was a good useful hour of your time. I hope if you're doing some research or presenting some in the near future, that this was a worthwhile hour to give you some structure and some context around it.

And more importantly, my other big question. Do you feel like better, more confident designer, researcher, presenter than you were an hour ago? I'm gonna share the template for presenting something that you can modify, something that includes all of the notes and tips that we have in here.

Something that you can scale up or down or tweak in terms of the nature of your study and what you and who you're presenting to. But I hope that after seeing the foundation today and these three key aspects where a lot of research presentations go wrong, you're feeling like. You have a little bit more structure.

You're not feeling like me presenting my my test prep research where I would just really had no idea where to begin. But that you've got to see the importance of these main building blocks of a great presentation and what it takes to put that research into action. Let's check the chat here.

Good. Awesome presentation. I'll be sending everything out after the workshop. Slides, recording further resources, templates, stuff like that. So you'll get the recording right after, but I will follow up at some point tomorrow with all the resources. If you're here and registered for this workshop, you will get everything that comes after. Have a great day everybody. Thanks again for joining and hopefully I'll see you in another workshop soon.