ISSUE #110

The small phrases that make strong leaders sound smaller.

"This is probably a dumb question, but…"

You've heard a capable leader open that way in a meeting full of executives. You may have opened that way yourself. Then came a sharp, useful point, delivered by someone who had already told everybody in the room not to take it seriously.

Phrases like that, along with "I might be wrong, but," make you sound smaller than you are. They're also a symptom. The deeper pattern is that many technology leaders, at the exact moment the conversation matters most, either go quiet or apologize their way in.

It almost never comes from a lack of knowledge. You usually know the answer. The hard part is saying it out loud in front of senior people without feeling self-conscious, and doing it before you're completely sure.

Technology leaders are especially wired to wait. We grow up in a world where being precise is the job. Getting a complex system wrong is expensive, so we learn to check before we speak. That habit makes us good engineers and quiet executives.

Consider Evan, who runs data engineering at a mid-size insurer. Ask anyone on his team and they'll tell you he's the sharpest person in the building on how the business actually runs, because he can see it all in the data. In the quarterly business review, he says almost nothing. He's waiting for a technical question that never comes. Twice he had the answer to a problem the executives were circling, and twice someone else said a rougher version of it first.

His manager tried to help. "Speak up more," she told him after one review. Nothing changed, because Evan didn't need permission. He needed a way in.

When the VP role opened, the feedback came back in one line: strong technically, not yet strategic.

Evan isn't missing strategic thinking. He's missing the habit of saying it out loud in that room. Presence is a set of behaviors, and behaviors get built by doing them repeatedly, with something real at stake. Every meeting he sits out quietly makes the next one harder to speak in.

That's the cost, and it compounds. Executives notice who speaks up and who doesn't, and they draw conclusions from the silence. Quiet in a strategy meeting rarely reads as careful. It reads as someone without a view. Over a year, that impression hardens into a label, and the label decides which meetings you're invited to next.

By the time someone tells you you're "not strategic," the label has usually been forming for a long time, built one silent meeting at a time.

There are three moments where technology leaders tend to go quiet, and each one has a different fix.

1. Before the meeting. Most people rush in straight from firefighting, with their head still in the last problem and their nervous system already on high alert. Take two minutes. Sit up, breathe, and ask one question: what matters most to me in this meeting? Then prepare one thing to say. A point of view, or a number you want to explain.

2. When the conversation turns to strategy. You don't need to be the strategy expert. You need a bridge from what you know to what they're discussing. Ask a question ("What's driving the increase in costs?"), share what you see from where you sit ("From the technology side, new-client setup is slowing our deals"), or connect your work to their problem ("The project we proposed would cut that setup time").

3. When you're put on the spot. Pause and breathe. To you it feels endless. To the room it looks like thinking. Clarify what's being asked if you need to. If you don't know the answer, don't guess. Give them a next step instead.

The moment most leaders go quietest is when they disagree with what's being said, especially when it's being said by someone senior.

William Ury, who co-wrote “Getting to Yes”, describes three ways most of us handle that moment: we give in, we attack, or we avoid. Going quiet is avoiding. It feels safe. It also leaves a decision you genuinely think is wrong to be made without your input, and it teaches the room that you don't hold positions. Giving in does the same damage more slowly. Attacking gets you heard once and avoided after that.

The mistake people make when they do speak is telling someone their idea is wrong in the first sentence. The moment you do that, they dig in and defend it.

A better sequence has three parts. Start with what you both want. Say your concern plainly. Then offer another way.

It sounds like this: "I want the same thing you do, which is bringing our costs down and shortening setup time. My concern is the process between product, sales and my team. What if we fix that first?"

You're not fighting their idea. You're giving them a better path to what they already want. Show them you heard them, say what you think plainly, and offer an alternative so you never have to lead with no.

Then drop the softeners. "I might be wrong, but." "This is probably a dumb question." "Just a thought." Each one quietly asks the room to discount you before you've made your point. Say what you mean, once, in a normal, steady voice.

The hardest version of this I ever faced was a billion-dollar bid, when the CEO's chief of staff turned to me in front of a full table and asked for a number I didn't have. I didn't say yes or no. I said we'd go back to the drawing board and come back at the next meeting. That next step bought us the week we needed, and we won the deal. Composure under a question you can't answer yet is a skill, and it can be practiced.

Capable leaders still stall here, for a few predictable reasons.

The first is the way the day is built. Back-to-back meetings, constant firefighting, a coffee in each hand. You can't prepare one clear point when you arrive at every meeting straight from the last emergency. The fix is unglamorous: guard a few minutes before the meetings that matter.

The second is the belief that presence is a personality trait. Some people seem born with it, so if you weren't, why try? That belief keeps a lot of capable leaders quiet for years. Presence is learned. I had to learn it myself, and nobody hands it to you with the promotion.

The third is waiting for a big moment to change. Leaders often hold their first real attempt at speaking up for the high-stakes meeting, where the pressure is highest and the habit is weakest. It works the other way around. Practice in ordinary meetings, where the stakes are low, so that the habit is already there when the big one arrives.

The fourth is assuming silence is neutral. It isn't, to the people watching. Every meeting you sit out says something about you, whether you meant to say anything or not. People fill a silence with their own story about you, and it's rarely the generous one.

None of this requires you to become a different person. You don't need to be the loudest voice in the room, memorize a script, or have an opinion on everything. You need one prepared point, the calm to say it, and enough repetitions that saying it stops feeling like a risk.

Here's a small, practical place to start. Pick one meeting this week. Prepare your thirty seconds. Then say it. Not perfectly. Just clearly.

Then watch what happens the second and third time. People start turning to you when the conversation reaches your area. Someone asks what you think before the decision instead of after. Nobody announces that shift. It just starts happening, and it's usually the first sign that the label is changing.

If you're in rooms where decisions get made and you keep leaving with things unsaid, that's worth working on with someone who has watched this pattern from both sides of the table. In one conversation we'll find where you go quiet, what's driving it, and the one change that will make the biggest difference in your next important meeting. You'll leave knowing exactly what to prepare and what to say.

https://meeting.techleadership.net/

The meeting won't wait for you to be a hundred percent right. Someone else will say a rougher version of what you knew, and the room will remember who said it first.