You know the answer.
You’ve solved this problem dozens of times. You’ve spent years becoming the person people come to when something goes wrong.
Then someone asks you a simple question.
And somehow, your answer becomes a five-minute explanation. You start with the background. Then you add some context. Then you explain an exception. Then another exception. Halfway through, you’ve forgotten what the original question was.
The person listening is nodding. But you can tell they’re not really following.
And the frustrating part is that you actually know this better than almost anyone in the room. So why didn’t you sound like it?
Because expertise and explanation are two different skills. And becoming an expert can sometimes make the second one harder.
I have watched this happen inside hiring panels and leadership reviews at Amazon, Accenture, and Acko, more times than I can count. The most technically sound person in the room, asked a direct question, giving the most technically complete answer, and somehow landing less clearly than someone with half their depth.
The expert’s problem is not lack of knowledge
When someone doesn’t understand something, the usual advice is to learn more. Read more. Study more. Get more experience.
But once you’ve become genuinely competent, the problem reverses. You now know too much.
Your brain doesn’t store your expertise as a neat explanation. It stores connections, patterns, exceptions, dependencies, context. You don’t just know what happens. You know why it happens, when it doesn’t, what caused it last time, what could go wrong, and which detail everyone else is likely to miss.
All of that feels relevant, because to you, it is relevant.
So when someone asks why the project got delayed, you don’t simply say the integration took longer than expected. You think about the architecture dependency, the vendor delay, the fact that the vendor delay wouldn’t have mattered if something else hadn’t happened first. And suddenly you’re explaining the entire system.
The listener didn’t ask for the system. They asked for the answer.
You explain from the inside. They listen from the outside.
This is one of the most common communication gaps I see in technical and senior professionals.
You start where your understanding starts. Your audience needs you to start where their understanding needs to start. Those aren’t always the same place.
Imagine you know a city extremely well. Someone visiting asks how to get to the airport. You could explain every road, shortcut, and alternative route you’ve learned over the years. Or you could say, take the highway for twenty minutes, then follow the airport signs.
The second answer doesn’t come from knowing less about the city. It comes from understanding what the traveller actually needed. Good communication doesn’t transfer everything you know. It transfers what the other person needs to know.
This is why smart people sometimes sound uncertain
There’s a second problem that rarely gets named. Overexplaining can make confidence look like uncertainty.
Not because the person is uncertain, but because their explanation carries too many qualifications before it arrives anywhere. I think. Basically. There are a few things. It depends. To give you some context. None of these phrases are inherently bad, but stacked ahead of the actual point, they create a strange effect. The listener starts waiting for you to arrive at your answer, and the longer they wait, the less certain you sound.
Meanwhile, you’re only trying to be accurate. That’s the irony. You’re adding information to demonstrate expertise, and the additional information is what’s making your expertise harder to see.
The person who knows less can sometimes sound smarter
This is uncomfortable, but it’s worth saying plainly.
Sometimes the person with less technical knowledge sounds more intelligent, simply because they know how to compress their thinking. They identify the important thing, give the conclusion, then provide the reasoning, then go deeper only if asked.
That’s why some people can explain a genuinely complicated subject in three minutes while someone else needs twenty. It isn’t that they know more. They know what to leave out. And that is its own form of expertise.
Clarity isn’t simplification
This distinction matters, and it’s the one people get wrong most often.
Good communication doesn’t mean turning a complex idea into something simplistic. You shouldn’t remove important information just to sound clear. You should sequence information intelligently.
There’s a real difference between telling someone everything you know, and telling someone what they need to know first. The first is information transfer. The second is communication. When you’re speaking to a client, an executive, or a leadership team, that distinction carries real weight, because your audience doesn’t need the entire journey your brain took to arrive at the answer. They need to understand where you’ve arrived, and why it matters.
So what should you do instead
Before explaining something, it helps to ask three questions.
What is the actual question, not the subject. If someone asks why a project is delayed, don’t answer with the entire history of the project, answer why it’s delayed.
What is the one thing they need to understand first. Give them that before everything else. You can always add context. You cannot easily recover someone’s attention once you’ve lost it.
What can I leave out. This is the uncomfortable one. Ask whether a detail helps them understand the point, or whether it simply proves you know the subject. If it’s the second, leave it out.
Your expertise doesn’t disappear when you say less
Many experts worry that if they don’t explain everything, people won’t realise how much they know. In practice, the opposite tends to happen.
When you can take something complicated and make it understandable without making it simplistic, people don’t think you left things out. They think you really understand this. That’s the actual difference between displaying knowledge and demonstrating mastery. Anyone can make something sound complicated. Mastery is knowing what matters.
The real communication advantage
The most effective professionals I work with aren’t the ones who speak the most. They’re the ones who can take what’s happening inside their head and give someone else a clear path through it.
They know when to give the conclusion, when to explain the reasoning, when to provide context, and, perhaps most importantly, when to stop. Communication isn’t the act of emptying your brain into someone else’s. It’s the act of helping another person understand what matters. And that takes a skill expertise alone doesn’t give you: judgement about what to say, what not to say, and what needs to come first.
Your expertise is valuable. But people don’t experience your expertise directly. They experience your explanation of it. And sometimes the smartest thing you can say is less than you know.
If this sounds familiar
If you recognised yourself somewhere in this, in the five-minute answer that should have taken thirty seconds, in the moment you watched someone with less depth land the point you actually understood better, that’s not a knowledge problem. It’s a specific, trainable gap between what you know and what you choose to say out loud. It’s the exact gap I work on with senior professionals whose expertise has outgrown their ability to compress it.
Being right and being believed are different skills.
Aryan Khazin
Executive and Strategic Communication Consultant, Khazin
Talk to Aryan.
Not another course. A free, direct conversation about what’s breaking down and what to do about it.
No sales pitch. No prep required.
150+ professionals coached, from senior ICs to executives. Individuals at Amazon, Accenture, Acko, TCS and KPMG. Not the companies. Them.
The gap you just read about does not close on its own. It compounds quietly until someone finally names it.
Start the Conversation