What it means
At its heart, this concept describes a clash between individual reward and collective responsibility. When a resource belongs to everyone, no single person bears the full cost of consuming it.
Imagine a shared office printer. One department prints massive training manuals because ink and paper cost them nothing directly.
They get the immediate benefit, while the shared expense and eventual empty cartridge become a problem for the whole company. In business, this dynamic appears frequently in shared budgets, internal talent pools, and IT infrastructure.
If different teams pull from a single, unallocated resource pool without coordination, the strongest or loudest team usually takes the most. This leaves other departments short of what they need to operate effectively, damaging overall company performance.
For non-finance managers, recognising this pattern helps prevent hidden inefficiencies. When departments compete for unmanaged shared assets, trust breaks down and waste increases.
Managers must spot where individual incentives clash with group survival. To fix these issues, organisations introduce boundaries, clear usage tracking, or internal charging mechanisms.
By attaching a cost or a quota to shared assets, companies align personal department goals with the long term health of the business. Imagine a shared neighbourhood pie.
If everyone cuts huge slices for themselves to get the most value right now, the pie is gone in minutes, leaving half the neighbours hungry.
In practice
Real-world examples
Example 1
Three startup co-founders share a company credit card for travel. Because individual trips do not impact their personal salaries, each books a $4,000 business-class flight instead of a $1,200 economy seat. In one quarter the extra spending takes $8,400 out of a $60,000 seed cash reserve, a 14% drop that nobody decided on. A simple per-trip approval limit would have stopped it.
Example 2
Four retail stores share one regional delivery van. Each store manager books it for minor local drop-offs every day, adding fuel and wear that nobody tracks. The van is constantly broken down and unavailable for major wholesale dispatches, and one missed delivery costs the group a $6,000 order. Because no store pays for the repairs separately, nobody has a reason to hold back.
Example 3
An advertising agency shares a pool of five graphic designers among ten account directors. Every director demands top priority and asks for 30 hours a week, creating demand of 300 hours against a capacity of 200 hours. The design team burns out and deadlines are missed. The agency loses a client because quality slips, even though every director acted sensibly for their own accounts.
Think of it
Imagine a shared neighbourhood pie. If everyone cuts huge slices for themselves to get the most value right now, the pie is gone in minutes, leaving half the neighbours hungry.
Formula
Calculation
Private Benefit > (Shared Cost / Number of Users)
Example: If a manager prints a 500-page report worth $50 to their project, but the paper and ink cost $100 shared across ten teams, their personal cost is only $10. Since $50 is greater than $10, they print it, despite a net loss of $50 for the company ($50 benefit minus $100 real cost).
Now add up the effect. If each of the ten teams makes the same decision once, the company spends 10 x $100 = $1,000 and receives 10 x $50 = $500 of benefit, a total loss of $500. If each team were instead charged the full $100 cost of its own report, the $50 benefit would no longer justify printing, and the waste would stop.Case study
Seen in the real world
This is a fictional, illustrative scenario. At Apex Consulting, four distinct divisions shared a single operational software budget of $20,000 per year. Initially, this arrangement worked well, but behaviours soon shifted. The marketing team began purchasing expensive niche add-ons for their specific campaigns, knowing the cost was absorbed by the general pool.
Soon, sales and HR followed suit, buying their own specialised tools. By August, the entire $20,000 was completely exhausted, leaving no funds for essential system security updates required by the IT department. Apex suffered a minor data outage that cost $8,000 in emergency contractor fees to fix. To resolve the crisis, the finance director abandoned the shared budget model.
She allocated $5,000 directly to each division's individual P and L statement. If a division wanted extra software, they had to fund it from their own savings. Unnecessary spending stopped immediately, the core system remained fully funded, and the $8,000 outage bill was never repeated. Each division head also began asking whether a tool was truly needed before buying it, because the money was now visibly their own.
Watch out
Common mistakes
- Assuming that giving people free access to a resource encourages cooperative behaviour.
- Failing to track small, cumulative resource drains until a major shortage occurs.
- Blaming employees for being selfish instead of fixing the broken system design.
Questions
People also ask
Is this an accounting rule?
No, it is an economic and behavioural theory that explains how people use shared assets.
How can managers stop this from happening?
By introducing clear limits, quotas, or internal billing so users feel the cost of consumption.
Does this only happen with physical goods?
No, it frequently happens with intangible resources like staff time, budgets, and IT bandwidth.