How can you tailor your usability testing presentation for technical vs. non-technical stakeholders?

1 Know your audience

Before you prepare your presentation, you should research your audience and understand their background, goals, and concerns. For technical stakeholders, such as developers, designers, or engineers, you may want to focus on the details of your testing process, the tools and methods you used, and the data and evidence you collected. For non-technical stakeholders, such as managers, marketers, or clients, you may want to emphasize the benefits and outcomes of your testing, the user feedback and insights you gained, and the recommendations and actions you suggest. You should also consider the level of familiarity and involvement your audience has with your product or service, and adjust your language and terminology accordingly.

2 Structure your presentation

A good usability testing presentation should have a clear and logical structure that guides your audience through your main points and supports your arguments. A common structure is to start with an introduction that summarizes the purpose and scope of your testing, the research questions and hypotheses you had, and the participants and scenarios you tested. Then, you should present your findings, organized by themes, categories, or tasks, and highlight the key issues, patterns, and examples you observed. Next, you should interpret your findings, explain what they mean for your product or service, and how they relate to your research questions and hypotheses. Finally, you should provide your recommendations, propose solutions or improvements, and outline the next steps or actions to take.

3 Use visuals and stories

One of the best ways to engage your audience and illustrate your findings is to use visuals and stories that show how users interacted with your product or service. Visuals can include screenshots, videos, graphs, charts, or diagrams that demonstrate the user behavior, feedback, or metrics you collected. Stories can include quotes, anecdotes, or scenarios that capture the user experience, emotions, or needs. You should use visuals and stories that are relevant, informative, and persuasive for your audience, and that support your arguments and recommendations. For technical stakeholders, you may want to use more data-driven visuals and stories that show the quantitative and qualitative results of your testing. For non-technical stakeholders, you may want to use more user-centric visuals and stories that show the impact and value of your testing.

4 Explain your rationale and assumptions

Another important aspect of your usability testing presentation is to explain your rationale and assumptions behind your testing process, findings, and recommendations. You should be transparent and honest about the strengths and limitations of your testing, the criteria and methods you used to analyze and interpret your data, and the evidence and logic you used to support your conclusions and suggestions. You should also acknowledge any uncertainties, gaps, or challenges you encountered or anticipate, and how you plan to address them. By explaining your rationale and assumptions, you can build trust and credibility with your audience, and show that you are confident and knowledgeable about your testing.

5 Invite feedback and questions

The last tip for your usability testing presentation is to invite feedback and questions from your audience, and to respond to them respectfully and constructively. Feedback and questions can help you validate, clarify, or improve your testing, findings, and recommendations, and can also reveal new insights, perspectives, or opportunities. You should encourage your audience to share their opinions, concerns, or suggestions, and to ask any questions they may have about your testing. You should also be prepared to answer them clearly, concisely, and politely, and to provide additional information or examples if needed. By inviting feedback and questions, you can show that you value your audience's input and involvement, and that you are open to collaboration and improvement.

6 Here’s what else to consider

This is a space to share examples, stories, or insights that don’t fit into any of the previous sections. What else would you like to add?