Why employees stop telling the CEO what is going wrong
Employees may stop raising problems when they expect speaking up to bring costs or no useful response. Examine what happened after recent warnings before interpreting silence as agreement. Repair the response process, make escalation practical, and show people how a concern reaches a decision without promising that every suggestion will be accepted.
Employee silence is the withholding of work-related concerns, suggestions, or useful information from people in higher organizational positions, following Elizabeth Morrison’s 2014 review of employee voice and silence. Silence is different from having nothing to add. You cannot distinguish the two from a quiet meeting alone. You need evidence about what people knew, where they could raise it, and what response they expected.
Morrison and Frances Milliken’s account of organizational silence describes the expectation that speaking up can bring negative consequences or make no difference. Treat that mechanism as a hypothesis to investigate in your company, not a diagnosis of every employee who declines an invitation to comment.
Notice where the candor moved
Consider this composite. You are at home after the quarterly review. The meeting was calm, the slides were clean, and no one challenged the plan. While you put away your laptop, a former colleague sends a personal message asking whether you know the implementation team has stopped believing the schedule. You spend the next hour scrolling through meeting notes instead of joining a family conversation. The warning was apparently available to everyone except the person responsible for the decision.
Do not begin by demanding to know who spoke outside the meeting. First ask whether the operating concern is real. If it is, establish why the formal route failed. A hunt for the messenger can leave the delivery issue unresolved and teach a further lesson about what happens when difficult information reaches you.
A recognition scene like this is a composite, not a report about a client or a claim about prevalence. Its purpose is to make the sequence inspectable: a quiet formal forum, an informal warning, and a decision about how you will respond. Examine your response before instructing people to trust your intentions.
Run the recent-warning audit
Use this proposed diagnostic to review a small set of actual warning events. Do not score employees’ personalities. Record the warning, the route used, and the observable consequence. Keep private employment information in the appropriate restricted process.
1. Choose events rather than reputations
Select recent occasions when someone raised a concern about an estimate, a customer obligation, a quality issue, or an executive proposal. Include a warning you considered useful and one you rejected. Avoid selecting only the people already known as difficult. A balanced event set gives you something more concrete than a general claim that the culture is open or closed.
For each event, write the concern in the words recorded at the time. If there is no record, identify that limitation. Do not reconstruct an exact quotation from memory. Ask the people involved to correct your summary, and distinguish the fact that a warning occurred from whether its prediction later proved accurate.
2. Map the immediate response
Record what the recipient did next. Did they ask a clarifying question, dismiss the concern, request evidence, change the subject, or criticize the way it was raised? Establish the context before interpreting the act. A request for evidence may be reasonable; it can also become an impossible hurdle when applied selectively.
Ask whether the recipient had authority to act. A well-intended manager may have acknowledged the problem while lacking a route to the owner. If so, the missing step is an escalation design issue. Do not make an employee repeatedly present the same warning to people who cannot decide what happens next.
3. Trace the practical consequence
Look beyond the conversation itself. Check whether the person received a decision, lost access to relevant work, was repeatedly described as negative, or faced additional demands that were not applied to others. Do not infer retaliation from a change in assignment without examining its basis. Potential retaliation or other employment concerns require the appropriate people process and employment counsel.
Also examine the consequence of raising an inconvenient issue that turned out to be wrong. If your response treated an honest uncertainty as misconduct, distinguish that from knowingly misleading others. People need a way to raise a plausible risk before it has become a verified failure. Define the evidence expected for that type of escalation.
4. Find where the loop ended
Identify whether the warning produced a named decision owner, a response, and a record of the next action. If the issue disappeared into an inbox, find out who thought someone else was handling it. Ask the originator what response they understood they would receive. An acknowledgement is not the same as a decision.
A rejected suggestion still needs a proportionate answer. Explain the decision, the evidence used, and any condition that would reopen it. Do not promise lengthy reviews for every comment. Set a response standard that the organization can sustain, and distinguish an urgent risk from a routine improvement proposal.
5. Ask what an observer could have learned
Imagine a colleague who witnessed the event but did not know your private intentions. What behaviour appeared useful, costly, or futile? Keep the answer tied to what was visible. You may have discussed the issue constructively in private while the public dismissal remained the only event the rest of the team saw.
This does not mean you should disclose private corrections. You can explain that a concern was reviewed, what operating decision followed, and how similar issues should be raised. Preserve personal details while correcting an inaccurate public impression about whether the information was taken seriously.
6. Repair one response route and test it
Choose a route you can improve now: the project escalation, the executive meeting, the manager conversation, or the protected reporting process. Define its purpose, owner, and next step. Tell employees what belongs there and what information they should provide. Do not collapse safeguarding, employment complaints, and ordinary project feedback into one informal CEO inbox.
Test the route with a hypothetical concern. Ask who receives it when the usual owner is absent. Check whether the person raising the issue can learn its status without pursuing senior leaders repeatedly. Then inspect the next real event. The change is useful only if the route works beyond the announcement.
Look for patterns without turning them into proof
A meeting where everyone agrees, a leader who always presents good news, and a rise in private messages may be reasons to investigate. None independently proves a silence problem. Workload, meeting purpose, communication style, or incomplete information can produce similar observations. Specify the question each sign raises rather than declaring its meaning.
For example, a consistently green project report should prompt you to compare the report with unresolved dependencies and actual delivery checks. Ask what threshold changes the status and who can challenge it. If the report has no usable category for uncertainty, repair the reporting method before accusing someone of concealing a risk.
A new employee who asks many questions and later stops also gives you a question, not a conclusion. Ask what has become clearer and what is still difficult to raise. Do not demand a confession of distrust. Make it possible to discuss a reporting obstacle without having to criticize an individual executive in front of that executive.
Change your invitation to speak
“Any questions?” at the end of a settled presentation may not provide enough structure for a consequential concern. Ask for a specific category of missing information before you finalize the decision. Give people a route to contribute before the meeting when the matter requires preparation or restricted handling.
A proposed invitation is: “Before we approve this schedule, tell me which dependency lacks an owner or which acceptance condition we have not met. You can send the evidence to the project owner before the review. We will record the unresolved items and identify who decides them.” That wording asks for useful information without requiring an employee to dramatize disagreement.
Edmondson’s research on psychological safety connects interpersonal risk with team learning. Do not treat an invitation as proof that risk has disappeared. Inspect what happens after an awkward question, including when you are tired or the information threatens a plan you supported. The response is the part of the process you can examine and change.
Use a script that does not demand reassurance
Try: “I am concerned that some relevant information reaches us late. I want to examine the route and our response, including my own. Tell me about a recent concern, where you raised it, and what happened next. You do not need to tell me that our culture is good or bad. We need an event we can understand.”
When an employee declines to discuss a matter with you, offer the appropriate alternative. Respect formal reporting and confidentiality limits. Do not guarantee anonymity in a conversation where identity or details may become apparent. If a concern involves your own conduct, use a process with suitable independence rather than appointing yourself its only judge.
The wider trust and conflict playbook helps separate operating disputes from relationship assumptions. Use meeting facilitation when the forum itself blocks useful information. If you reacted badly to an earlier warning, make a specific leadership apology and name the response you will change.
Review the next few events
Keep a short record of concerns received, response ownership, and unresolved actions. Do not rank employees by how often they challenge leadership. A numerical target for speaking up can invite low-value objections while important information remains difficult to raise.
Compare the record with actual work. Are critical dependencies reaching the owner before commitment? Can people identify where an unresolved issue went? Do rejected concerns receive a usable answer? Preserve uncertainty where your evidence is thin. A successful review produces a more reliable information path, not a claim that everyone now feels safe.
Finish by closing an overdue loop. Tell the relevant people what decision was made, which limitation remains, and who owns the next action. Let the next response demonstrate the change before asking employees to believe a new statement about openness.