Dear Bob: What would you say about a consulting project manager who says to a member of his team, “stop talking because what you are saying doesn’t make any sense,” in front of the entire team and the clients on a zoom call?
That’s a remarkable display of incompetence dressed up as authority.
A project manager’s entire job — the whole point of the role — is to manage communication. Shutting someone down in front of clients isn’t decisive leadership, it’s panic wearing a tie. If what the team member was saying genuinely didn’t make sense, the PM had about fifteen options available: redirect the conversation, table the point for later, ask a clarifying question, or simply intervene gracefully. Instead he chose the one option that accomplished nothing useful and several things harmful simultaneously.
What it reveals is insecurity, not competence. Confident managers don’t silence people in public because they aren’t threatened by confusion — they’re paid to resolve it. The public humiliation was the tell. He needed the room to know he was in charge more than he needed the project to go well.
The client dimension makes it worse. Now the clients have seen internal dysfunction up close. They didn’t need to know there was a communication problem on the team. They do now. Whatever credibility the team member lost in that moment, the PM lost more, because the clients just watched him handle pressure by throwing a colleague under the bus.
And the team will remember it. Everyone on that call just learned the same lesson: don’t speak up, because if you say something imperfect you’ll be publicly gutted for it. That’s a chilling effect that will quietly damage every meeting going forward.
Brutal, unnecessary, and — this is the part that should sting — entirely unprofessional by the most basic standards of the job.
A CTO setting that example isn’t just one bad manager having a bad day — he’s demonstrating the culture from the top. Everyone on that call, team and clients alike, just received a live demonstration of how this firm treats people when things get uncomfortable. That’s not a bug, at that level. That’s a feature. That’s who they are.
The technical dimension adds another layer of embarrassment. A CTO is supposed to be the person in the room who can translate confusion into clarity — who can hear something that “doesn’t make sense” and either synthesize it or expose why it doesn’t work through reasoning, not dismissal. That’s the whole intellectual value proposition of the role. What he demonstrated instead is that when confronted with something he couldn’t immediately process, his response was to make it stop rather than understand it. That’s not a technology leader. That’s a man protecting his ego with a title.
And the clients saw it. They’re now doing math in their heads — if this is how he treats his own people in front of us, what happens when we’re the ones saying something he doesn’t want to hear? How does he handle it when the project goes sideways and someone on our side raises a concern? That moment will follow every subsequent client interaction whether he knows it or not.
The team member who was silenced deserves an apology. They almost certainly won’t get one, because the kind of person who does that in public is rarely the kind of person who reflects on it afterward.
If you’re on that team, the most useful thing I can tell you is that this information is valuable. You now know, with complete clarity and zero ambiguity, exactly who you’re working for.
© 2026, Bob Baldwin [1]. All rights reserved.
