Chapter 16: Zero-Sum Hoarding & Cross-Team Generosity

Last updated on 
Share
Chapter 16: Zero-Sum Hoarding & Cross-Team Generosity

The Toddler’s Instinct & Organizational Reciprocity

Observe toddlers in a sandbox and you will witness raw, unvarnished greed: children snatching toys they have no intention of using, simply to keep others from having them. Functional socialization teaches children to share so they can operate inside a community and count on mutual support when trouble arises.

Adult managers often retain that same primitive impulse. Fearing future scarcity, they hoard idle engineers, hide extra task backlogs, and isolate internal tools behind team silos.

Generosity is not foolish sacrifice. As a project manager, you are the steward of your team’s capacity and commitments. Building long-term organizational trust requires active cross-team support—because no project operates in total isolation forever.

Tactical Generosity: Sharing Your Slack

When your project has operational buffer, actively assist neighboring teams:

  • Capacity Balancing: If a neighboring team runs out of work while your backlog is overflowing, share tasks to optimize overall organizational throughput.
  • Talent Loans: If another project faces an acute deadline crisis and your milestones contain slack, lend a developer for a week or two.
  • Knowledge Sharing: Distribute internal tools, automation scripts, and technical frameworks to other teams unless keeping them proprietary is your sole operational mandate.

Assisting colleagues builds institutional goodwill. When your project inevitably encounters its own crisis, that accumulated credit determines whether neighboring teams rush to your rescue or watch you founder.

Generosity vs. Sacrifice: The Hard Boundary

Sharing slack capacity must never be confused with surrendering baseline commitments. If helping another team threatens your budget, client SLA, or delivery quality, say no.

  • Immediate Transparency: If you lack the capacity to assist, issue an immediate, unambiguous refusal.
  • The Danger of False Hope: Never make soft promises or offer conditional commitments you cannot guarantee. Leaving a colleague with false expectations prevents them from seeking alternative solutions, turning a minor resource shortage into a catastrophic failure.

Rule of Thumb: If you can help without damaging your delivery baseline, help immediately. If you cannot, refuse cleanly and transparently.