How can you confidently present your UX research findings?

Understanding your audience is a key step when crafting your presentations, I cannot stress its important enough. Sometimes as researchers we want to showcase how we worked and what we found and we do so with a lot enthusiasm and passion because that's our job. But this passion might not be shared by others. When we present, we should always put ourselves in their shoes and think "What do they need to know?", "How should I share it?" and "What can they do with this?". This can help you define the level of detail, the structure of your presentation and the rhythm.

One of the most important phrases I learnt early in my career was "So what?", i.e. what should I do differently because of this additional insight being shared. As a UX researcher, being proactive in surfacing the "So what?" early on in the presentation makes it much easier for your target audience (e.g. PMs, Engineers) to digest what you have to share, and understand how it can be actionable in the course of product development.

I absolutely agree with other opinions about the audience. Also, you should think about the goal of the presentation and the outcomes you want to get. Why do you share this? To convince others that the product has a real problem? Or to discover a scope for potential growth? Do you want to surprise or even shock the audience (it's actually helpful if, for example, stakeholders do not believe that our users have a problem) – the goal depends on the outcomes you want to achieve.

Your research findings should balance the business and users' needs. Also, it should include an executive summary of the findings

In my experience First of all Understanding who we are presenting to designers, developers or stakeholders. Personalize your presentation to their level of expertise and interests. Present only meaningful and relevant data. Explain your research goal present insights and give them recommendation based on this research. It would be great if we use some visuals like charts, graphs, and user journey maps to make complex data suitable. Clearly explain user problem research process and way solution.

Here's how I generally do it: 1. Find a Hook: First, I find a catchy hook to grab everyone's attention. I kick off with a scenario or problem that's relatable to them, making it more engaging right off the bat. 2. Dive into the Story: Next, I dive into the core findings but in a storytelling manner. I usually start with the main findings, then zoom out to the summary, insights, and recommendations. It's like giving them the juicy stuff first, then explaining the "why" and "how" behind it. 3. End with a Bang: Lastly, I end with a vision of the future, highlighting the opportunities and recommending action steps. It leaves them with something to look forward to and act upon.

I highly recommend every researcher to explain all “what if” scenarios. What if we solve this problem? Suppose we don’t? In other words what are the consequences for customers and business? How can this or that insight contribute to product evolution? And please please please don’t forget about product and business KPIs behind the storyline. While telling a story, we still need to be precise and concrete.

Here is how we did it with “Mahatoky”, a Human-centered assistance for Malagasy public services: — Provide a clear context on what problem are we willing to solve and find the biggest constraints. For example, “Only 20% of the Malagasy people has access to internet” and few of these 20% has a good digital literacy. — Highlight personas with the real story of the citizens — Highlight Key learnings — Highlight testimonials, as it provide the real thoughts of citizens, and it will help build a strong empathy maps. — Highlight some directions to explore Finally, don't forget to embellish each steps of your research with authentic photos.

Framing, framing, framing. I cannot stress enough how important it is to frame the objective, problem statement or insight before you go into the specifics. Statement ? evidence + evidence NOT evidence + evidence ? Statement Many in your audience might be hearing the findings for the first time. It's crucial to give them the context to the enquiry (We wanted to understand X), before you hit them with the facts and responses (this is what our users told us). Many research teams also make the mistake of spending too much time on methodology explanation. This is important of course, but make sure you get to the heart of the problem first, and leave time to supplement on methodology or questions afterwards.

One thing that isn't usually discussed enough is the flow of the research "story". The same insights, data points and details shared in a different order could make up an entirely different story for your audience. It's worth asking yourself as you draft your story: What does what I'm about to tell say about the previous insight that I shared before? What makes more sense to introduce next? The flow of your story is the taste that your narrative leaves in your listeners mouths.

Avoid cramming your slides with text, it might steer them towards the text rather than what your saying and it can be quite distracting. If you're also using your decks as reports, create two "levels" of slides: one with top level titles and one with more detail, to be consumed async (you can hide these for presentation mode).

By virtue of the occupation we're in, we are visual communicators! We map journeys, we prototype out solutions, we personify users, we constantly illustrate our thinking through artefacts and by giving form to abstract concepts. I think presenting research insights should benefit from the same focus on "physicality". Charts with focal points, verbatim quotes with accompanying screenshots, snippet video recordings where privacy allows. Every insight gains realism and context when accompanied by simple visuals.

I also love adding animations and interactions straight into a presentation. Have a flow or micro interaction you want to show off...add it as a GIF and let the audience see it. Got a quote that really demonstrates your findings? Use it. Play the video alongside a relevant visual. Have visualisations of what was tested vs future recommendations. Show these and share the why so your stakeholders can see not only the problems or findings, but how they could be solved.

Visuals are understood and retained much longer than plain text shall ever be. For every insight, accompanying it with a visual relevant to it is a good starting point.

Use visuals like charts, graphs, and infographics to present data in an easy-to-understand manner. Ensure that your visuals are clear, concise, and relevant to the findings.

Here's how you can practice and rehearse: 1. Practice Aloud: One way to practice is to do it out loud, which helps you get better at time and delivery. 2. Use Tools for Recording: Record your practice to help you judge it. 3. Look for Feedback: Practice in front of a coworker or friend who can give you helpful comments. 4. Practice in the real place: If you can, practice in the real place where you'll be giving your presentation so you can get used to it. It will be more helpful than you think!

Practicing and rehearsing, apart from giving you comfort and confidence, may also reveal the gaps in your story. The slides are often visual, with the story either narrated verbally or captured as presenter notes. Either way, as a reflective practice, rehearsing may help build a stronger narrative and present a complete, compelling story.

I almost never rehearse although I speak publicly almost every week. What matters most is knowing your subject well. If you do, you'll be able to speak freely and confidently. If you find yourself rehearsing too much, it might be a sign you need to deepen your knowledge of the subject, or simply improve your vocabulary.

Practice your presentation multiple times to ensure you are confident and can speak fluently about the findings. Time yourself to ensure you stay within the allotted presentation time.

Practicing and rehearsing is always an optimal idea. However, we often find ourselves in situations where we cannot meet up with practicing and rehearsing. This could be due to time constraints or impromptu meetings. I think these are situations which benefit from having an indepth knowledge of the subject area...in this case, one could just go with the flow!

A great way to anticipate questions and demonstrate your expertise is to envision a bulls-eye: 1. In the very center ring, list all questions you anticipate directly related to your research findings. Think through contextual data that help support the insights or past supporting evidence. 2. In the adjacent outer ring: Questions that relate to company strategy and roadmapping. How will these insights impact the near to long-term timeline? How do they relate to business objectives? 3. For the final, peripheral ring: How do these insights relate to companies within the same industries? Is it on par with competitive data? What direction can future research take?

You can anticipate questions by reviewing your data and list out parts that makes sense and parts that does not make sense in the first glance or you yourself might even wonder why is it that way. Then you need to think from other people job roles, what would they focus on and care about, like how does this impact user's willingness to buy, user's frequency of using the product etc.

Prepare for potential questions and objections your audience may have. Having well-thought-out responses will enhance your confidence during the presentation.

Anticipating questions is like having a crystal ball for your presentation success, here's what I do most times: ??Put Yourself in Their Shoes: Imagine what your audience knows and what might puzzle them. Be their guide to clarity. ??Review Your Research: Dive deep into your data to spot potential gaps and ambiguities. You'll be armed with knowledge to conquer any question thrown your way. ??

What I like to do is send out an agenda before hand, with a bit of background info on the presentation. That way, the listeners are pre-informed and could even read some documentation beforehand (some actually do), then id like to ask them to think about questions beforehand and send them to me beforehand. I can use these as part of the presentation or answer them afterward. Of course, there can be more questions after your presentation, but if you use this neat trick you will have an idea of what your listeners are looking for and you can prepare accordingly.

In the ever-evolving world of UX research, we're witnessing a pivotal shift from traditional presentations to a collaborative and co-creative model. At the heart of this transformation are collaborative tools and research repositories. These platforms facilitate dynamic updates and follow-up discussions. They also provide the ability to tag team members for immediate input, interlink with relevant studies, and integrate diverse media, including videos. More than just a means of sharing findings, this approach fosters active team participation. The continuous feedback loop ensures that research remains a living, co-creative resource.

After the presentation, follow up with stakeholders to address any remaining questions or concerns. This demonstrates your commitment to the research and its impact on the project.

It's fascinating to observe UX research evolving from a specialised area focused on identifying product issues and offering insights and recommendations to a broader, strategic discipline. It is transitioning into a cross-functional discipline, and it's gratifying to witness decision-makers incorporating research insights into their business roadmaps and future plans. This transformation is only achievable through actively sharing and engaging in discussions across teams, stakeholders, and clients - not just the research findings but also the outcome & impact of the research based designs on customer satisfaction and overall business growth.

Research is a collaborative effort. Scalable insights are often obtained from a fresh pair of eyes. It's always vital to further dissiminate findings and follow up on feedback. I learnt a lot from presenting and publishing my work among both academic and business audiences.

This is probably the thing that makes most projects, or pitches fail. Not understanding ideas as an artifact of a sales funnel. It's not your client, boss, user to remember you, and sales today are multi touch points. So take a step ahead from the sales world and send a summary of your presentation with the most relevant feedback to everyone. This will give all a common ground to discuss and then do personal follow ups with some Stakeholders and ask for more out of the record opinions or thoughts. The overall way you stay on your stakeholders minds vs others is what usually closes a deal, a pitch or gets funding for more research. Don't do the highschool thing of presenting something and expecting a grade. It's a process.

As a researcher, it's important to approach presenting research findings with objectivity and without personal bias. To achieve this, rely on data and evidence that support your conclusions. This helps convey information convincingly and reliably. Additionally, openly acknowledge the limitations of your methodology and the data used in the research. This demonstrates your commitment to transparency and strengthens trust in your work. Lastly, based on your research findings, provide actionable recommendations. Explain how these recommendations can enhance the user experience. This helps your colleagues or stakeholders understand what actions should be taken based on your conclusions.

Presenting UX research findings as unveiling a secret recipe. Begin by building anticipation, setting the stage for the main course, your research findings. Each insight represents an ingredient in the recipe, and the presentation showcases how these ingredients combine to create a delightful user experience. Much like a chef balances flavors, emphasize the importance of harmony in your research insights. Practice your presentation to perfection, like a chef refining their culinary skills. Invite your audience to savor the unique user experience dish and encourage them to apply your "Recipe" in their own projects. It turns your findings into a flavorful, memorable experience for your audience, just like a chef's secret recipe??

Striking a Balance Between Qualitative and Quantitative Data. Your audience has a natural ability to remember the vivid qualitative aspects of stories involving people. However, stakeholders have a strong desire for quantitative data that provides insights into scale, causation, and the number of occurrences or individuals involved. It is important to complement your qualitative data with quantitative evidence to enhance its credibility and support your arguments.

Create a plan. Research that's handed off without a plan isn't useful. Presentations for C-suite execs needs to be succinct and clear. But any proposed solutions should also be scoped. Presenting the research about a found problem or opportunity without scoping solutions will get shelved.

use this strategy. Research that is passed off without a plan is useless. Presentations for C-suite executives must be concise and straightforward. However, any proposed solutions should be scoped. Presenting research on a discovered problem or opportunity without exploring solutions will result in the research being shelved.