Right now in a meeting someone is explaining something genuinely important — and the executive in the room has already mentally moved on. Not because they’re disengaged. Not because the topic doesn’t matter. But because the explanation isn’t speaking their language.
Many technical communicators make the same mistake: they start with the how before why it matters. And in a room of people making high-stakes decisions under time pressure, that’s a costly mistake.
The Assumption That Backfires
Here’s the assumption that gets technical people into trouble: “If I explain it thoroughly, they’ll understand and trust my recommendation.”
This logic might work in a classroom, but it doesn’t work in a boardroom. Executives aren’t evaluating your explanation for accuracy. They’re filtering it for relevance. They’ve sat through enough presentations to know that most of the detail shared won’t change what they need to decide. When your communication gets filtered out before the point lands, thoroughness becomes a liability.
What It’s Costing You
And the ripple effects are bigger than most people realize. When technical explanations run long without a clear payoff, trust quietly erodes. Leaders wonder if the person presenting understands the business — or just the technology. Clarity signals competence. Over-explaining signals the opposite.
If the key takeaway is buried at the end of a dense walk through, executives leave without the confidence to move forward. They table it. They ask for a follow-up. The project stalls — not because anyone said no, but because no one said yes. And eventually, someone else gets pulled in to “translate.” That person may not have the full picture. Now you’ve lost control of your own narrative.
How to Get Through to the Room
The shift isn’t about simplifying what you know. It’s about restructuring how you deliver it. Executives respond to outcome-first communication. Lead with what changed, what’s at risk, or what decision needs to be made. Then offer the detail as backup — available if they want it, don’t force if they don’t. Your technical depth doesn’t disappear. It moves to the appendix, the follow-up, the Q&A.
The leaders who consistently get buy-in at the executive level have figured this out. They’ve stopped proving how much they know and started making it easy for the room to say yes.
Make This Your Default
Before your next executive conversation, run your message through this filter: If this person only remembers one thing from what I’m about to say — what do I want it to be?
Start there. Build backwards. Open with the outcome, follow with the evidence, close with the ask. Every layer of detail you include after that should serve the decision, not the explanation. The goal isn’t to be understood. It’s to make it easy to act.
Notes from Drew
Practical things you can do starting this week:
- Before any executive meeting, write your opening sentence first. It should contain the business impact — not the background. If you can’t write it in one sentence, you’re not ready to present.
- Try the “so what” test on your next deck or brief. After every key point, ask yourself: so what does this mean for the business? If you can’t answer it immediately, that slide or paragraph needs to be reworked.
- Replace your agenda slide with a decision slide. Instead of “here’s what we’ll cover today,” open with “here’s what I need from you by the end of this conversation.” It reorients the whole room from the start.
- When someone asks a follow-up question after your explanation, write it down. The question is a signal that your original communication had a gap. Collect enough of those signals and you’ll start to see the pattern in where your messaging loses people.
- Practice the 90-second version. For any initiative or update you’re managing, be able to explain it clearly in 90 seconds to someone who has zero context. If you can do that, you can handle any executive conversation that comes your way.
