Why silos quietly tax speed, accountability, and customer experience
Three in four cross-functional teams underperform on key metrics. If you run a business unit, that is not an abstract collaboration problem; it is a direct warning that the way work moves across functions is likely costing you speed where customers can feel it (McKinsey, 2024).
You have seen the scene. A regional services VP walks into a quarterly review after sales has promised a delivery date operations never approved, finance is disputing margin assumptions, and support is already handling complaints for an issue no one officially owns.
That is what silos look like in practice. Not boxes on an org chart, but handoffs that stall, work that gets redone, and decisions that sit in the gap between teams because each function is acting rationally inside its own lane.
The cost compounds fast. Deloitte found that 66% of C-suite leaders say it is very or extremely important to push beyond traditional functional boundaries, yet only 7% say they are making great progress doing so (Deloitte, 2026).
66% say cross-functional integration is critical, but only 7% report great progress (Deloitte, 2026).
That gap is where business-unit performance leaks away: slower launches, noisier escalations, weaker forecasting, and a customer experience that feels fragmented even when every team is busy. This article is about how a GM closes that gap by redesigning how the unit works, not by asking people to “collaborate better.”
The hidden tax is local optimization
Specialization is not the enemy. A business unit needs strong functional judgment in sales, operations, finance, and support. Problems start when those functions optimize for their own targets without enough shared visibility into the outcome the business actually needs.
Sales pushes volume. Operations protects throughput. Finance tightens variance. Support absorbs the fallout. Each move can make sense on its own and still produce a worse result for the unit.
This is why the GM matters. The GM is the only role with the mandate to connect trade-offs across the whole system — revenue, cost, service, capacity, and customer impact — and to decide where one function’s local win creates another function’s downstream burden. That is not a culture poster. It is operating design.
The role is not referee; it is system architect
Many leaders treat silos as a behavior issue. They sponsor offsites, ask for more alignment, or invest in functional leadership excellence inside each department. Useful, but incomplete.
A GM has to do something harder: clarify ownership where work crosses boundaries, make trade-offs explicit, and create a cadence where issues surface before they become customer pain. If that sounds structural, it is. Silos rarely persist because people dislike each other. They persist because the system keeps rewarding separation.
So the real question is not whether your teams are specialized. It is whether specialization is sharpening execution — or quietly turning into isolation that no one owns until performance slips.
What are silos, and when does specialization become harmful isolation?
95% of respondents in one workplace study said they were motivated to reduce silos. So what if the real problem is not unwilling people, but a system that makes separation the easier default? Before a GM labels this a collaboration issue, it is worth asking a harder question: are your functions actually resisting each other, or are they simply built to succeed without needing one another (National Institutes of Health, 2024)?
That distinction matters.
Specialization is useful; isolation is expensive
A silo is not just a function with deep expertise. It is a function that performs well inside its own boundary but fails at the points where work, information, and decisions need to cross into another team. Sales can be disciplined. Operations can be efficient. Finance can be rigorous. If those strengths do not connect, the business unit still underperforms.
Healthy specialization sharpens judgment. Harmful isolation narrows it.
In a mid-market manufacturer during budget season, the operations director freezes overtime to protect cost targets while commercial leaders push a promotion to hit quarterly volume. Neither decision is irrational. The problem is that no one is accountable for the combined effect: backlog rises, service slips, and margin gets eroded by expedite costs two weeks later. Each function did its job. The business unit did not.
That is what executives often miss. Silos rarely begin with bad intent. They emerge when teams are measured, staffed, and reviewed in ways that reward local wins more than shared outcomes.
Collaboration is not the same as synergy
Many organizations say they want more collaboration when what they actually need is synergy. Collaboration can mean more meetings, more handoffs, or more polite coordination. Synergy is stricter. It means the whole system performs better than the sum of its parts because functions make better trade-offs together than they would alone.
The research points in that direction. 58% of respondents in the NIH and CDC-authored study identified institutional factors — organizational structure, bureaucracy, and red tape — as contributors to siloing (Centers for Disease Control and Prevention, 2024). In plain managerial terms: people often work in fragments because the operating model tells them to.
58% pointed to structure and bureaucracy as drivers of siloing, not simply individual behavior (Centers for Disease Control and Prevention, 2024).
A GM should read that as a design problem. If incentives, decision rights, and escalation paths all reinforce functional independence, asking leaders to “partner better” will not change much.
The real test is simple: are your teams merely cooperating at the edges, or is the unit making smarter decisions because they are connected? If the answer is unclear, the next issue is unavoidable — who gets rewarded for the whole, and who gets rewarded for the part?
Why incentives and decision rights matter more than slogans
70% of the variance in team engagement can be attributed to managers. That should change how a GM reads a silo problem: not as a failure of intent, but as a failure of design (Gallup, 2024).
Most organizations still reach for language first. They ask leaders to collaborate, reinforce values, and talk about “one team.” The evidence points somewhere less comfortable. If managers shape engagement that strongly, what happens when the GM leaves incentives and decision rights untouched? People hear the slogan, then follow the scorecard.
People do what the system pays for
This is why silos survive even when nobody defends them. A sales leader is paid on bookings, operations on utilization, finance on cost control, and customer success on retention. Each function can hit its number while the business unit misses the outcome that actually matters.
Gallup’s latest workplace data makes the managerial stakes hard to ignore: only 31% of employees are engaged, while 17% are actively disengaged (Gallup, 2024). That is not just a morale issue. It is a coordination issue. When teams do not see how their work connects to a shared result, they retreat to what is measurable, familiar, and locally rewarded.
In a regional healthcare provider during annual planning, the service-line VP pushes for faster patient intake, finance tightens labor budgets, and clinical operations protects staffing ratios. The weekly meeting sounds aligned. The actual decisions are not. Every exception gets escalated because no one knows who can trade speed against cost against care quality without political risk.
Decision rights are the hidden speed system
Decision rights determine whether cross-functional work moves at the level where facts are freshest or gets trapped in an escalation loop. When rights are vague, teams protect themselves. They copy more people, ask for more approvals, and delay trade-offs until a senior leader intervenes.
That is why the GM’s job is not motivational. It is architectural. The GM has to define which decisions sit with functions, which require shared input, and which belong to the business unit leader because they cut across revenue, cost, and customer impact. This is the practical core of integral leadership: shaping the conditions under which better behavior becomes normal, not heroic.
Shared metrics matter for the same reason. A common dashboard creates shared visibility; a shared incentive creates shared attention. Without both, “partnership” remains optional.
Low engagement costs the global economy US$8.9 trillion, or 9% of global GDP (Gallup, 2024).
The GM who aligns goals, incentives, and workflows makes cooperation the easiest path. The one who does not gets polite meetings and recurring friction. So what does real cross-functional synergy look like when the system is finally built to support it—not fight it?
What does cross-functional synergy look like in a business unit?
66% of C-suite leaders say it is very or extremely important to push beyond traditional functional boundaries (Deloitte, 2026). If your business unit still runs through disconnected handoffs, that gap shows up where it hurts most: revenue slips from delayed execution, customer trust erodes in the seams, and strong people leave because too much work feels harder than it should.
The practical question is not whether functions should work together. It is what cross-functional synergy looks like when it is real.
The operating signs are visible
Start with the basics. Fewer stalled handoffs. Faster decisions at the point of work. Clearer accountability when tradeoffs have to be made. Better customer outcomes because the unit behaves like one business, not four departments.
In a mid-market technology company during a quarterly review, the VP of sales wants to accelerate a product bundle, operations flags implementation capacity, finance sees margin risk, and support is already tracking a rise in onboarding tickets. In a siloed unit, that conversation ends with follow-up meetings and private escalations. In a healthy unit, the same facts are on the table at once, the tradeoff is made in the room, and one owner leaves with a decision—not four leaders leave with different interpretations.
That is synergy. Not harmony. Not more meetings. A faster, cleaner way to convert functional expertise into business outcomes.
Design work around outcomes, not boundaries
This is where many GMs get tripped up. They organize cross-functional work around the org chart—sales does its part, then operations, then finance, then support. But customers do not experience your org chart. They experience response time, delivery reliability, pricing clarity, and issue resolution.
So the unit has to be designed around a common operating purpose: winning profitable demand, fulfilling it reliably, and resolving issues without internal friction. Functional depth still matters. In fact, it matters more when connected well. Strong functional leadership excellence across domains is not the opposite of synergy; it is one of its inputs.
Deloitte’s global research base is broad enough to matter here—14,000 leaders in 95 countries participated in its 2024 Human Capital Trends work (Deloitte, 2024). The signal is clear: boundary-spanning performance is no longer a niche management concern.
Real synergy means sales, operations, finance, and support share visibility into priorities, constraints, and tradeoffs before the customer feels the disconnect.
That shared visibility is where most business units either gain speed—or create bureaucracy. So the next question is unavoidable: how do you align goals, metrics, and workflows tightly enough to improve coordination without building a heavier system than the one you are trying to fix?
How should a GM align goals, metrics, and workflows without adding bureaucracy?
The four-part operating model is simple: shared outcomes, shared metrics, decision rights, and visible workflows. It matters because every GM has sat in the Monday meeting where sales says the quarter is on track, operations says capacity is full, and finance says margin is slipping—yet no one can explain which number should govern the next decision.
This is where most “alignment” efforts go wrong. They add forums before they fix design. McKinsey found that three in four cross-functional teams underperform on key metrics (McKinsey, 2024), and Deloitte reports that only 7% of leaders say they are making great progress breaking beyond traditional functional boundaries (Deloitte, 2026).
Three in four cross-functional teams underperform on key metrics (McKinsey, 2024).
Start with outcomes everyone can move
A GM should begin with a small set of shared outcomes—usually three or four, not twelve. Think revenue quality, delivery reliability, cash discipline, and customer retention. If every function can influence the outcome, every function should see it as part of its job.
In a regional retail business during peak-season planning, the merchandising director pushed assortment breadth, supply chain protected inventory turns, and store operations fought for labor flexibility. The breakthrough did not come from another steering committee. It came when the GM reduced the conversation to two shared outcomes: in-stock availability on priority items and gross margin after markdowns. The trade-offs got sharper because the target got clearer.
Replace competing scorecards with a common view
Shared metrics are not about taking functional metrics away. They are about putting a business-unit layer above them so local wins do not hide system losses.
A good test is blunt: can one function hit its target while the customer experience gets worse? If yes, the scorecard is still siloed. The fix is not a bigger dashboard. It is a tighter one. A handful of shared measures reviewed weekly will do more than a dense monthly pack no one uses.
Make decision rights and handoffs explicit
Then define decision rights with precision: what a function owns, what requires cross-functional input, and what must escalate to the GM. Ambiguity creates delay. Clarity creates speed.
Finally, make workflows visible at the handoff points—quote to delivery, forecast to capacity, issue to resolution. Name the owner of each transition, the expected turnaround, and the trigger for escalation. This is where practices like integral team coaching or disciplined team development and follow-up colloquia can help: not as add-ons, but as ways to reinforce how the unit actually works.
The real question is not whether your model is elegant. It is whether people can use it under pressure—during a client escalation, a forecast miss, a bad week. And if they cannot, where should a GM begin fixing it first?
Where should a GM start in the first 30 days?
The first month is for diagnosis, not theater
The 30-Day Friction Audit is where a GM should start. And the uncomfortable question is this: when you inherit a business unit with visible tension between functions, are you actually looking at a people problem—or at a work design problem no one has named yet?
A newly appointed GM in a regional services business often walks into the same scene. Sales says operations is slow. Operations says finance keeps changing the rules. Support says nobody warns them before promises reach customers. The instinct is to call a reset meeting and ask for better collaboration. That usually misses the point.
Research from National Institutes of Health and Centers for Disease Control and Prevention authors found that 95% of respondents were motivated to reduce silos (National Institutes of Health, 2024). The issue, then, is rarely lack of intent. It is where the system breaks.
Start by testing four points of failure: goals, incentives, decision rights, and cadence. Where do teams pursue different outcomes? Where does one function absorb the cost of another function’s decision? Which calls require three approvals when one should do? Which meetings produce updates but not decisions?
58% of respondents identified institutional factors such as structure, bureaucracy, and red tape as contributors to siloing (Centers for Disease Control and Prevention, 2024).
That statistic should shape the first month. Look for friction embedded in the operating model, not just in personalities.
Map the handoffs that create customer pain
Do not map everything. Map the few handoffs that matter most: sales to operations at commitment, operations to finance at forecast and margin review, finance to support when policy changes affect customers, support back to sales when recurring issues signal bad-fit deals.
In practice, this can be done in a week. Put the leaders in one room. Trace the path of one recent order, one forecast revision, and one customer escalation. Mark where information was incomplete, where ownership blurred, and where time was lost. If you want a sharper read on recurring leadership patterns behind those breakdowns, tools like predictive HR analytics for leadership planning can help separate structural issues from capability gaps.
Then fix one or two routines fast. A weekly business review that ends with explicit decisions, not status recaps. A simple escalation path with named owners and response times. Nothing elaborate. The point is to remove drag people feel immediately.
Early wins matter because they change belief. When a cleaner review meeting cuts escalation loops, or when support gets earlier visibility into risky deals, teams see that cross-functional discipline can reduce work rather than add it. That is also why some GMs invest in targeted leadership development for chief operating officers and adjacent leaders early—the bottleneck is often managerial coordination under pressure.
The first 30 days should not produce a grand redesign. They should produce proof. And once the unit feels that proof, a harder question appears: how do you keep collaboration useful—without letting the system grow heavy again?
Why the best GM-led collaboration systems feel simpler over time
Bad collaboration systems do not fail quietly. They lose deals in the gap between promise and delivery, wear down customer trust one handoff at a time, and push strong leaders out because every cross-functional issue turns into politics.
That is why the end state should feel almost uneventful. If collaboration is working, why does it often feel less dramatic than the silo problem it replaces? Because cross-functional synergy is not an initiative to keep relaunching. It is a management system that becomes lighter as routines become clear.
Simpler is the point
In an enterprise financial services business during a client escalation, the division president should not need to personally broker every dispute between sales, risk, operations, and service. If that keeps happening, the unit does not have a collaboration culture problem. It has a design problem.
The best systems reduce the need for heroics. Managers matter enormously here; Gallup’s research shows how much team performance is shaped by managerial practice, not just intent (Gallup, 2024). The GM’s role, then, is to keep the system connected — to make sure decisions move, trade-offs are visible, and conflicts get resolved at the right level.
Healthy specialization still matters. You want strong functional judgment. You do not want separate kingdoms defending local logic after the business has already changed around them.
Judge the system by what gets easier
The real test is operational, not rhetorical. Are decisions faster? Are handoffs cleaner? Do customers experience one business instead of a relay race between departments?
When that answer is yes, the gains compound. McKinsey has pointed to meaningful efficiency gains when organizations remove friction from how work crosses boundaries (McKinsey, 2024). Not because people suddenly become more agreeable, but because the work itself requires less translation, less escalation, and less recovery.
That is what a good GM-led model does over time: it makes coordination ordinary.
If your current system still depends on you to settle every cross-functional tension, that is the signal. What would need to become simpler — this quarter, not someday — for the business unit to run as one business?
