You’ve been in the meeting.

Sarah, your SVP of product, is on slide 17. The spreadsheet is immaculate, the ROI projection is a perfect hockey stick, and the ask is clear: She needs David’s best engineer for six months to launch "Project Titan," the company’s next big thing.

The room goes quiet. Everyone looks at David, the VP of Engineering. He clears his throat, praises Sarah’s diligence, and then delivers the polite, corporate "no."

"I'd love to help, Sarah," he says, "but my team is at capacity. We're focused on critical stability work that I just can't pull them off of right now."

The meeting ends. Sarah is furious. She comes to your office and vents: "David is hoarding his best people! He's not a team player. He's putting his own silo ahead of the company's most important initiative. We have a collaboration problem."

And you, as the executive leader, are inclined to agree.

But what if Sarah is wrong? What if David isn't the problem? What if the problem is the spreadsheet itself?

The real diagnosis: The trust deficit

Why do department heads refuse to share resources even for high-priority projects?

For decades, we’ve been told that resource hoarding is a political problem, a symptom of a bad culture. The solution? More team-building, more cross-functional offsites, more speeches about being "one team."

This is a fundamental misdiagnosis.

Your best leaders aren't hoarding resources because they are selfish. They are hoarding resources because they are rational actors in a broken system. They are making a smart, defensive bet against a single, corrosive force: untrustworthy data.

How does poor data quality lead to internal office politics and resource hoarding? This poor data introduces a "trust deficit," which is the single biggest barrier to achieving enterprise agility. David doesn't trust the data in Sarah's plan, and his self-preservation instinct is telling him not to trade his most valuable asset—his star engineer—for a promise built on a foundation of sand.

This isn't a new phenomenon. It's a deeply human behavior, explained by decades of research in psychology and economics.

First, it’s a classic case of “loss aversion.” As Nobel laureates Daniel Kahneman and Amos Tversky proved, the psychological pain of losing something is twice as powerful as the pleasure of an equivalent gain. For David, the potential pain of giving up his engineer and having his own projects fail is far more potent and real than the abstract corporate pleasure of Project Titan’s success. He is psychologically wired to avoid the loss.

Second, the situation is rife with “information asymmetry.” A concept from Nobel laureate George Akerlof, this describes a situation where one party has better information than the other. David has the better information. He knows the data in Sarah's spreadsheet is a guess. He knows the story points are inconsistent, the timelines are optimistic, and the financial projections aren't connected to the real work. He is being asked to trade a real asset for what he knows is a "lemon" of a plan. His refusal is not political; it's intelligent.

This leads directly to a corporate “prisoner's dilemma.” In a low-trust environment created by bad data, the safest individual strategy is to protect your own interests. David can't trust that if he gives up his engineer and his project catches fire, the system will help him. So, he defects. He hoards. He ensures his own survival, even if it leads to a worse outcome for the company as a whole.

Fixing the system, not the people

As systems thinking teaches us, you cannot fix the behavior without fixing the system that creates it. The problem isn't your leaders; it's the system that forces them into a defensive crouch.

The system lacks a feedback loop of trusted, real-time data. The solution, therefore, is not another process or a new mandate. The solution is architectural.

To solve the trust deficit, you must create a single, shared, and verifiably trustworthy reality.

Imagine a different version of that meeting. Instead of a spreadsheet, Sarah and David are looking at a strategic command center. This isn't just a dashboard; it's a platform powered by a data governor that has been cleansing and standardizing the in-flight workstream data from every delivery team.

When Sarah shows the plan for Project Titan, David sees data he can trust. He sees the real-time capacity of his team and the real-time progress of every other project in the portfolio.

More importantly, the system provides a safety net. David can use a “what-if” analysis to model the impact of loaning out his engineer. He can see that if a crisis hits his own project in three months, the system will allow him to make a data-driven case to get the resources he needs back.

The conversation is no longer a political negotiation based on fear and mistrust. It's a data-driven discussion about trade-offs and probabilities. David is no longer being asked to take a blind risk; he's being asked to be a partner in a transparent, trustworthy system.

In this world, he might just say "yes."

Conclusion

Stop trying to fix your leaders. Fix the broken system that forces their hand. The problem isn't a lack of willingness to collaborate; it's a lack of trust. And in the enterprise, trust begins—and ends—with the data.

Please contact us to continue the conversation and watch a demo.


Frequently asked questions

Is resource hoarding a sign of a toxic corporate culture or bad leadership?

Not necessarily; it is often a rational response by smart leaders to a faulty system built on untrustworthy data.

How do psychological principles like "loss aversion" affect a manager’s willingness to collaborate?

Managers fear the certain pain of losing a key staff member more than they value abstract, potential future gains.

Why are traditional "team-building" exercises ineffective at mitigating siloed approaches to resource management?

They fail to address the underlying architectural problem: a lack of real-time, shared data that leaders trust.

What is the most effective way to encourage leaders to share their best talent?

Create a transparent system with "what-if" modeling so leaders can weigh among trade-offs and see the impact of their decisions.


Sources and Further Reading

  • Loss aversion: Daniel Kahneman and Amos Tversky, "Prospect Theory: An Analysis of Decision under Risk," Econometrica, vol. 47, no. 2, 1979, pp. 263–91.

  • Information asymmetry: George A. Akerlof, "The Market for 'Lemons': Quality Uncertainty and the Market Mechanism," The Quarterly Journal of Economics, vol. 84, no. 3, pp. 488–500, 1970.

  • The prisoner's dilemma: William Poundstone, “Prisoner's Dilemma,” Anchor, 1993.

  • Systems thinking: Peter M. Senge, “The Fifth Discipline: The Art & Practice of The Learning Organization,” Doubleday/Currency, 1990.