How to Present to Non-Technical Audiences | Episode 7

Ultimize. 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 failed. 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 or 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 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. You know, there's one thing I always find interesting. People will listen to a podcast like this, get ideas, maybe even feel a little motivated, and then just move on with their day. Nothing actually changes. And I get it. Information alone doesn't do it. Repetition does. That's actually why we built Ultimize. So if you're getting any value from this, just go to ultimize.com. That's spelled ultimize.com. There's a free course waiting for you there. You can start with communication skills, but the whole idea is simple. Don't just hear something once, actually build it into your life. Again, it's free. Go to ultimize.com.