Mercer International

How Organizations Build Silos, Who Gets Hurt, and What HR and Communications Must Own

Communication failures kill in manufacturing.

Undocumented processes create catastrophic errors. Lockout/tagout procedures exist because equipment that is not properly de-energized will kill the person working on it. Whenever a critical incident occurs, regulators do not ask if your culture was collaborative. They ask what was communicated, to whom, when, and if you can provide it. Organizations without defensible records are those that cannot answer that question.

Information flow in industrial environments is not just an engagement problem. It is a safety system. When that system is fragmented by silos, the consequences do not show up in your culture survey first. They show up in incident reports.

This is not a peripheral concern. It is the central issue. Silos are not just an organizational efficiency problem. In any workplace that carries physical risk, they are a lifesafety problem. We are often the architects of how they form.

We Built This, and Then We Automated It

Organization charts establish hierarchy. Performance systems reward departmental success. We establish belonging within teams, which is genuinely valuable, and thereby create distance between them.

We then buy technology that replicates the same architecture.

In most industrial organizations, technology is not always chosen by HR. Organizations rely on many of the systems they use for people management not because they are HR-related. Their accounting architecture was purchased for SAP, Oracle, Workday, and others, and they were extended to HR because the module had already been purchased. The system that tracks your workforce, training records, and safety certifications was designed primarily to reconcile ledgers. That is not a neutral foundation for a communication infrastructure.

In the end, the platform is based on financial control, not human behavior. The system tracks. It records. It reports. However, it was never designed to deliver verified, current information to the right person on a plant floor at the right time. Technology hasn’t solved the silo problem when a verified SOP and an outdated SOP exist simultaneously in different parts of the same system and no governance model ensures workers find the right one. It’s digitized.

When Does Data Become the Silo?

Today, organizations are chasing efficiency more than ever, but are achieving less of it because the volume of data generated has outpaced the ability of humans to handle it.

Data, dashboards, and reports are drowning leaders at every level. They sit unread, because the people who are supposed to use them are already overloaded, managing the demands of an organization that confuses data collection with organizational intelligence.

“ Silos are not just an organizational efficiency problem. In any workplace that carries physical risk, they are a life-safety problem. “

On the floor, something more damaging is happening.

In place of being with their crew, the supervisor becomes a data administrator. The person whose experience and judgment are the actual safety system, who recognizes hesitancy, catches near misses before they become incidents, and imparts knowledge through presence, relationships, and mentorship, has been pulled away from that work to populate fields in a system that three levels of leadership above them cannot open in time.

Keyboards have been given to those closest to the risk.

Engagement loss, mentoring loss, and erosion of informal knowledge transfer are real problems in industrial workplaces. They are driven, in part, by HR and operations technology that was sold as a solution to these issues.

Data has become the silo. And that silo is costing organizations not just efficiency, but the human connection that fosters safety culture.

What Deconstruction Actually Requires

The process of deconstructing silos is slow, difficult, and politically uncomfortable.

Start with a forensic diagnostic. Trace specific recent incidents backward. Ask: Who was involved? What happened? Where did the process break? Incident investigations already do this in safety-critical environments. Findings should drive structural change or retrain employees who failed. Human resources and communications must be included.

Map all your workforce management, communication, and tracking systems. Ask who chose them, why they were purchased, and whether the users find them useful or burdensome. In most cases, that last question is instructive. Frontline workers experience administrative overhead because reporting systems are not optimal.

Those supervisors, whose knowledge, mentoring, and trust cannot be replicated by a platform, should return to their actual tasks in the absence of data entry and system administration. They are the safety system between a written procedure and worker action.

It is not a structure, a cross-functional task force, or a new platform. In order to communicate safety-critically, people need to understand why procedures exist, who wrote them, and what happens when they aren’t followed. Systems don’t provide this understanding. The frontline leaders must be present enough to build it through relationships across functional lines.

The Role HR and Communications Must Own

Traditionally, HR and communications have been seen as support functions: helpful, facilitative, responsive. That’s insufficient in industrial environments, and frankly, it’s insufficient anywhere there is serious decision-making.

Through HR, we know if critical work is understood, if capability gaps are identified, and whether workforce culture is changing. A system can be created when these two functions are aligned. A silo-operated organization has gaps that can kill people in the wrong environment.

Do not ask whether your current systems will integrate with new technology. Ask whether they make people closer to the work more efficient, more present, and more connected to the information they need to stay safe or buried beneath it.

While we keep generating data, people are getting hurt— physically and psychologically—somewhere between the dashboard and the floor.

Our first step is to understand that HR and communications are not bystanders in this architecture. We must be authors.