I've been called a lot of things on client engagements. Consultant. Solution architect. Process expert. But the role I end up playing more often than any of those is translator.

Not because the technology is complicated. Because the people in different departments have spent decades developing their own languages, their own priorities, and their own mental models of what the other teams are doing wrong.

Organizational silos in manufacturing aren't an IT problem. They're a culture problem — and they require a fundamentally different approach than most technology vendors will tell you.

The Org Chart Doesn't Show You the Real Problem

When I walk into a new engagement, I don't start with a system audit. I start with conversations. One-on-ones with people in engineering, manufacturing, supply chain, quality, IT. And I ask the same question to everyone: What does the team downstream of you not understand about your work?

The answers are almost always illuminating.

Engineering says manufacturing just wants to ignore design intent and do things however they've always done them. Manufacturing says engineering doesn't understand cycle time, tooling constraints, or what it actually takes to produce something at volume. Supply chain says both teams change things without telling anyone and then wonder why parts aren't available. Quality says everyone knows about the issues but nobody wants to own them.

These aren't wrong observations. They're all partially right. But they're each missing the other team's perspective — and that's what creates the silo.

Why Technology Doesn't Solve This

Here's the uncomfortable truth: most enterprise software implementations make silo problems worse before they make them better.

Here's why. System implementations create a forcing function for process decisions. Suddenly, someone has to decide: which team owns this data? Which system is the master record? Who approves changes before they flow downstream?

In organizations without strong cross-functional leadership, those decisions get made by whoever has the loudest voice in the room during the implementation. Which usually means one team's workflow gets codified in the system, and every other team has to adapt to it. The other teams didn't lose the argument — they were never in the room.

Then the system goes live, the "winning" team's workflow is automated, and the resentment from every other team calcifies. The silos don't break down. They get automated.

Technology doesn't break down silos. Aligned incentives do.

What Aligned Incentives Actually Look Like

The manufacturers who successfully break down organizational silos share one characteristic: they've built metrics that force cross-functional accountability.

When engineering is measured only on design completeness and manufacturing is measured only on production throughput, you get two teams optimizing for different things with no reason to care about each other's constraints. The engineer hits their targets by releasing designs on time. The manufacturing engineer hits their targets by keeping the line moving. Neither metric reflects what actually matters: getting the right product out the door at the right cost.

The companies that do this well create shared metrics that cut across organizational boundaries. First time right rate. Cost of Poor Quality that gets allocated back to the team that caused it. New product introduction cycle time that engineering and manufacturing both own.

When the same number shows up on both teams' scorecards, the conversation about whose fault something is becomes a lot less interesting than the conversation about how to fix it.

The Real Role of Cross-Functional Teams

Cross-functional teams get a lot of hype. Most implementations I see treat them as a box to check: "Yes, we have a cross-functional team for NPI." Then I ask who's on it, how often they meet, what authority they have, and who owns the outcomes — and the answers reveal that it's mostly a coordination meeting with no real decision-making power.

A cross-functional team that works looks different. It has representatives with actual authority to commit their teams. It has clear decision rights — not just input rights. It has accountability for outcomes that span organizational boundaries. And it has executive sponsorship that reinforces those accountability structures when they get tested.

The testing always comes. Someone's department head decides to override the cross-functional team's recommendation. A priority conflict comes up and the team starts making unilateral decisions. The integration breaks and everyone points fingers.

The organizations that get through that testing are the ones where someone at the top — a COO, a VP of Operations, a GM — has explicitly made cross-functional accountability a priority. Not in a town hall speech. In how they respond when the finger-pointing starts.

The Change Management Work That Nobody Wants to Pay For

Here's where I'll say something that makes some clients uncomfortable: the change management work — the stakeholder alignment, the role clarification, the governance design — usually takes longer and costs more than the technical implementation. And most organizations don't want to budget for it.

I understand why. It's much easier to point to software as the deliverable. You can see a system. You can demonstrate a workflow. You can show a dashboard. "We aligned the organization and clarified decision rights" doesn't show up on a project status slide.

But when implementations fail — and they fail more often than vendors admit — it's almost never because the software didn't work. It's because the human infrastructure to support it wasn't built.

The questions that need answers before go-live:

• Who owns the item master, and what's the process for creating or changing a part number?

• When engineering changes a design, who needs to know before it flows to manufacturing?

• When a quality issue surfaces on the floor, what's the path from detection to root cause to corrective action?

• When two teams disagree about a product data decision, who has the authority to make the call?

If you can't answer those questions before you go live, the software will reveal the gaps — loudly and expensively.

Starting Smaller Than You Think

The good news is you don't have to solve the whole org-chart before you can make progress. In fact, trying to boil the ocean is usually what kills these initiatives.

The approach that works: find one cross-functional pain point that both teams agree is a problem. Map the current state. Get alignment on what good looks like. Implement a process change — not a system change — and see if the teams can actually operate it together. Then use that success to build credibility for the next initiative.

It's slower than "big bang" transformation. It's also the approach that actually sticks.

Element Consulting helps manufacturers align cross-functional teams, design governance frameworks, and implement the process infrastructure that makes system investments actually work. If your silos are stronger than your integrations, let's start a conversation.