Skip to content
All articles

The Silence Tax: When Your Team Stops Raising Problems

14 October 2026 · Tahseen team · 4 minutes to readDownload as PDF
Having no problem is the biggest problem

It is Sunday morning, and the weekly performance review begins. Every indicator on the dashboard is green. Yet on the shop floor, in the call centre and at the service counter, people know about the rework, the workaround and the delay that never make it into the meeting.

Most CI practitioners in the GCC have sat in that room. The data looks fine because the bad news was filtered out before it reached the top. Continuous improvement depends on problems being visible. When people stop raising them, improvement stops too, quietly.

Why people go quiet

1. The messenger gets the blame. If the first question after a problem is raised is "who did this?", people learn fast that silence is safer.

2. Speaking up costs more than staying quiet. A concern can mean extra meetings, an awkward talk with a manager or a mark on an appraisal. Keeping quiet costs nothing today.

3. Nobody knows where problems should go. When reporting channels are unclear or confusing, concerns stay in corridors and WhatsApp groups instead of reaching the people who can act.

Hierarchical workplaces, common across our region, can make all three stronger. Respect for seniority is a strength, but it can make it hard for a junior engineer to tell a director a plan will not work.

A real-world example: Boeing's safety culture review

In February 2024, an expert panel convened by the US Federal Aviation Administration (FAA) published its review of Boeing's safety culture. The panel had been set up after the fatal 737 MAX crashes of 2018 and 2019, and its report landed weeks after a door panel blew out of a new Alaska Airlines 737 MAX 9 in flight on 5 January 2024.

As reported by NBC News and CNN, the panel reviewed thousands of documents and interviewed more than 250 employees. It found a "disconnect" between senior management and other employees, and "hesitation in reporting safety concerns for fear of retaliation." It also found that safety procedures and training were confusing across sites and groups, which, the report said, "may discourage employees from submitting safety concerns." The panel made 27 findings and 53 recommendations.

Two days later, on 28 February 2024, the FAA gave Boeing 90 days to produce a plan to fix its quality problems, according to the Associated Press. FAA Administrator Mike Whitaker said "Boeing must commit to real and profound improvements." Boeing said it had "taken important steps to foster a safety culture that empowers and encourages all employees to share their voice," adding: "there is more work to do."

The lesson for CI leaders is not about aviation. An organisation can have procedures, systems and reporting tools on paper, and still not hear what its people know.

Lessons for CI leaders

1. Watch what happens after someone speaks up. As Mark Graban puts it, the better question is not "Why won't people speak up?" but "What happens when they do?" This week, thank the next person who raises a problem in front of the team, and tell them what will be done about it.

2. Make the path for problems simple and visible. One clear way to raise an issue, one owner and a status everyone can see. If people cannot see what happened to their last concern, they will not raise the next one.

3. Ask about the process, not the person. Replace "who messed up?" with "what in the process allowed this?" Root-cause tools only work when people trust the answer will not be used against them.

How the Tahseen ecosystem tackles it

No platform can create trust on its own; leaders do that. But the right structure makes it much easier for problems to surface and get solved.

• One platform from charter to results. Every CI project in Tahseen has a clear owner, tracked actions and live dashboards. A concern raised by the team is recorded where everyone involved can see it, instead of disappearing in an email chain.

• Project charter workshops. A good charter starts with an honest problem statement backed by facts. Our workshops help teams name the real problem, agree the scope and secure a sponsor before work begins.

• Lean Practitioner training (5 days). Participants practise structured problem-solving that focuses on the process, not on blame: the habit that makes speaking up safe.

• Project coaching. A Tahseen coach works alongside project leaders and sponsors, helping them respond to bad news with questions rather than judgement.

Everything is available in Arabic and English, and built for the way GCC organisations work.

Over to you

In your organisation, what happens to the person who raises a problem first? Share your experience in the comments.

Learn more at tahseen.om

More articles

Is resistance to change the norm? Yes. Here is why.In any change, what do people want from their leader?