What’s the record for the maximum amount of coffee you’ve drank to avoid falling asleep at a meeting? Sometimes I think coffee just exists to keep people alive during a heavy PowerPoint.
Thousands of slides with tiny texts and confusing graphs can suck the life out of your entire team.
In my current company, we never use any presentation tools. No photos, no graphs, and no long texts are prepared to present in a meeting. We consider them a waste of time.
To present our ideas, we prepare simple data Excels (not exceeding one page) with only relevant numbers and cases. You don’t need fancy colors or flying images to express your ideas.
In this article, we will discuss how you can kill your audience with your presentation. You will also learn how to shift your presentation style according to audience and meeting types with real-time examples.
As you can probably guess, “death by PowerPoint” is a term used to describe bad presentations where the presenter ends up losing their audience. You cannot get through more than 50 slides without yawns.
Bored faces stress out the presenter and pressure only makes everything worse. The presenter will start to skip slides.
The problem isn’t PowerPoint itself, but unfortunately people who have a lack of presentation skills always use this tool. Despite the name, the term refers more generally to poorly prepared boring presentations.
If you have too many slides to present it means your presentation will end in a wrong way. You can think of it as a meeting. You aren’t going to discuss every important point in the same meeting.
If you find yourself skipping over slides more than once without mentioning any point, you likely didn’t need those slides in the first place. Skipped slides decrease the importance of the whole presentation.
The slides you skipped took your hours to prepare, but milliseconds to skip. You will start to lose your focus.
As a product manager you should know that every presentation should be rehearsed before the meeting. You should go over every detail and take time to make sure it adheres to the timeline. Remember, the rehearsal will be quicker than the real one.
You need to know where to pause, where to take questions, and when to lead the room.
Complicated pictures, graphs and texts create confusion. Most audiences like to read slides first before the presenter explains.
There are several factors that contribute to death by PowerPoint:
It all starts with this. If your presentations lack a compelling narrative or fail to tell a coherent story you’d better get back to the drawing board.
Without a clear structure or flow, your audience will struggle to follow the main points you are looking to convey and lose interest.
Another common culprit behind death by PowerPoint is the presence of dense, wordy slides that overwhelm the audience.
When slides are overloaded with text, it becomes challenging for the audience to read, comprehend, and retain the information being presented.
Even more than ever before visual appeal is key when conveying a message. When your presentations lack visual appeal you’ll quickly lose the attention of your audience.
Too many bullet points, generic stock images, and cluttered graphics make your slides appear uninteresting and visually unappealing.
Death by PowerPoint can also occur when you simply read the text from your slides verbatim, offering no additional insights or engaging delivery.
This approach fails to capture your audience’s attention, making the presentation feel more like a lecture than an interactive experience.
As a product manager, you have to present things on a daily basis. You present tasks to the development team, developed features to the business team, and metrics to upper management.
I prefer selecting funny images while presenting something to the development team, simple and chic templates for my teammates, and Excel sheets to present management level. Engagement types differ according to who you are presenting to.
Developers do not like to attend meetings, so explaining something to them might bore them. That’s why I prefer images, less texts, and colorful templates to keep them inside the presentation. Most developers will be younger than you too, so adding gifs, funny images, and jokes will be better.
Internal meetings mostly involve sharing knowledge with each other. You don’t need flying images. Instead, rely on good content. The presentation must show them you care about the topic.
My management level meetings mostly use Excel sheets. We don’t have presentations if they’re not required. Our attention stays on numbers and dates.
Try to be sincere and smile. There may be a big bug, or a system failure to present, but you’re the one who will shape the meeting. Your posture and gestures lead the way, so be self-confident.
Alongside this, remember the following:
Featured image source: IconScout
LogRocket identifies friction points in the user experience so you can make informed decisions about product and design changes that must happen to hit your goals.
With LogRocket, you can understand the scope of the issues affecting your product and prioritize the changes that need to be made. LogRocket simplifies workflows by allowing Engineering, Product, UX, and Design teams to work from the same data as you, eliminating any confusion about what needs to be done.
Get your teams on the same page — try LogRocket today.
Dev Ward shares how she’s helped curate the digital experience for the WNBA’s growing fanbase, including redesigning and launching a new app.
From now on, app developers can avoid the 30 percent cut Apple takes from most transactions and opt to process payments on their own.
Rangarakesh Kanchamreddy shares how he helps standardize the product requirements process via templates, context-setting, and collaboration.
Outliers show you where your product is brittle, where your assumptions break, and where your next act might be hiding.
Learn more →
