User interviews can reveal why people struggle, what they value, and how they make decisions. But a collection of transcripts and notes is not yet a stakeholder presentation. The challenge is to preserve what participants actually said while making the evidence clear enough to guide a decision.
A useful presentation does more than summarize conversations. It connects a specific business question to patterns in the interviews, shows how those patterns affect users, and makes the next step explicit. The process below helps you build that story without overstating what a small or targeted set of interviews can prove.
Start with the decision the research should inform
Before choosing themes or designing slides, write down the decision your audience needs to make. It might be whether to simplify onboarding, which customer problem to prioritize, or what to investigate in the next research round. A focused question gives you a filter for deciding what belongs in the presentation and what should stay in the research archive.
For example, if stakeholders are deciding whether to change account setup, frame the presentation around where new users encounter friction and what evidence supports a change. Avoid a broad opening such as “Here is everything we learned about users.” If the research was exploratory, say so: its job may be to identify promising questions rather than select a final solution.
Organize notes into themes without losing the evidence
Review interview notes or transcripts and group observations by the user need, behavior, or obstacle they describe. Keep each observation close to its source: note the participant or session, the context, and the supporting passage. This makes it easier to distinguish a recurring pattern from a memorable one-off comment.
Give themes descriptive names that state what participants did or needed, not a conclusion you have not established. “Participants struggled to compare plan limits” is more informative than “Pricing is confusing.” Check each theme against the underlying interviews, including examples that do not fit. If three people raise an issue in a small sample, report that accurately rather than implying it represents all customers.
Separate observations, interpretations, and recommendations
A stakeholder audience needs to know what you heard, what you think it means, and what you recommend doing. Make those layers visible. An observation might be that participants opened a help article while setting up an account. An interpretation could be that the next step was unclear. A recommendation might be to test a more explicit instruction at that point.
Do not present the interpretation as if participants stated it directly. Explain what evidence supports it and where uncertainty remains. If people used the help article for different reasons, that may weaken a single explanation. This distinction helps decision-makers assess the recommendation rather than treating an analyst’s inference as a direct quote or proven cause.
Build a narrative that moves from context to action
A strong flow usually answers four questions in order: What decision is at stake? What did the research show? Why does it matter? What should happen next? This is more useful than presenting one slide per interview or following the order in which conversations took place. Each slide should contribute to the answer, not simply document the research process.
For example, a presentation about account setup could begin with the decision to improve completion, show the point where participants hesitated, explain the effect of that hesitation, and end with a proposed test. Keep the research scope and method visible so the audience can judge the findings in context. A Presentation Storyline Generator can help explore an outline, while a Research Presentation Template can provide a starting structure.
Choose slides that make findings easy to evaluate
Use a clear headline that states the slide’s main point, then provide the evidence needed to assess it. A short quotation can add participants’ language and texture, but pair it with context and an explanation of why it matters. Avoid filling a slide with long transcript excerpts that force stakeholders to search for the insight themselves.
Choose a visual that clarifies the idea: a simple journey for steps in a task, a comparison for differences between user groups, or a small set of labeled themes for a synthesis. If you include counts, explain what was counted and the number of interviews involved. Counts can describe your sample; they should not imply statistical prevalence unless the research design supports that claim.
Make recommendations specific and qualify the limits
Translate each important finding into a practical implication. Instead of “Improve onboarding,” specify the part of the experience to address, the user need involved, and a reasonable next step. For instance: “Test clearer guidance before plan selection because participants paused there to look for information about limits.” The recommendation is tied to observed behavior, yet still leaves room to validate the proposed change.
Include limitations that could change how stakeholders interpret the findings: who was interviewed, which users were not represented, and whether the work was exploratory or evaluative. End with an owner, decision, or follow-up question where possible. If the source material is meeting notes or a transcript, Pekto can turn source content into an editable presentation; review and edit the generated structure and content before sharing. See Meeting Transcript to Presentation AI. For research that combines interviews with questionnaire findings, Survey Results to Presentation AI may also be relevant.
