Hostile Fiefdoms: The Cost of Information Hoarding

Hostile Fiefdoms: The Cost of Information Hoarding

How many times do you have to feel your soul slowly exit through your ear before you realize that your salary is essentially a bribe to tolerate structural incompetence?

Sarah is sitting at her desk, her knuckles white as she grips a lukewarm mug of coffee. It is 4:02 PM on a Tuesday, and she needs the Sales performance data for the Q3 campaign launching tomorrow. She emails Dave. Dave is the gatekeeper of the CRM, a man who treats customer data like it’s his personal inheritance. Two minutes later, she gets a reply. It’s not the data. It’s a link to a Jira portal. Dave tells her she needs to file a ticket. The ticket, Sarah knows, will sit in a queue of 52 other requests. It will eventually be flagged for ‘managerial review,’ but Dave’s manager is currently on a beach in Maui for the next 12 days.

This isn’t an organizational chart problem. It’s not a software limitation. It’s a hostage situation.

The Currency of Control

I’ve spent 12 years as a conflict resolution mediator, stepping into rooms where the air is so thick with resentment you could carve it with a dull butter knife. In those rooms, I’ve realized that most corporate silos aren’t built by accident. They are deliberately fortified fiefdoms. We like to use words like ‘cross-functional collaboration’ in our slide decks, but in the trenches, information is the only currency that matters. If Dave gives Sarah that data freely, he loses his leverage. He’s no longer the indispensable wizard of the CRM; he’s just a guy who knows how to run a report. And in an era of precarious employment, being ‘just a guy’ feels like a death sentence.

I’ll be honest, I spent about 22 years of my life pronouncing ‘misled’ as ‘mizz-uld,’ as if it were the past tense of some mysterious verb ‘to mizzle.’ I thought it was a fancy way of saying someone was confused. It wasn’t until a particularly embarrassing mediation session involving a board of directors and a leaked memo that I realized the word was ‘mis-led.’ I felt like a fool.

– Personal Reflection on Language Isolation

Companies do the same thing. They ‘mizzle’ themselves into believing that having 32 different software platforms-none of which talk to each other-is a sign of specialized excellence. They think that forcing an employee to enter the same customer name into three different systems is just ‘the way it is.’ In reality, it is a symptom of a deep, systemic lack of trust. If the Sales team doesn’t trust the Marketing team, they won’t share their data. If the Production team doesn’t trust Sales, they won’t give accurate lead times. Each department becomes a bunker, hoarding resources and protecting their ‘territory’ while the customer stands outside in the rain, wondering why nobody can answer a simple question.

The Cost of Friction

This fragmentation is the antithesis of what a business is supposed to be. When you are building something complex, the friction between parts is where the heat destroys the machine. I recently worked with a client who was trying to manage a global project by hiring 12 different vendors for 12 different parts of the process. Each vendor had their own timeline, their own standards, and their own ego. By the time the project reached the halfway mark, they had spent $42,000 just on meetings to figure out why the left hand didn’t know the right hand existed.

[In a world of fragments, the only real power is integration.]

What they actually needed was a single point of truth. It’s the same reason why high-end manufacturing and artistic production have moved toward integrated models. Consider the complexity of high-fidelity wax artistry or custom commercial displays. If you source the sculpting from one place, the mold-making from another, and the finishing from a third, you end up with a Frankenstein’s monster that satisfies no one. The beauty of a ‘one-stop solution’ isn’t just about convenience; it’s about the integrity of the vision. This is the exact problem that a Wax museum project addresses by bringing every stage of the creative and technical process under one roof. When you remove the barriers between the ‘departments’ of creation, you stop losing the essence of the work in the handoffs.

Customer Impact Metric: Retention Decrease

High Silo Environment

-22%

Retention Drop (2 Yrs)

vs

Integrated Model

Stable

Retention Rate

The Private Silo: Vanity and Fear

But let’s talk about the Dave in your office. Why does he hoard the data? He hoards it because he perceives the company as a zero-sum game. If Sarah’s campaign is a massive success, Dave worries he’ll be forgotten. In his mind, keeping Sarah waiting is a way of reminding her-and the organization-that he is a vital cog. This is the ‘Hostile Fiefdom’ mentality. It creates a culture where internal politics are more important than external results.

Fear of exposure breeds the need for defensive walls.

I remember a mediation I did for a tech firm where the Engineering lead refused to give the Support team access to the bug tracker. He claimed it was for ‘security reasons,’ but after 2 hours of digging, it turned out he was just embarrassed by how many open bugs there were. He was using a silo to hide his team’s failures. We spent 52 minutes just talking about how his fear was actually making the product worse. When teams don’t talk, errors don’t just happen; they multiply. They hide in the gaps between systems.

I sometimes find myself slipping into this trap in my own work. I’ll keep my notes on a private drive instead of the shared one because I’m not ‘ready’ for others to see the raw thoughts. It’s a form of vanity disguised as quality control. But every time I do that, I create a tiny silo. I create a moment where someone else has to wait for me to be ‘ready.’ We have to fight that instinct every single day.

Rewiring Incentives: From Walls to Bridges

To break the fiefdoms, you have to change the incentive structure. If Dave is rewarded for how many tickets he closes instead of how well the Marketing team performs, he will always prioritize the ticket queue. If the Production team is judged solely on speed rather than the lack of rework in the next stage, they will continue to ship ‘good enough’ products that the next team has to fix. We are essentially paying people to build walls.

Organizational Flow Metric

Seamless Handoff Success Rate

91% (Target: 90%)

91%

I’ve seen organizations transform simply by moving the ‘gatekeepers’ into the same physical or digital space as the ‘users.’ When Dave has to look Sarah in the eye every day-or at least see her face on a recurring Zoom call dedicated to a shared goal-it becomes much harder to hide behind a Jira ticket. Humanization is the natural enemy of the silo.

Humanization is the natural enemy of the silo. Look people in the eye.

In my 12 years of mediating, I’ve found that the most successful companies are those that prioritize the ‘turnkey’ experience-not just for the customer, but for the employee. They invest in integrated systems that allow for a seamless flow of information. They realize that a ‘one-stop’ philosophy isn’t just a marketing gimmick; it’s a survival strategy. It’s about ensuring that when Sarah needs data, she can get it in 2 clicks, not 12 days.

The Cage of Control

We often think of ‘efficiency’ as doing things faster. But real efficiency is about removing the things that shouldn’t be happening at all. You shouldn’t be entering data twice. You shouldn’t be waiting for approval for a report that has no sensitive information. You shouldn’t be navigating the ego of a middle manager just to do your job. These are the frictions that turn a team into a collection of warring tribes.

If you find yourself stuck in a fiefdom today, ask yourself: what am I protecting? Is it the company’s success, or is it just my own sense of control?

As I look back on my own career, and those ‘mizz-uld’ moments of misunderstanding, I realize that the most profound shifts come from radical transparency. It’s uncomfortable. It’s vulnerable. It means Dave has to admit that his CRM data isn’t perfect, and the Engineering lead has to admit there are bugs. But once the walls are down, you can finally stop defending your territory and start doing the work you were actually hired to do.

The moment you let the data flow, the moment you integrate the systems, the moment you trust your colleagues-that’s the moment the cage door opens. You might find that the world outside the silo is a lot bigger, and a lot more productive, than the tiny corner you’ve been defending for the last 12 years.

Stop building walls.

Start building bridges. Or better yet, just tear the whole fortress down and build something that actually works for everyone involved.

Conflict resolution principles applied to organizational architecture.