Organizational silos: what the Titanic teaches us about information that never arrives
Ask anyone what sank the Titanic and you'll get the same answer: an iceberg.
Maybe they'll add the part about the lifeboats, the band playing on, or Jack and Rose at the bow.
But the real story is far more interesting. And far more relevant to how we run organizations today.
But before we get to that, let's define what we're talking about.
What is an organizational silo?
An organizational silo is a part of a company that becomes so focused on its own metrics, priorities, and survival that it stops sharing information or collaborating with the rest of the organization. The result: critical signals get stuck, decisions slow down, and the wider business misses what the silo can already see.
A story about the Titanic & organizational silos
On April 14, 1912, at least seven different ships radioed ice warnings to the Titanic.
Some were specific: icebergs directly in its path. Others were blunt: we've stopped because we're surrounded by ice.
All of these warnings made it to the ship's radio room. Almost none were treated as urgent.
Here's why.
The Titanic's radio operators didn't work for the captain. They were employees of the Marconi Company. Their job was handling passenger telegrams: personal messages from wealthy travelers to people on shore.
Think of it as the social media of 1912. That was their KPI.
Ice warnings? Not their priority.
Break the silos before they sink you. Learn how 200+ progressive organizations design for good information flow in our Masterclass.
Image source: Wikipedia
When the nearby Californian tried to warn the Titanic that it was surrounded by ice, operator Jack Phillips shot back:
"Shut up. I'm busy."
He was working through a backlog of passenger messages.
The Titanic had the information. It had the technology. It had the time.
What it didn't have was a structure where life-saving information could reach the people who needed it.
The ice warnings weren't filtered out by malice or incompetence. They were filtered out by design.
By a system where the person receiving the signal was optimizing for something entirely different than the ship's survival.
By an organizational design that prevented information from flowing to the right place at the right time.
The perfect organizational silo
The Titanic's radio room was a perfect organizational silo.
A structure that makes people focus locally at the expense of the whole.
Jack Phillips wasn't a bad radio operator. He was excellent at his actual job: transmitting passenger messages. The Marconi Company probably gave him glowing reviews.
But his incentives, his reporting lines, his entire work structure pointed him away from the ship's survival and toward clearing his telegram backlog.
That's what an organizational silo really is. A part of the organization that's so focused on its own metrics, its own priorities, its own survival, that it can't see the iceberg approaching.
Or worse: it can see the iceberg but doesn't consider warning about it part of the job.
Your organization is full of ice warnings
If you've ever worked in a large organization, the Titanic's radio room should feel familiar.
Customer complaints sit in support ticket systems that product teams never see. The support team closes tickets efficiently. Their metrics look great. Meanwhile, the same product flaws generate complaint after complaint.
Market shifts get picked up by salespeople who mention them in passing during quarterly reviews. By the time the signal reaches strategy, it's been filtered through three layers of management and packaged into PowerPoint. The urgency is gone.
Employee concerns raised in engagement surveys disappear into HR dashboards. HR produces detailed reports. Action plans are created. Task forces are formed. The original concerns remain unaddressed.
Everyone is busy transmitting their own telegrams.
Each silo has its own language, its own priorities, its own definition of success.
And just like the Titanic's radio operators, the people in these silos aren't failing. They're succeeding at exactly what their structure rewards them for.
The iceberg gets closer.
Why silos survive (they're not a bug, they're a feature)
Here's what most people miss about organizational silos: they're not caused by bad people or poor communication.
They're rational responses to structure.
When you group similar work into departments, you create functional concentration. Finance sits with finance. IT sits with IT. Marketing sits with marketing.
It sounds efficient. Until it isn't.
Dutch sociotechnical pioneer Udo de Sitter described this decades ago. Functional concentration creates walls. Not because people want walls, but because the structure demands them.
Each department develops its own targets. Its own language. Its own priorities.
Soon, departments stop talking. People start optimizing for their own metrics instead of the customer. You get handovers, delays, and endless email chains trying to coordinate across the walls you've built.
Ever tried getting a hospital invoice corrected? Or changing a train ticket? That's functional concentration at work. Each department doing its job perfectly while the customer drowns in the gaps between them.
The silos aren't bugs. They're features of a system designed for efficiency, not effectiveness.
Separate KPIs make it worse. When finance gets rewarded for cutting costs and product gets rewarded for adding features, they're not on the same team. They're competing.
The Titanic's radio operators weren't badly trained. They were well-trained for the wrong priorities.
Most organizational silos work exactly the same way.
What progressive organizations do instead
Over the past decade, Corporate Rebels has visited hundreds of organizations that have solved this problem.
They don't fix silos with more meetings. They don't create matrix structures or add integration roles. They don't try to build a better Titanic.
They redesign how information flows.
Shorten the distance between signal and response
Progressive organizations build networks of customer-connected teams instead of layered hierarchies.
At bol.com, rapid growth created the familiar problems. More employees, more complexity, more hierarchy. And with it: silo thinking, bureaucracy, and the first signs of disengagement.
Their response? They moved from large functional departments to small, cross-functional teams. Each team focused on a specific product category. Within their Stores division, they created 42 cross-functional teams grouped by shared customer journey.
The result: teams that feel like small companies. Close to the customer. Able to spot the ice themselves.
Most progressive organizations follow this pattern. They ensure the majority of teams are directly connected to customers. People can pick up signals themselves. Almost everyone can see the ice approaching.
Push decisions to where the information lives
Seeing the ice isn't enough if you can't steer the ship.
Progressive organizations push decision-making authority to where information flows. No chain of relay where warnings get repackaged or lost. No escalation through three layers. No waiting for permission from a distant captain.
The person who sees the ice can steer.
HOLIS, a Japanese company with 27 businesses, embodies this approach. They eliminated middle management entirely. CEO Takuya Katagiri led a transformation to a decentralized model where small teams have full decision-making autonomy.
Each business operates like its own ship. When they spot ice, they don't radio headquarters for permission to change course. They steer.
Make transparency the default
Traditional organizations treat information like treasure. Financial data stays with finance. Customer feedback stays with support. Strategy stays with leadership.
Progressive organizations flip this. Information is open by default.
HOLIS makes financial flows transparent across all 27 businesses. Everyone sees the numbers. Everyone understands how money moves.
Nation Partners opens all salary data and business metrics internally. This eliminates guesswork. It removes politics from pay discussions. Instead of lobbying a manager, people focus on meaningful work.
When the entire crew can see ice warnings, you don't depend on one radio operator deciding what's urgent.
Align incentives around shared outcomes
The Marconi operators weren't bad people. They were rational actors in a badly designed system. Their paycheck came from passenger telegrams, not from keeping the ship afloat.
Progressive organizations remove these structural conflicts.
HOLIS aligns employee and organizational goals through transparent money flows and shared rewards. When everyone participates in financial success, nobody optimizes their silo at the expense of the whole.
Clarasys, an employee-owned consultancy, distributes profit based on tenure rather than role or performance. This creates collective achievement rather than competition between departments.
NER Group advocates minimum 30% annual profit sharing. But here's the key: everyone needs to understand how they influence outcomes. If people don't see how their work connects to results, profit sharing becomes just another perk.
When your success is tied to organizational success, not your department's KPI, you don't tell other ships to shut up when they warn about ice.
Stop building better titanics
Here's the deeper lesson from April 14, 1912.
The Titanic's problem wasn't just bad communication between the radio room and the bridge. The problem was the ship itself was the wrong model.
One massive vessel. One bridge. One captain. One point of failure.
No matter how good your protocols, a single centralized structure will always have this vulnerability: too many layers between signal and response. Too many chances for critical information to get delayed, diluted, or lost.
The alternative isn't a better Titanic with faster elevators to the bridge.
It's replacing the Titanic altogether.
With a fleet of speedboats.
Small, autonomous teams. Each able to see ice and steer away. Each talking to others laterally, not routing every signal through central command. A network, not a hierarchy.
Progressive organizations don't have one giant ship hoping the right information reaches the bridge in time. They have fleets of small crews, each with the authority to change course, each sharing what they see with others in real time.
Everoze describes their structure this way: "not perfect, but just one way to see how we're organized." Structure is a tool, not an ideology. They run three overlapping structures: project teams, tech teams, and functional teams. People don't sit in boxes. They flow where needed.
That flexibility matters more than the specific model. When you stop thinking in terms of one right structure, you can build systems that actually let information flow.
The organizational silos that sink companies aren't different from the ones that sank the Titanic. They're the same pattern, repeated across industries and decades.
Functional separation. Local optimization. Information that exists but can't flow. People doing their jobs perfectly while the organization steams toward disaster.
The fix isn't better communication protocols or more integration meetings. It's recognizing that the giant ship model is the problem.
Build speedboats instead.
The question for your organization
The Titanic's ice warnings are 113 years old. The failure pattern is alive in most organizations today.
So ask yourself:
What ice warnings are sitting in your organization right now?
What critical information is stuck in someone's inbox, trapped in a silo, or being deprioritized because the person who has it is optimizing for the wrong thing?
And more importantly:
Are you trying to build a better Titanic?
Or are you ready to build a fleet of speedboats?
Ready to swap the Titanic for a fleet of speedboats?
Spotting the silos in your organization is not that difficult. Redesigning how information actually flows, pushing decisions to where the signals live, and aligning incentives across the whole ship is harder.
That's exactly what we built the Progressive Organizational Design Masterclass for. Six weeks, a global cohort of rebels, and a practical playbook drawn from the 200+ progressive organizations we've studied. You'll walk away with the structures, principles, and peer network to start replacing your own Titanic.
