The One Mistake Killing Your Technical Presentations

Today on Ultimize Discover, you're getting a short practical sample from the Ultimize universe. Use this on its own, take one idea and apply it today, or go deeper at ultimize.com. Ultimize is the world's largest personal development podcast, audiobook, and online learning network. Ultimize. Before you create your next presentation, do this first. Write down your goal in one sentence. Not the topic, not everything you know, the goal. Because if you can't clearly state what you want your audience to understand and to do, there's almost no chance they will. That one step alone will immediately make your presentations clearer and more effective. Hi, you're entering Public Speaking for Engineers produced by Ultimize. I'm your host, TJ Walker. If you're an engineer, you've been trained to value precision, completeness, and depth. That works extremely well when you're building systems. It often fails you when you're trying to explain those systems to other people. The problem isn't that you don't know enough. The problem is you're not designing your communication the way you design everything else, by looking at the results. In this podcast, we're going to treat every presentation as an engineering challenge. This is an objective. There are constraints, there are failure points, and there is a way to design for a successful outcome. We're going to program your brain for one specific result: successful communication where people understand you, remember your message, and act on it. And just like any engineering system, we won't rely on guesswork. You will test your presentations, measure what works, and improve based on real evidence. If you're ready to stop overloading your audience and start delivering clear, effective presentations, then let's begin. This is a limited series podcast, so you don't have to listen once a week for the rest of your life. Just a handful of short episodes. You can binge the entire thing in less than 2 hours and be on your way to being a great presenter. Let's dive in. Before your next presentation, take your most important idea and explain it as if you only had 30 seconds. Not 5 minutes, not 10 minutes, but 30 seconds. Because if you can't explain it simply and quickly, you don't fully understand how to communicate it yet, and your audience definitely won't get it. Engineers deal with complexity. That's your job. You build systems with multiple components, dependencies, constraints, and interactions. You understand how all these things work at a deep level, but when you present, that depth often becomes a problem because you try to transfer that entire understanding to your audience and it doesn't work. You can force and force and push, but it just doesn't work. Your audience does not need to understand everything you know. They need to understand just enough to make the decisions or take the actions you want them to. They just need to know enough to take action, enough to follow your reasoning. This is where most engineers go wrong. They assume that clarity comes from completeness. If I explain everything, give every little detail, people will understand. But clarity doesn't come from more information, more facts, more data dumping. That's not how it works. It comes from better organization and simplification. So let's break down how to explain complex ideas clearly. First, you need to identify the core of the idea. Not all the parts, not all the details, the core. What is the simplest version of what you're trying to explain? If you can't answer that, you're not ready to present, because without that core, everything else becomes noise. Second, you need to sequence your explanation. Most engineers explain things in the order they discover them. That's natural, but it's not effective. Your audience doesn't need to go through your entire thought process. They need a clear path. Start with a high-level idea, then add one layer at a time, only as much as needed, and stop before you lose them. Third, you need to use comparisons and simple language, not because your audience is dumb, but because simple language reduces effort. Use as little jargon, use as few acronyms as possible. And when something requires less effort to understand, people are more likely to stay engaged. Instead of using technical terms immediately, you can say, "Think of it like this," and then give a simple comparison. Once they understand the concept, you can introduce more precise language if needed. Fourth, you need to pause and check understanding, not by asking, "Does this make sense?" because most people will say yes even if it doesn't. They don't want to look stupid. Instead, look for signals. Are people nodding? Are they following along? Are they sleeping? Do their questions indicate understanding or confusing? That's your data, and you use that data to adjust in real time. Now let's connect all of this to testing and evidence. How do you know if you explain something clearly? You don't guess. You test after your presentation. Ask someone, can you explain that back to me? How would you explain what I talked about today to one of your colleagues who didn't make it and was supposed to be here? If they can explain it clearly, you succeeded. If they struggle, not their problem, it's not their fault. You need to simplify further. It's always the speaker's problem if the audience doesn't get it. That's one of the most powerful tests you can run, asking someone in the audience what they actually learned and how they describe it to someone else, because it measures actual understanding, not perceived clarity. And over time, this test will change how you communicate. You'll start to notice patterns. You'll see which explanations work and which don't. You'll learn how much detail is enough. You'll develop a sense for when to stop. That's how you improve, not by adding more, by refining what works. Now let's address a common concern. Engineers often worry that simplifying complex ideas will make them seem less credible. That's not true. In fact, the opposite is true. The ability to explain something clearly is a sign of mastery. If you truly understand something, you can explain it simply. If you can't, it usually means your understanding is still tied to complexity. Your audience doesn't evaluate your intelligence based on how complicated your explanation is. They evaluate it based on how clearly they understood you. Clarity builds trust. Confusion destroys it. Now let's bring this back to the engineering mindset. Think of your explanation as a system. The input is your idea. The process is how you present it. The output is understanding. If the output is not what you want, you don't blame the audience. You improve the process. You simplify. You restructure. You test again. That's how you get better. So from now on, identify the core idea, build your explanation in layers, use simple language and comparisons. Test understanding with real feedback. Because when you do that, something important happens. Your audience starts to follow you. They stay engaged. They understand what matters, and your ideas have a much greater chance of being accepted. In the next episode, we're going to address something many engineers struggle with— confidence and how to present effectively, even if you don't feel like a natural speaker. Before your next presentation to a non-technical audience, do this: remove all technical jargon from your opening 60 seconds. Not reduce it, remove it completely. Because if your audience doesn't understand you at the beginning, they will not catch up later. And most engineers lose their audience in the first minute. Engineers are used to speaking with other engineers. Shared language, shared assumptions, shared context, shared acronyms and shared buzzwords. That makes communication efficient. But when you present to non-technical people, executives, clients, stakeholders, that shared context disappears. And if you don't adjust, your message gets lost immediately. This is one of the biggest gaps in engineering communication. The assumption that what makes sense to you will make sense to everyone else. It won't. Non-technical audiences process information differently. They're not looking for depth first. They're looking for relevance. They want to know, why does this matter? Why does it matter to me? What the impact is, what decisions need to be made from this. If you don't answer those questions quickly, they disengage. So here's the shift. When you present to a non-technical audience, your job is not to explain the whole system. Your job is to explain the outcome. Start with what's happening, then why does it matter? Then, what should we do? That's the structure, not how it works. That comes later if needed. Now let's talk about language. Engineers often rely on precise technical terms, and those terms are accurate, but they're not always useful. If your audience doesn't understand the technology, they cannot follow your explanation. So you need to translate, not by dumbing things down, but by making them accessible. For example, instead of saying, "We're expecting latency due to increased load on the system," you might say, "The system is slowing down because more people are using it than it was designed to handle." Same idea, more accessible. And once your audience understands the concept, you can introduce more precise language if necessary. Now let's connect this to testing and evidence. How do you know if your message is accessible? You test it after your presentation. Ask someone, what was the takeaway? If they can explain it in simple terms, you succeeded. If they repeat your technical language without understanding it, you fail. Because your goal is not to transfer terminology, it's to transfer understanding. You can also test this before your presentation. Explain your idea to someone outside your field. If they understand it quickly, you're on the right track. If they don't, you need to simplify. That's a powerful test because it reflects reality. Now let's address a concern. Engineers often worry that simplifying for a non-technical audience will make them seem less credible. But credibility does not come from complexity. It comes from clarity. If executives understand you, they trust you. If they don't understand you, they question you, even if your analysis is correct. So clarity is not a trade-off, it's an advantage. Now let's talk about structure again. With non-technical audiences, structure becomes even more important because they don't have the background to fill in all the gaps. So you need to guide them. Start with the outcome, then give 2 or 3 reasons, at most a handful. Then stop. If they need more detail, they'll ask. And when they ask, you can provide it by giving more examples, more case studies, things they can visualize. But you don't start there. You start with what matters to them. Now let's bring this back to the engineering mindset. Your presentation is still a system. The input is your message. The process is how you translate and structure it. The outcome is understanding and action. If the output is not what you want, you adjust the process. You simplify the language, you change the structure, you test again, you improve based on results. That's how you get better. Not by assuming your audience should understand you, by designing your communication so they can. So from now on, remove jargon from your opening. Lead with outcomes, not mechanics. Translate technical ideas into simple language. Test understanding with real people. Because when you do that, something important happens. Your audience stays with you. They understand what you're saying. They see why it matters, and they're much more likely to support your ideas. In the next episode, we're going to build on this and focus on persuasion. How to make your ideas not just understood, accepted. By the way, quick question for you. Have you ever noticed how easy it is to consume content and how hard it is to actually do anything with it? I mean, you can listen to 100 episodes, read 10 books, and your habits are exactly the same. That's the gap most people never close. So if you're listening to this and thinking, yeah, I want to actually improve, go to ultimize.com. We've got free courses there for you, either on communication skills or building better habits, and it's designed to get you to actually use what you're learning, not just hear it once. No cost, no catch. Just go to ultimize.com and start. Ultimize.