Build a speak-up culture: why employees do not report misconduct

Many companies invest time in platform selection, process design and legal alignment, then wonder why the channel is rarely used. The reason is often not the tool. It is the absence of a speak-up culture: the sense that concerns are welcome, handled fairly and do not lead to retaliation.

A functioning whistleblowing system therefore needs more than a reporting channel. It needs a cultural environment in which people can raise concerns without social or professional isolation. That is where the real work often starts after go-live.

Why employees often stay silent

The main barriers are usually psychological, not technical. Employees ask themselves: will I be believed? Will I become the person who causes trouble? What happens if the suspicion turns out to be wrong? What if I am identified anyway? These questions appear even when the channel itself is technically strong.

Such barriers are especially strong in hierarchical organisations, tense teams or companies with little open management communication. In those settings, publishing a link is not enough. The organisation has to show that reports are taken seriously and retaliation is not accepted.

Fear of retaliation remains the biggest blocker

The EU directive and national protection laws focus exactly on this point: people who report in good faith should be protected. In day-to-day company culture, however, abstract legal protection is rarely enough on its own. Employees pay more attention to how leaders talk about mistakes, criticism and uncomfortable information.

If a culture tolerates upward communication only in theory, but discourages real challenge in practice, even a good reporting system will remain underused. That is why speak-up culture is not only a compliance issue. It is a leadership issue.

Trust grows when fairness is visible

Trust increases when the process is understandable. Employees do not need to know every legal detail, but they do need to understand what the channel is for, who can report, how confidentiality works and what kind of feedback they can expect. It also helps when the company makes clear that not every report has to be a dramatic scandal. Raising a concern early can already be valuable.

Organisations strengthen trust when they communicate the channel neither defensively nor alarmistically. A reporting system is not a weapon against the workforce. It is a way to surface problems early and handle them fairly inside the organisation.

The role of managers

Speak-up culture cannot be delegated entirely to the reporting office. Managers shape whether concerns are welcomed or whether silence is rewarded. Leaders who react defensively to criticism undermine the reporting system even when the formal setup is compliant.

That is why launch communication should address leadership directly. Teams need to see that reports are not treated as attacks, but as part of responsible governance. Managers need simple guidance: listen, do not prejudge, redirect to the proper channel and avoid informal retaliation.

Communication after launch

Many companies announce the channel once and then treat the work as finished. That is a mistake. A speak-up culture needs repetition, plain language and concrete examples. Useful tools include short intranet explainers, recurring training references, manager guides and a clear policy template.

The communication should not explain obligations only. It should explain value. A working channel protects people, reduces damage, improves fact-finding and reinforces trust in fair processes.

How you can tell the culture is improving

Not every organisation needs a sudden surge of reports to show progress. Better signals often appear earlier: more questions about the channel, managers actively pointing people to the correct route, better understanding of the system’s purpose and more positive feedback on confidentiality. Culture therefore shows up not only in case numbers, but in the quality of follow-on communication.

How this becomes a durable operating process

At first glance, Build a speak-up culture: why employees do not report misconduct can look like one isolated work package. In practice, it nearly always depends on several connected elements: channels, ownership, privacy, communication, backup coverage, escalation and day-to-day operations. That is why it helps to see the topic as part of a wider operating model rather than as a standalone task.

Many rollouts slow down when operational details are clarified too late. A process may sound convincing in a workshop while still failing in real work because responsibilities remain vague, follow-up questions are not planned properly or launch communication stays too technical. A useful guide on Build a speak-up culture: why employees do not report misconduct should therefore support both understanding and sequencing.

When companies structure the topic well, they gain twice: the rollout becomes easier to explain internally, and the later operation becomes more stable. That is the real difference between a short-term compliance fix and a reporting setup that keeps working over time.

Three questions for the project team and future operators

Before implementation starts, it helps if the project team and the later operating roles answer three practical questions together:

• Which role owns which task in reality? Do not stop at job titles. Clarify who receives cases, who watches deadlines, who decides, who documents and who covers absences.
• Where is the process most likely to break? In some projects the weak point is intake, in others follow-up, documentation or communication. Finding that fragile point early makes it much easier to stabilise the rollout.
• How does the process feel from the reporter’s perspective? Good processes are not designed for internal comfort alone. They should also make it clear to the reporting person what happens next, what information is useful and why the route can be trusted.

Typical mistakes in operational rollouts

Operational topics rarely fail because the theory is missing. They fail because the same practical mistakes keep returning:

• A neat target process with no backup coverage. If one person holds all the knowledge, the process becomes unstable as soon as that person is absent or leaves. Backup design is part of the operating model, not an afterthought.
• Too little connection between tooling and procedure. A platform, template or policy only helps if there is a clear rule for how it is used. Without that translation, the system often loses momentum immediately after launch.
• Launch without follow-through communication. Employees and external groups are far more likely to use a channel when they understand why it exists, what belongs there and how reports are handled. Silence weakens even strong processes.

A pragmatic next-step sequence

To move Build a speak-up culture: why employees do not report misconduct forward internally, companies usually need a workable sequence rather than a giant programme plan:

• Lock the operating model first. Define ownership, backup, permissions, decision logic and interfaces to HR, legal, privacy or management. Without that foundation, later discussions become unnecessarily chaotic.
• Then test the flow in a few realistic scenarios. Simulate intake, follow-up questions and one concrete next measure. This quickly shows whether timing, ownership and documentation really hold up.
• Only then align communication and training. Final website copy, FAQ, launch messages and training materials work best once the real process is stable. That reduces contradictions and improves trust.

What to do now

If you want more use of the system, do not start by rewriting the slogan. Start by improving the cultural environment around it. Review how leadership, communication and confidentiality are perceived today and whether the channel is understood as a genuinely safe route.

• Read the policy template
• See the whistleblowing system
• Read the anonymous reporting guide