Why adding people makes projects worse

The team is under-resourced. The obvious answer: add people. Five become ten. And then, paradoxically, progress slows. Mistakes accumulate. And eventually something serious happens that everyone saw but no one reported.

This is not about effort or motivation. It is a structural phenomenon with a structural explanation.

The RBM paradox: adding supply that generates more demand

RBM (Resource Balance Model) distinguishes between the supply added by new members and the demand their arrival creates. When five people join a team of five:

• Communication paths multiply non-linearly.
• Coordination, clarification, and alignment become full-time activities.
• Individual cognitive supply is increasingly consumed by the work of managing relationships — leaving less for the actual task.

The bottleneck is not the number of people. It is the structural organisation of their roles.

The RSM problem: roles that dissolve into ambiguity

In a team of five, each person has a clear functional identity — they know what they own, and so does everyone else. When headcount doubles without role clarity, something critical happens: gaps appear. Work exists that belongs to no one.

SANA OS calls this Role Deficit. In a Role Deficit state, problems that surface in the gap are processed by the individuals who encounter them through the Proximity Rule: "If I touch this, I own it. If I stay quiet, it belongs to the system." Staying quiet is the rational survival choice.

Why concealment is a rational response, not a character flaw

When a problem appears in an ambiguous structural space:

• Layer A (self-protection): "If I flag this and it turns out to be my fault, the consequences fall on me."
• Layer B (belonging): "Everyone else seems to know what they're doing. Maybe I'm missing something — I'll wait and see."

These are not signs of bad character. They are the rational outputs of a structural environment that has made honesty too costly and ambiguity too safe.