High stakes, low structure
Why important meetings fall apart, and how it keeps data engineers stuck, small, and sidelined.
I’m running a live workshop next week on stakeholder mapping with the RACI method.
Join as a member to unlock this and every workshop (recordings included) for the next 12 months.
Subscribe here
There was a VP in the meeting. The project was behind. Engineering had escalated. The project was late. The board wanted answers. This meeting was supposed to be the turning point.
Except no one led it.
There was no agenda. No channel. No thread. No clarity on what we were even deciding. Just a Zoom room full of muted faces and an unspoken hope that someone else would take the wheel.
The VP tried. She started asking questions. One by one. And every single time, someone replied with some version of:
Sorry, I was doing something else. Can you repeat?
You could see her face change. First surprise. Then frustration. Then something worse, resignation.
She told people to be more attentive. Asked us to focus. But it was already too late. The culture had been like this for months. Maybe longer. People tuned out because nothing in that meeting told them to tune in.
There was no owner. So no one owned it. There was no plan. So decisions got made off vibes and guesses. There was no record. So by the next day, everyone remembered a different story.
And I watched it all happen, thinking, “This is the call that decides if we ship or if we slip again”.
And we just… slipped.
No structure means no signal
Have you ever walked into a meeting thinking, “What the hell is this for”? Yeah. Same.
There’s no agenda. No one owns the doc. Half the people don’t even know why they’re there. And suddenly, it’s on you to sound smart, look prepared, and drive clarity in a call nobody bothered to set up right.
It’s chaos dressed like collaboration.
And if you’re the data person, it’s worse. You bring context. You know where the bodies are buried. But none of that matters if the call doesn’t give you the air to speak or the frame to land your points.
So you sit quiet.
Or you try to speak, but it comes out messy. No one follows. People start talking over each other. Then someone high up jumps in and redirects the whole thing. And now the clock’s dead and your input’s gone.
You don’t look senior. You don’t look clear. You don’t look like someone to trust next time.
But it’s not because you suck. It’s because the meeting did.
Context dies, and rework shows up
The meeting ends. Everyone says thanks. Then comes the worst part, nobody remembers the same thing.
One person thinks we agreed to Option A. Another thinks we’re pausing. Someone already told their manager it’s shipping Friday.
There’s no doc. No thread. No line that says: “Here’s what we decided. Here’s who’s doing it. Here’s when it’s due.”
So the next week, the team builds the wrong thing. The stakeholders review the wrong thing. And then they ask why we didn’t do the thing they never actually agreed on.
It’s rework. It’s frustration. And it triggers more “alignment” meetings just to fix what could’ve been handled in two clear sentences.
This is how quarters slip. Not from bad code or bad hires. From meetings with no memory.
Silence is a trap
When a meeting has no structure, most people go quiet. Not because they don’t care. Not because they don’t have ideas. They’re just waiting for someone else to lead.
So, the loudest person takes over.
They throw out some half-baked vision. Start assigning “next steps”. Make assumptions no one challenges. And now the team’s scoped into work they never agreed to, solving problems that don’t exist.
The smart folks stay muted. The room moves fast. And bad decisions get locked in because no one wants to be the one who says, “Wait, why are we doing this?”
Silence isn’t neutral. It’s compounding damage.
And it happens every time there’s no prep, no owner, and no clear decision to make.
Your impact can’t show up without a frame
You can do everything right.
Understand the business. Know the data. Show up to the meeting with real context and solid ideas. But if the meeting’s a mess, none of it lands.
You drop a key insight, and it gets buried under someone’s brainstorm. You ask a question, and they skip it to “circle back”. You flag a risk, and it dies in the noise.
And when things go sideways, no one remembers you spoke up at all. This is what keeps good engineers stuck.
You’re doing high-value work, but there’s no frame to show it. No structure to surface it. So you keep playing support when you should be leading.
You don’t grow. You don’t get pulled in earlier. You don’t get trusted with more.
Not because you’re not capable. Because you’re invisible inside the chaos.
Final thoughts
You tell yourself
This is just how it is. I’m the data person. I show up. I support. I wait for direction.
You think you’re being helpful. Flexible. Low ego. But you’re not helping. You’re disappearing.
The project moves without you. Decisions happen without you. And when it all falls apart, they don’t remember that you sat in every meeting. They remember that no one stepped up.
You’re not supposed to lead every call.
But when the stakes are high and the structure is missing, don’t wait for permission. Ask the question. Name the gap. Bring the spine.
If the room has no frame, your work has no shot.
Next week, I’ll share exactly how I structure high-stakes meetings, without looking cocky, stepping on my manager’s toes, or playing politics. It’s not magic. It’s a better way to show up when it counts.
Thanks for reading,
Yordan
PS: If this hit a little too close to home, good. That means you’re ready for more.
This is the stuff I help with, turning your technical skill into real leverage in the room, in the roadmap, and in your role.