How Do I Speak Up in Meetings Without Feeling Like I'm Interrupting?

SHOW NOTES:

WorkLife Stories from School of WorkLife Episode: How Do I Speak Up in Meetings Without Feeling Like I'm Interrupting?

How do I speak up in meetings without feeling like I'm interrupting is the question behind every I should have said something on the walk back to your desk. The answer: stop waiting for a gap, and listen for the moment the room needs you. Speaking into a problem the room has already named never feels like interrupting — because it isn't.

Tomasz knew the system better than anyone, and fixed more bad decisions at his desk than he ever prevented in the room. This is the story of the quiet colleague who changed that, and the three stories he found in years of engineering — the architecture he watched fail in silence, the rough sentence that saved a migration, and the reason he protects the people downstream of the code.

RESOURCES MENTIONED

Get the Seat at the Table — Professional Self-Coaching for Strategic Influence Tell the Three Stories That Turn Your Expertise Into a Voice People Listen To

Work With Me: Commissioned learning resources, speaking engagements, and organisational partnerships.

Transcript

Copy

Speaker 0:08

Tomasz was the person who usually knew. He understood the system more deeply than anyone on the team — where it was fragile, what would break, which shortcuts would cost triple later. In meetings, he said almost nothing. He'd watch a decision move toward a choice he knew was wrong — and not say a word. Because to speak, he'd have to cut across someone. And there was never a clean gap. He'd fixed more bad decisions at his desk, after the meeting, than he ever prevented in the room. Welcome to WorkLife Stories from School of WorkLife. I'm Carmel O' Reilly. And today's episode is How Do I Speak Up in Meetings Without Feeling Like I'm Interrupting? — the question behind every I should have said something on the walk back to your desk. This story is about Tomasz. And about a quiet colleague who showed him that the moment before a decision was never a wall — it was a door. The door to the table. The Thing He Didn't Say Tomasz was thirty-five, a software engineer, and the person who usually knew. He understood the system more deeply than anyone else on the team — not just how it worked, but where it was fragile, what would break under load, which shortcuts would cost triple in six months. When something went wrong, people came to his desk. Quietly, one at a time, after the meeting where the decision had already been made. In the meeting itself, he said almost nothing. It wasn't that he had nothing to say. It was the opposite. He'd be sitting there, watching the discussion move toward a choice he knew was wrong, feeling the words build up — and not saying them. Because to say them, he'd have to cut across whoever was talking. He'd have to insert himself. And there was never a clean gap, only a fast-moving conversation between people who seemed comfortable interrupting each other in a way he wasn't. So he'd wait for the right moment. And the right moment never came. The decision would get made, the meeting would end, and an hour later someone would be at his desk saying "hey, quick question about the thing we just agreed" — and he'd explain, quietly, why it wasn't going to work. He'd fixed more bad decisions at his desk, after the fact, than he'd ever prevented in the room. And every one of them was a decision he could have stopped, if he'd only known how to open his mouth at the right time. What He Saw Someone Else Do The person who showed him was not louder than him. That was the part that stayed with Tomasz. A designer on the team — quiet, measured, not a natural performer — was in a meeting heading toward a decision Tomasz could see was shaky. He assumed she'd do what he did: notice, wait for a gap, miss it, explain later. Instead, at the moment someone said "so we're agreed, then, we'll build it this way" — she said, simply: "Before we lock it in — can I tell you what happened the last time I saw us do this? We built something exactly this way on the last project. It worked in the demo and fell apart the week real users touched it, because we'd designed it for the room, not for them. I don't want to watch that happen twice. Can I show you the bit that's worrying me?" That was all. Thirty seconds. Not an interruption, not cutting across anyone — a short, true story, offered at the exact moment the room was about to decide. The room stopped. Turned to her. And changed the decision. Tomasz replayed it for days. She hadn't been braver than him, or quicker, or more senior. She'd done two things he never did. She'd waited, not for a gap, but for the moment the room was about to decide — and instead of asserting that they were wrong, she'd told them a story about a time they’d gotten it wrong, and let them see it for themselves. He'd spent years waiting for a gap in the talking. The opening was never a gap in the talking — it was a moment in the deciding. And the thing that walked through it wasn't an argument. It was a story. Why Speaking Up Feels Like Interrupting Here is the mechanism, and understanding it dissolves most of the fear. Speaking up feels like interrupting when what you're doing is, in a sense, interrupting — when you're pushing into the flow of a conversation with something of your own, competing for airtime, inserting your point into a stream that was going somewhere else. That genuinely is hard to do, and it feels rude because it slightly is. But that is not the only way to speak. A room constantly tells you what it needs. It says we're not sure why this is happening. It states something as settled that you know is wrong. It moves toward a decision. Each of those is not a gap you have to jump into — it's an opening, a moment when the room has a hole in exactly the shape of what you know. When you speak into that opening, you are not interrupting. You are answering. And answering a question the room has just asked — even if it asked it without knowing you had the answer — never feels like interrupting, to you or to them. It feels like the conversation getting what it needed. The shift is from waiting for a chance to insert my point to listening for the moment my knowledge is what the room is missing. One feels like interrupting because it is. The other feels like being useful, because it is. What Tomasz Found He sat down one evening and thought about his own experience — not the systems, for once, but what the years had taught him. He found three stories. A failure. Eighteen months earlier, he'd sat silent while the team committed to an architecture he knew would buckle. He'd seen it clearly. He'd said nothing, because the meeting was moving fast and he couldn't find the gap. It buckled, on schedule, and cost weeks. What made it worse was that nobody blamed him — nobody even knew he'd seen it coming. It taught him the hardest lesson of his career: a problem you spotted and didn't voice is, to everyone else, a problem you didn't spot. A success. The one time he had spoken — haltingly, awkwardly — to stop a database decision he knew was wrong. He hadn't done it smoothly. He'd just said "can I flag something before we commit?" and then explained what he could see. They'd changed course. It saved a migration that would have taken months. What it showed him: he didn't need to be smooth. He needed to be early — before the door closed, not after. A passion. He'd loved systems since he was a boy taking things apart to see how they held together — and what drove him wasn't the cleverness of them. It was that a well-built system quietly protects everyone who depends on it, and a badly built one quietly punishes them, usually the people who had no say in it. That's why he does this work: he's not protecting the code. He's protecting the people downstream of it who'll never know how close it came to failing them. Three stories, none of them technical. All of them the truth about how he works. The Decision He Stopped A few weeks later, a meeting moved toward a choice Tomasz knew was wrong — the kind he'd have let pass, a year before, and fixed at his desk afterwards. He felt the old pull to wait for a gap. He ignored it. And when someone said "okay, let's go with that" — he used the door. "Before we commit — can I show you one thing? I've watched us make this exact call before. Eighteen months ago I could see an architecture wasn't going to hold, and I sat on it because I couldn't find the right moment to say so. It cost us weeks. I'm not going to sit on this one. Can I take two minutes?" The room turned to him. Someone said, "yeah — go." He wasn't louder that day. He was the same engineer, with the same knowledge he'd always had. He'd simply stopped waiting for a gap in the talking, and started listening for the moment the room was about to decide. Within a few months, people had stopped coming to his desk after meetings. They'd started turning to him in them — because the team had learned that the moment before a decision was exactly when they needed to hear from him. How to Speak Up Without Interrupting: What Tomasz's Story Shows Stop waiting for a gap. Listen for the opening. A gap in the talking may never come. But the room constantly signals what it needs — confusion, a wrong assumption, a decision forming. Those are openings, and they're held open for you. Enter on the room's problem, not your point. "Before we commit — can I show you one thing?" answers a decision the room is making. That never feels like interrupting, because it isn't. It's the conversation getting what it needed. Be early, not smooth. Tomasz's success wasn't eloquent. It was in time — before the door closed. A rough sentence at the right moment beats a perfect one after the decision's made. A problem you saw and didn't voice is a problem you didn't spot. However clearly you saw it, if it stayed in your head, you get no credit and the room gets no benefit. Silent foresight helps no one. The story you lead with is the one the moment needs. A room uncertain whether to trust you? The failure you can name. A room about to misread something? The success only you can see. A room deciding what it's all for? Your passion. You carry all three; the moment chooses. You Already Have What the Room Is Missing Years of knowing the system held every story Tomasz needed. He hadn't lacked things worth saying — he'd lacked a way of saying them that didn't feel like forcing his way in. The failure that taught him what silence costs. The success that showed him he only needed to be early. The reason he does this at all. Yours are there in the same way — in every meeting you left thinking I should have said something. CLOSING That's today's story — How Do I Speak Up in Meetings Without Feeling Like I'm Interrupting? And if you want to go deeper, my third Professional Self-Coaching resource — Get the Seat at the Table, for strategic influence — is there when you're ready. All the details and links are in the show notes, or you can find everything at www.schoolofworklife.com. Remember: The moment before a decision isn't a wall you have to break through. It's a door the room opens for you — and leaves open for exactly as long as it takes someone to walk through it. Thank you for listening.