Discernment: When To Speak Up At Work
For years I believed that agreeing was the professional move. That the reliable, well-liked, "team player" thing to do was to swallow the concerns and make the plan work through sheer effort. Most managers I have worked with (minus two — you know who you are) rewarded the ‘yes sir, yes ma’am no questions asked’ culture and not-so-quietly resented the pushback. I quickly learned to keep my doubts to myself and my calendar full.
It’s something I still battle with today. Especially as someone who runs a business myself, I struggle to understand what I should call attention to in the corporate world versus where I should just stay in my lane.
Here's what I’ve learned throughout experiences… the skill isn't having opinions. Everyone has opinions. The skill is discernment: the expertise comes from knowing when to stay quiet and when to speak up. Some things require you to speak up and advocate for your team, your bandwidth or even your values. And other times, it is not worth your time or energy to go against the grain.
Knowing the difference is what we're exploring today.
What is discernment at work? It's the repeated judgment call of deciding which concerns to raise and which to release — so that when you do speak up, people listen, because you've earned a reputation for only spending your voice on things that matter.
The people who get labeled "difficult" aren't the ones who disagree. They're the ones who disagree about everything, so no one can tell the real alarm from the background noise. And the people who get labeled "not ready for more" are often the opposite - so agreeable that leadership genuinely doesn't know what they think. Discernment is how you avoid both traps.
So before you decide to speak up or let it go, run the concern through four questions.
1. Is this about the outcome or my ego?
Be honest about which one is talking. There's a real difference between "this timeline will cause us to miss the client deadline" and "I would have sequenced this differently." The first is a risk to the work. The second is a preference. Spend your voice on risks to the outcome, the team, or a value you're not willing to trade — not on the fact that you'd have done it your way.
2. Is this my concern to raise?
Proximity earns you a voice. If you own the deliverable, sit closest to the client, or will personally absorb the fallout, you have standing. If you're weighing in on a decision three lanes over because you have a hunch, you're spending credibility you'll want later. Ask: am I closest to this, or just loudest about it?
3. Can my input still change anything?
Timing is leverage. Raising a concern while the decision is still forming can redirect it. Raising the same concern after it's been announced, resourced, and communicated to the client mostly reads as relitigating. If the window is open, move. If it's closed, note it for next time and let it go.
4. What does silence actually cost?
Name the concrete cost, not the discomfort. "I'm uncomfortable pushing back" is a feeling. "If I stay quiet, we ship a number I know is wrong and I'm the one who saw it" is a cost. When the cost of silence is real and downstream, that's your signal — speak up, even when it's awkward.
If a concern clears all four, it's worth raising. Here's how to raise it without torching the relationship using three scripts:
When a new plan lands in a meeting and you see a crack:
"Before we lock this in — can I flag one observation? I want this to perform well, and I think [X] could be challenging for us on the client deadline. Could we pressure-test that piece before we commit?"
When you get a Slack instruction you disagree with:
"Got it, happy to run with this. One thing before I do: I'm seeing [specific risk]. Want me to proceed as-is, or take 10 minutes to walk through the tradeoff first? Your call either way."
When you already said yes and realized you shouldn't have:
"I've been sitting with [project] since we talked, and I want to flag something I missed in the moment. I don't think [X] holds up, and I'd rather raise it now than after we're further in. Can we revisit?"
Notice what these have in common. Each one opens with warmth and buy-in ("happy to run with this," "I want this to land well"), names one specific concern, and hands the decision back. That's not softness — it's discernment made audible. You're signaling that you're on the same team and that you only interrupt for things that matter.
If you're the manager on the other side of this: the way you receive pushback determines how much discernment you ever get. If you punish the person who flags a real risk, you don't get fewer objections — you get a team that's learned to stay quiet and full-calendared, exactly like I did. Reward the good flag, even when it's inconvenient, and you train people to bring you the ones worth hearing.
Discernment isn't about staying silent to seem easy, and it isn't about pushing back to seem sharp. It's knowing which of your concerns has earned the right to be spoken — and trusting yourself to tell the difference.
Your reputation is built in the moments when you communicate clearly. Choosing those moments well is the whole skill.
Want your team to build this muscle together? Book a Career Civility workshop or keynote — discernment and productive disagreement is one of our most-requested sessions.
