A short presentation about your work should make it easy for people to understand what you do, why it matters, and what you want them to remember. This guide shows you how to plan, write, design, rehearse, and deliver a presentation that works within a tight time limit.
Start with the purpose
Before opening PowerPoint, Google Slides, Canva, or another presentation tool, define the purpose of the presentation. A presentation for a job interview is different from one for a client meeting, team update, portfolio review, or networking event.
Write one sentence that completes this prompt:
After my presentation, I want the audience to understand ______ and do or think ______.
For example:
- “After my presentation, the client should understand how my design process can improve their website and agree to a discovery call.”
- “After my presentation, my manager should understand the progress of the project and approve the next phase.”
- “After my presentation, a potential employer should understand my strongest skills and the results I have achieved.”
This sentence becomes your filter. If a detail does not help achieve that purpose, remove it or move it to a backup slide.
Also identify your audience. Consider what they already know, what they care about, and how much technical detail they can reasonably follow. A specialist audience may understand industry terms, while a general audience will need plain-language explanations and context.
Choose a simple structure
Short presentations are easier to follow when they have a visible beginning, middle, and end. For most work-related presentations, a five-part structure is enough:
- Who you are and what you do
- The problem, goal, or context
- What you did
- The result or value
- The next step or key takeaway
You can turn this into five to seven slides. A useful rule is to give each slide one job. Do not make a slide responsible for introducing your background, explaining a process, showing data, and asking for a decision all at once.
A short presentation might follow this outline:
| Slide | Main question it answers | Possible content |
|---|---|---|
| 1. Opening | What is this about? | Name, role, topic, one-sentence promise |
| 2. Context | Why does it matter? | Problem, audience, goal, or starting point |
| 3. Approach | What did you do? | Process, decisions, tools, or collaboration |
| 4. Evidence | What changed? | Results, examples, visuals, or feedback |
| 5. Takeaway | What should happen next? | Recommendation, request, or memorable summary |
If you have only two or three minutes, combine the context and approach slides. If you have closer to ten minutes, add one slide for a case study, comparison, or lesson learned rather than adding several background slides.
Write the message before designing slides
Start with a rough script or speaking outline, not a template. Write the main point you want to communicate in ordinary language. Then reduce it until it sounds natural when spoken aloud.
For each slide, write:
- The slide’s main point in one sentence
- Two or three supporting details
- The transition to the next slide
For example:
- Main point: “I simplified the onboarding process so new customers could reach the first useful result sooner.”
- Supporting details: “I reviewed support questions, mapped the existing steps, and tested a shorter sequence.”
- Transition: “That change mattered because the original process created confusion at the first decision point.”
This approach prevents a common problem: slides that contain facts but no clear argument. Your audience should be able to explain why each slide exists.
Use specific language whenever possible. “I helped improve the project” is vague. “I reorganized the project dashboard so the team could see owners, deadlines, and blockers in one place” is easier to understand. If you can share a measurable result, include it, but do not force a number when the work cannot be measured reliably.
Decide what to include about your work
A presentation about your work does not need to include your entire career history or every task you completed. Select examples that support the purpose of the presentation.
Prioritize:
- Work that is most relevant to the audience
- Decisions that show how you think
- Problems that required judgment or creativity
- Outcomes that demonstrate value
- Contributions that clearly belong to you or your team
When describing a project, use a compact version of the situation, action, result pattern:
- Situation: What was happening or what needed to change?
- Action: What did you personally do, and how did you approach it?
- Result: What improved, was learned, delivered, or decided?
Be precise about collaboration. Saying “I did everything” can undermine credibility, while saying “the team delivered it” may hide your contribution. Explain your role honestly: “I created the content system, worked with the developer on implementation, and helped review the final version.”
If the work is confidential, replace sensitive names, figures, or customer information with approved descriptions. You can still explain the challenge, your method, and the type of result without revealing restricted details.
Design slides for quick understanding
A short presentation benefits from restraint. Use a consistent layout, a readable typeface, and enough empty space for the important information to stand out.
Keep these principles in mind:
- Put one clear headline on every slide.
- Use short phrases instead of paragraphs.
- Make body text large enough to read from the back of the room or in a video call window.
- Use contrast between text and background.
- Align elements consistently.
- Limit the number of colors and font styles.
- Use visuals only when they clarify the message.
Your headline should state the point, not merely label the topic. “The onboarding process had three unnecessary decisions” is more useful than “The Problem.” “A simpler sequence reduced confusion” is stronger than “The Solution.”
Use charts carefully. A chart should answer a question, such as “Which option performed better?” or “Where did the delay occur?” Remove decorative gridlines, excessive labels, and unrelated categories. If the audience needs exact figures, add a small source note or provide the figures verbally.
Screenshots can be effective when you annotate them. Add a box, arrow, or short label showing exactly where the audience should look. A full, unmarked screenshot often forces people to search while you are speaking.
Build a clear opening
The first 20 to 30 seconds determine whether the audience understands where you are going. Avoid beginning with a long biography or an apology for the presentation being short.
A strong opening can include:
- A problem the audience recognizes
- A surprising contrast
- A concrete result
- A question that the presentation will answer
- A brief example of the work in use
For example:
“When we began, customers needed four separate steps before they could see a useful result. I redesigned the first-time experience around one clear decision, and today I’ll show the reasoning behind that change.”
Then state the roadmap in one sentence: “I’ll explain the original challenge, the approach I took, and the result we reached.” This gives the audience a mental map without wasting time.
Practice for the time limit
A presentation that is too long is not ready, even if the content is good. Set a timer and practice aloud, because silent reading does not reveal pauses, awkward transitions, or sentences that are difficult to say.
For a five-minute presentation, prepare approximately 550 to 700 spoken words, depending on your pace and pauses. Treat this only as a starting estimate. Visual demonstrations, questions, and technical explanations may require more time.
Practice in three rounds:
- Content round: Check whether the story makes sense and whether every slide supports the purpose.
- Timing round: Measure the full presentation and identify sections that can be shortened.
- Delivery round: Practice eye contact, gestures, emphasis, slide transitions, and your closing sentence.
Do not memorize every word unless the setting requires it. Memorize the opening, the key transition points, important figures, and the final takeaway. Use brief speaker notes containing prompts rather than a full script that encourages you to read.
Prepare a shorter version as well. If someone says you have only two minutes, you should be able to keep the opening, the strongest example, the result, and the next step. This is more reliable than speaking faster through the complete version.
Deliver the presentation clearly
Speak slightly slower than you would in casual conversation. Pause after an important point so people have time to process it. Look at the audience while explaining the idea, then glance at the slide when you need to reference a detail.
Avoid reading text that the audience can already see. Instead, interpret the visual and explain why it matters. If a slide shows a process, describe the decision or insight behind the process rather than reciting every label.
Use verbal signposts to make the structure obvious:
- “The important constraint was…”
- “This led us to change…”
- “The result was…”
- “There are two reasons this worked…”
- “The decision I’m asking for is…”
If you make a mistake, correct it briefly and continue. Do not draw extra attention to a minor wording error. If you lose your place, return to the slide headline and restate its main point.
Your final slide should not simply say “Thank you.” End with the takeaway and the desired next step. For example: “The main lesson is that reducing the first decision made the service easier to use. I recommend applying the same pattern to the account setup flow, and I’m asking for approval to prototype it next week.”
Prepare for questions and technical problems
Expect questions about your choices, evidence, limitations, and next steps. Before presenting, write down the three questions you are most likely to receive and prepare concise answers.
If you do not know an answer, say so plainly and explain how you would find out. A useful response is: “I don’t have that figure with me, but I can verify it from the project report. The related result I can confirm is…” Avoid guessing, especially when discussing budgets, performance, compliance, or customer information.
Create a backup plan for technical issues:
- Export a PDF version of the slides.
- Keep a local copy and, if permitted, an approved cloud copy.
- Test videos, links, fonts, audio, and screen sharing before the meeting.
- Bring printed notes or a one-page outline when appropriate.
- Know how to explain the presentation without an animation or embedded video.
If the screen share fails, continue using the structure and describe the key visual verbally. If a video or demo is unreliable, replace it with screenshots and a short explanation. The presentation should not depend on one fragile technical element.
Review the presentation before using it
Complete a final review with the audience and purpose in mind. Remove anything that is interesting but not useful. Check that the presentation answers these questions:
- Is the purpose clear in the opening?
- Can someone unfamiliar with the project follow the context?
- Is my personal contribution clear?
- Does every slide communicate one main idea?
- Do the examples support the message?
- Are results and limitations presented honestly?
- Is the requested next step specific?
- Can I finish within the time limit?
Ask one person to watch the presentation without interrupting and then summarize what they think your main point was. If their summary differs from your intended message, revise the structure or wording. That feedback is often more valuable than asking whether the slides “look good.”
A successful short presentation is selective, not incomplete. It gives the audience a clear understanding of your work, shows the reasoning and value behind it, and leaves them knowing what should happen next.