When preparing a 10-minute presentation, first identify what decision or understanding should emerge by the end of the meeting. This timeframe is best used to explain a single recommendation alongside its context and evidence; it is not meant to force every detail into the talk. Plan the speaking portion and the Q&A allowance separately. Next, write down the specific question each slide answers and eliminate unnecessary repetition. AI can help you experiment with this sequence, but only an actual rehearsal will verify your timing.
Note your audience's starting knowledge
In an internal team project review, everyone might already understand the core problem. A prospective client you are meeting for the first time, however, needs brief context to grasp the same recommendation. This distinction determines how much of your ten minutes you should allocate to background. List three things the audience already knows and three things they need to learn during the meeting. If your draft lingers on what they already know while rushing through what they need, adjust the order.
Build a sample time breakdown
For a product improvement proposal, you might test a breakdown of one minute for the opening and purpose, two minutes for the current problem, two minutes for available evidence, two minutes for the proposed solution, one minute for prerequisites, one minute for the requested decision, and one minute of buffer for transitions. That totals ten minutes; this example does not include a separate, extended Q&A block. If questions are included in the time limit, trim the evidence or background section. Leaving technical details for supplementary materials can keep the narrative much easier to follow.
Give each slide a distinct role
A sample flow might consist of purpose, current status, the focal issue, two evidence slides, the recommendation, implementation prerequisites, and next steps. Each slide’s title should state its takeaway. A headline like “Request ownership remains ambiguous in the initial stage” rather than “Findings” makes the direction of the talk visible. If you lack observations to support that headline, use a narrower statement. You can find an additional approach to ordering decisions and evidence in the executive summary presentations guide.
Lock down scope and sources in your AI draft
Sample prompt: “Plan a ten-minute product improvement presentation. The audience consists of support and product teams. The goal is to secure approval for a small pilot that defines request ownership. Use the following observations; do not invent new metrics. Across an eight-slide proposal, separate each slide's key takeaway, supporting evidence, and speaker notes. Do not hide implementation prerequisites.”
If the draft scatters across multiple core proposals, decide first which one belongs in this meeting. When needed, have the AI rewrite just a single section. The AI presentation editing guide explains how to make revisions without regenerating the entire file.
Allow time to explain visuals
Adding a chart or diagram does not just increase slide count; it also requires time for the audience to interpret the visual. Explain first what the visual compares, then point out which takeaway matters. Instead of rushing through numerous data series, pick the comparison that actively supports the recommendation. You can move the detailed table to a pre-read document. If the visual suggests a different conclusion without the speaker’s spoken explanation, reevaluate the labels and annotations.
Make your final cuts based on rehearsal results
During your first rehearsal, record how much time you actually spend on each section. Cutting only the closing when running overtime can leave the desired decision ambiguous. Identify redundant explanations or secondary examples within the section that runs long. Know exactly where your backup slides live if questions arise. By applying the evidence-focused approach described in the guide to preparing for presentation Q&A, you can prepare for the meeting without overloading your main narrative with every potential question.
← Back to blog
