You watch their eyes go at ninety seconds.
You know it completely. That's the problem — you're explaining it in the order you learned it, not the order they need it.
“It's an event-driven pipeline that de-duplicates at ingest and reconciles against the source of truth on a rolling window, so we're not double-counting across regions.”
“Right now two countries can report the same sale twice. This makes sure a sale is only ever counted once.”
The second version isn't dumbed down. It's the same claim with the mechanism removed — and the mechanism was never the thing they were deciding on.
Then the cost: your project gets deprioritised in favour of one that was explained better, and you know that's exactly what happened, and there's no way to say it that doesn't sound bitter.
Simplifying feels like lying by omission to someone whose whole value is precision. That instinct is why you keep losing the room.
Nobody in that meeting is trying to understand your system. They're trying to decide something. Everything that doesn't help them decide is noise, however true it is.
Say it out loud. Get scored 0–100. Hear exactly what to fix — down to the word.
Scroll through. Count how many you recognise.
You're not bad at communicating. You're precise, in a room that's optimising for a decision. Those two things pull in opposite directions and nobody ever teaches you how to hold both.
One session a day. Not a warm-up — the deep end.
They're not deciding whether you're right.
They're deciding whether they followed you. Find out which part they lost.
Practise the plain version — free