How great communicators win decisions (even with worse ideas)
Learn the simple shift experienced leaders use to turn every idea into a business win, so your work finally gets the support it deserves.
⚠️ I opened a Black Friday deal. It’s the lowest price I’ve ever offered, and it may not happen again. If you’ve been meaning to dig deeper into the playbooks, now’s the time before it’s gone.
If you’ve been in data long enough, you know the particular kind of tired that comes from explaining a good idea over and over and watching nothing happen.
You sit in a meeting, walk everyone through the problem, lay out the logic, outline the impact, and still end up with a room that hesitates. People stall.
Someone asks a question you already covered. Someone else suggests pushing the decision to another meeting. You leave knowing the idea will probably fade out like the last three did.
It’s not confusion that drains you, but the sense that you’re doing everything right and still going nowhere. You prepare. You think ahead. You anticipate objections. You give people the full truth so they can make the right call. And somehow the decision still doesn’t move.
The part that makes it worse is watching a simpler, weaker idea get approved a few days later. It’s frustrating. It makes you feel invisible. It makes you wonder what you’re missing that everyone else seems to understand.
The answer is rarely the idea itself. It’s the way the decision feels to the people who need to approve it.
Experienced leaders don’t get green lights because they’re the smartest people in the room. They get them because they make the decision feel easy to support.
That’s the shift nobody teaches you early in your career, and once you see it, the whole job starts to feel different.
You’re not losing because your idea is bad
If you’ve been working in data for a while, you know the strange disconnect that happens when you bring a well-thought-out idea to a meeting. You do the prep, you understand the problem, and you know exactly why your approach makes sense.
On a technical level, the solution is sound. On a business level, it solves a real pain. Everything lines up.
Yet the moment you start explaining it, the room slowly drifts away from you.
People nod politely, but their questions go sideways. Someone gets stuck on an irrelevant detail. Someone else suggests parking the decision until there’s “more clarity.”
You can feel your idea slipping, not because anyone disagrees with the logic, but because the whole thing suddenly feels heavier than you expected.
This is where most data engineers unintentionally sabotage themselves. When they sense confusion, they add more detail. When someone hesitates, they respond with even deeper technical context. When the room seems unsure, they expand the explanation instead of tightening it.
The instinct comes from a good place. You want to be thorough. You want people to understand the full picture. You want to avoid surprises later.
But the more information you add, the harder the decision becomes.
It’s not your idea that creates resistance. It’s the weight of evaluating it. Decision-makers aren’t sitting there judging the correctness of your logic. They’re judging the cost of engaging with it.
If an idea requires a long mental climb just to understand, most people will quietly back away, even when the solution is objectively strong.
This is how weaker ideas sometimes get approved while stronger ones stall. It’s not fairness. It’s cognitive load. Someone else frames their idea in a way that feels simple to evaluate, so it moves. You frame yours in a way that feels complex, so it slows down.
None of this means your idea is bad. It means the way you present it unintentionally raises the effort required to support it. And once you understand that, the dynamic in the room starts to make a lot more sense.
The shift leaders make
Evgeni, my manager 8 years ago, told me something that changed the way I see communication forever. He didn’t give me a list of tactics or a script to memorize.
He said, “Watch how the Mitio talks”. I used to spend a lot of time with the director of infra.
And instead of giving me random advice, Evgeni told me to extract all the lessons myself.
If you’re a data engineer, you already sit close to people who get the green lights. Directors, senior managers, leads. You hear how they pitch ideas, how they describe problems, how they ask for support. But you might not study it. You might assume their wins come from authority, experience, or reputation.
Look a bit closer and you’ll see something else.
Experienced leaders talk differently. They don’t drown people in context. They don’t feel the need to explain the entire system. They don’t open ten tabs in the listener’s head. They walk into a room and make their idea feel small, clear, and safe to move forward.
They do three things extremely well.
First, they center the other person immediately. Not with flattery, and not with manipulation. They speak directly to the stakes the other person cares about, not the mechanics they themselves understand best. They start with the business pain, not the architecture diagram.
Second, they frame every conversation as a choice, not a lecture. They narrow the decision instead of expanding the explanation. Two paths, clear tradeoffs, minimal noise. Nothing for the room to decode.
And finally, they recommend one of those paths with confidence. Not arrogance. Not certainty. Just a clear direction. They reduce the cognitive effort required to support them.
When you watch leaders through this lens, something clicks. They aren’t “better at talking.” They aren’t born charismatic. They’ve simply learned how to lower the weight of a decision so someone can pick it up.
This shift is learnable. And once you see it, you’ll notice it everywhere.
Why decision-makers say yes to worse ideas
Once you start paying attention to how leaders frame ideas, another pattern becomes obvious. Decisions rarely hinge on technical depth.
They hinge on how easy the idea is to evaluate. That sounds unfair when you’re the person who actually understands the system, but this is how most organizations operate.
People say yes to the idea that feels lightest.
A “light” idea is one they can understand quickly, explain to someone else without embarrassment, and defend if things go sideways.
It doesn’t overwhelm them. It doesn’t force them to remember five dependencies. It doesn’t create the fear of being blamed for approving something they didn’t fully grasp.
A “heavy” idea does the opposite.
It asks them to track complex logic, imagine multiple outcomes, and trust they interpreted your explanation correctly. None of that has anything to do with the quality of your thinking, but it has everything to do with how safe the decision feels in the moment.
This is why you sometimes watch a simpler, weaker idea move forward while your stronger one dies slowly. It’s not a measure of intelligence. It’s not politics. It’s the psychology of risk.
A decision-maker would rather back an idea they can hold in one hand than one that requires both.
And here’s the part that stings a little: when you over-explain, you unintentionally add weight to your own idea. You make it harder for someone to champion it because they now feel responsible for understanding every detail you just shared.
Meanwhile, the person with the “worse” idea isn’t winning because of talent. They’re winning because they made it easy.
Easy to grasp.
Easy to support.
Easy to move.
Once you see this dynamic clearly, you stop asking, “Why did they approve that?”. You start asking, “How can I make my idea feel this simple to say yes to?”. That’s the real turning point.
How to make your ideas easy to support
This is where the shift becomes practical. If decisions move when they feel light, then your job is to remove weight, not add detail. You don’t need to become a storyteller or a politician. You just need to reframe your ideas in a way that matches how leaders think.
There’s a simple structure that works almost every time:
Start with the business pain.
Not the technical trigger. Not the system diagram. Not the error pattern, latency profile, or column-level issue. Open with the consequence the other person already cares about. “Forecasting is now two days late”. “Customer complaints doubled this week”. “The product team is guessing instead of deciding”. When you start here, the room is aligned before you even share the idea.
Give two viable options
Not five. Not a lecture. Two. One that maintains the status quo and one that moves forward. People make decisions faster when the tradeoff is narrow and obvious. You’re not trying to educate. You’re reducing cognitive load.
Recommend one of those options
This is where most engineers hesitate. Recommendation feels risky. You might be wrong. Someone might disagree. But this step is what makes you sound like a leader. You’re doing the mental work on behalf of the room. You’re saying, “I’ve looked at the paths, and this one gives us the best chance to fix the pain”.
Own the first step
Not the whole project. Just the next move. “If you’re good with this direction, I’ll start by doing X today”. That final piece removes the last bit of friction. It tells the room, “You don’t need to orchestrate this. I’ve got it”.
When you structure your ideas this way, something shifts. Stakeholders stop seeing a complex technical solution. They see a clear path out of a business pain. You’re not asking them to understand the whole system. You’re asking them to choose between two clear outcomes. You’re not giving them work. You’re taking work off their plate.
And that’s when you notice the real change:
People stop hesitating.
People stop delaying.
People stop asking for more context.
Your idea becomes easy to support. Which means it finally moves.
Final thoughts
Most engineers assume leadership is about stronger arguments, cleaner logic, or better slides. But the more time you spend around experienced leaders, the more you notice something quieter.
They aren’t trying to impress anyone. They aren’t trying to prove how much they know. They simply remove weight from the room until the path forward becomes obvious.
That’s the part nobody teaches you early in your career. You learn how to build systems, not how to lower the friction around decisions. You focus on getting the architecture right, not making the choice feel safe enough to support.
It’s natural. It’s how most of us start.
But once you shift your focus from explanation to clarity, from detail to direction, the whole job changes. You stop dragging ideas uphill.
You stop exhausting yourself in meetings. You stop feeling like you’re always one misunderstanding away from another “no.”
Leadership isn’t about talking more. It’s about making progress feel simple.
When your ideas become easier to move than to ignore, people finally follow your lead.
Thanks for reading,
Yordan
PS: Got a minute? Share how this publication helped you. Be a champion.