Latest / The Productivity Podcast with Fexingo: Output, Efficiency, and Long-Term Economic Growth / The Hidden Productivity Cost of Organizational Silos
Transcript
- Lucas: If I asked you to name the biggest productivity killer in your organization, you might say meetings, or email overload, or your boss. But there's a quieter, more systemic one that rarely gets talked about. Luna: Let me guess — silos. Those invisible walls between departments. Lucas: Exactly. And McKinsey actually put a number on it. Their research found that knowledge workers spend nearly twenty percent of their time just searching for internal information or tracking down the right person in another department. Luna: Twenty percent. That's a full day every week. Lucas: Right. And for a company with five thousand knowledge workers, that adds up to tens of millions in wasted salary per year. But the cost is worse than just time — silos create duplicated work, delayed decisions, and a kind of organizational amnesia where the left hand has no idea what the right hand is doing. Luna: So why do they persist? It's not like anyone sets out to build a silo. Lucas: No, they emerge naturally from specialization. You have a marketing team that lives and breathes campaigns, an engineering team that lives and breathes code, and each develops its own language, its own priorities, its own metrics. Over time, the departments optimize for their own goals — and those goals may not align. Luna: Right — marketing wants brand awareness, engineering wants technical excellence, and the customer experience falls through the cracks. Lucas: Exactly. And the incentives reinforce it. If a marketing manager is evaluated on lead generation, they're not going to slow down to loop in engineering unless they're forced to. The system rewards silo behavior even if leadership preaches collaboration. Luna: So what's the fix? Some companies have tried structural solutions. Spotify famously organized into squads, tribes, and chapters — cross-functional teams that own a feature end to end. Lucas: And Zappos went further with holacracy, which basically eliminated managers and job titles. But those are extreme cases. A more common approach is to create 'liaison roles' — people whose job is to bridge departments. Luna: That sounds sensible, but it can create its own silo — the liaison becomes a bottleneck. Lucas: True. And there's research from Denmark that's really interesting on this. A Danish study looked at open-office layouts and found that even in completely open spaces, silos persisted. The physical walls were gone, but the mental ones remained. People still only talked to their own team. Luna: So it's a culture problem, not a floor plan problem. Lucas: Exactly. And that's harder to fix. One metric that can help is what I call 'time to answer' — how long does it take to get a response when someone from one department asks a question of another? If it's more than a few hours, you have a silo problem. Luna: I love that. It's concrete. You can measure it. Lucas: Yeah. And if you track it over time, you can test whether your interventions are working. Some companies have started 'rotation programs' where employees spend six months in another department. Others use shared goals — like tying bonuses to company-wide performance, not just team performance. Luna: Speaking of company-wide performance — one of the reasons we can talk about this kind of thing without interruption is that we don't run ads on these episodes. If you find value in that, and you want to support the ad-free model, we have a simple way to do that. Lucas: Yeah, it's really straightforward. You can go to buy me a coffee dot com slash fexingo. No pressure, no perks — just a way to say this kind of deep dive is worth keeping free. Luna: Exactly. And it helps us stay independent and focused on what matters. Now back to silos — another interesting fix is shared digital workspaces. Lucas: Right. But again, tools alone don't solve culture. You can have a shared Slack channel, but if nobody posts in it, it's just a ghost town. The key is leadership modeling. If the CEO visibly asks for input from other departments and acknowledges their contributions, it signals that cross-functional work is valued. Luna: So it's top-down, but also bottom-up. Everyone has to buy in. Lucas: Exactly. And one of the most powerful bottom-up moves is simply creating 'show and tell' sessions where teams share what they're working on. Not for approval, but for awareness. That alone can reduce duplicated work. A Danish engineering firm I read about cut duplicated effort by thirty percent just by doing weekly cross-department demos. Luna: Thirty percent — that's huge. And it's almost free to implement. Lucas: That's the thing about silos. The cost is enormous, but the fixes are often cheap — they just require a change in habit. And the first step is measuring the problem. time to answer, duplication rate, decision latency. Once you surface those numbers, the case for change becomes undeniable. Luna: So next time you're frustrated by a slow cross-department project, don't just blame the people. Look at the structure. And maybe suggest a time to answer metric. Lucas: Exactly. And if you do, let us know how it goes. We'd love to hear.