The working journal / Leadership & teams
When good employees stop challenging leadership
Silence can look like alignment. What changes when experienced people stop offering their judgment.
One of the things I’ve become more aware of over the years is how easily silence can be mistaken for alignment. When people stop questioning decisions, meetings become easier, initiatives move faster, and leadership can reasonably assume that everyone is moving in the same direction. Sometimes that really does mean the team is aligned. Other times, though, people have simply learned that challenging the direction isn’t worth the effort or the potential consequences.
I’ve seen this happen gradually. Someone raises a concern and gets dismissed. Another person pushes back on a decision and becomes known as difficult. Eventually, experienced people start choosing their battles more carefully, and then they stop choosing them at all. They still do their jobs, participate in meetings, and execute what is asked of them, but a part of the value they once brought to the organization disappears. The company still has their labor, but it no longer has their judgment.
When the question disappears
Consider an illustrative planning meeting. A team has promised a Friday release. An engineer notices that an import can create duplicate records after a retry. The first time they raise it, the response is that the date has already been agreed. At the next meeting, they report their assigned tasks as complete and say nothing about the retry path.
The delivery report has become simpler. The risk has not. The engineer may be discouraged, tired, or convinced that somebody else owns the decision. The silence alone cannot tell us which. It should prompt a conversation, not a conclusion about their attitude.
A useful response separates the technical concern from the deadline: what can fail, how would we notice, and what would make the release acceptable? A repeatable example gives the discussion something more concrete than a contest between optimism and caution.
Make room for a specific answer
I also understand why this is complicated from the leadership side. Constant disagreement can slow teams down, and not every objection deserves to derail a decision. There are also people who confuse being contrarian with being thoughtful. The challenge is being able to distinguish between someone creating unnecessary friction and someone raising an uncomfortable point because they genuinely see a risk that others do not.
A broad invitation to speak up can be hard to use when the leader has already announced a preferred answer. A narrower question is easier to act on: which assumption in this plan is least tested? What would support need to handle on Saturday? What would you change if the date could not move?
In the release example, the options might be to fix the retry behavior, exclude the import from the release, or accept the risk with an explicit recovery plan. Each has a cost. Hearing the objection does not require choosing the engineer's preferred option, but it does require dealing with the problem they identified.
Close the decision loop
After the discussion, write down the concern, the decision, the person responsible, and the condition that would trigger a review. This is a decision record, not a scorecard for who was right. It should be short enough that someone will actually use it.
Then return to the person who raised the issue. Explain what changed or why the team is proceeding anyway. If their concern prevented a problem, credit the contribution. If it was not borne out, resist treating that as a reason to dismiss the next concern. A warning can be reasonable even when the feared outcome does not happen.
Watch what happens in the next planning conversation. Are people offering concrete objections earlier, or only repeating the agreed plan? That is more useful than counting how many people answered yes when asked whether everyone was comfortable.
Listen without demanding a performance
Not everyone thinks best in a crowded meeting. Written review time and a private conversation can reveal concerns that a quick round of comments misses. A quiet person may simply prefer a different way to contribute; they do not need to become the team's public challenger to have their judgment respected.
As I’ve moved further into leadership, I’ve started paying more attention to the people who used to speak up and suddenly don’t. Sometimes the absence of disagreement means you have created clarity. Sometimes it means people have stopped believing their disagreement matters. Those are two very different kinds of silence.
The practical test is what happens after disagreement. Does a concern produce a considered decision and a response, or does it merely make life harder for the person who raised it? The answer shapes whether the next useful question gets asked.
Share this article
Continue the conversation
A question, a different experience, or an idea for the next article? Send Jason a private response.