The Ringelmann Effect on GCC Scale

Every GCC business case assumes that capability scales with headcount. A century-old experiment suggests otherwise.

In 1913, French agricultural engineer Max Ringelmann measured how hard people pulled on a rope, alone and in groups. As later reported, two people pulled at 93% of their solo effort, three at 85%, and groups of eight at just 49%. Add more people, and the contribution of each individual becomes harder to see.

India now hosts over 2,100 GCCs employing approximately 2.36 million professionals. The question enterprise leaders should ask is not how many people their GCC has, but how much of each person's effort reaches the outcome that matters.

What the research actually measured

Ringelmann's findings point to two distinct challenges.

The first is coordination loss. People work at slightly different moments, priorities diverge, and some effort is lost in synchronisation. The second is motivation loss, later associated with social loafing. When an individual's contribution becomes less visible within a larger group, effort can decline.

In 1974, Alan Ingham and colleagues demonstrated that coordination could not explain the entire effect. Participants believed they were pulling alongside others when they were actually working alone. Performance still fell, suggesting that motivational factors also matter. That distinction matters for GCCs. Coordination loss is largely an operating-model challenge. Motivation loss is partly a design challenge, and GCC structures can inadvertently create it.

The two-shore tax

In a GCC, coordination loss has a familiar name: the two-shore tax.

Every task that starts in one geography and finishes in another passes through handoffs, time-zone gaps and approval loops. Each handoff is a moment where teams are pulling at slightly different times. Add parallel management layers in headquarters and India, and decisions can travel across the organisation multiple times before work moves forward.

This tax compounds with scale. More people create more interfaces, more meetings to maintain alignment and more effort spent coordinating. Fred Brooks described a similar dynamic in software development: adding people to a late project makes it later. The coordination tax is real, but process improvements can contain it. The more difficult challenge lies elsewhere.

Organisational visibility

The same principle observed in social-loafing research operates one level higher. What psychology observes in individuals also appears structurally within organisations.

A GCC designed primarily to execute tickets often works toward outcomes owned elsewhere. Teams cannot always see their contribution reflected in the final business result because accountability sits outside the centre. As a result, effort naturally gravitates toward what is visible: tickets closed, SLAs met and utilisation reported.

The work gets done. The business does not move.

Nobody consciously decides to contribute less. Rather, the structure makes contribution harder to connect to business outcomes, and behaviour follows visibility.

The industry is already moving in a different direction. The Nasscom-Zinnov GCC Landscape Report 2026 finds that nearly 50% of India's GCCs now operate at a high maturity stage, and close to 75% could evolve into Portfolio or Transformation Hubs within five years. What separates these higher-maturity models is not size. It is ownership of outcomes rather than execution of tasks.

Why smaller can outperform

If coordination costs rise and contribution visibility falls as organisations grow, the largest GCCs are not automatically the most valuable. This challenges a common assumption that a larger centre is necessarily a more mature one. A focused centre with a clear mandate, short decision chains and direct visibility into business outcomes can generate greater value per person than a centre many times its size.

Scale remains important for breadth of capability. But headcount is an input, not an outcome. The measure that matters is how much of each person's effort reaches the business objective.

The problem is not scale. It is scale without visibility.

Large GCCs can create extraordinary value. But as organisations grow, the operating model must work harder to preserve three things that smaller teams often enjoy naturally: visible contribution, clear ownership and short decision paths.

Designing against the curve

Research on reducing social loafing is remarkably consistent. A 1993 meta-analysis by Karau and Williams found that effort losses diminish when individual contributions are identifiable and when the work itself is meaningful.

Translated into GCC design, four practices follow:

1. Give the centre an outcome, not a queue. Ownership of a product, process or business metric makes contribution visible.

2. Build pods, not pyramids. Small cross-functional teams with end-to-end ownership reduce handoffs and make accountability clear.

3. Collapse the decision distance. Leadership that can make decisions in India removes delays that drain both time and effort.

4. Measure outcomes, not activity. Utilisation and ticket counts measure motion. Business outcomes measure impact.

Headcount scales coordination. Ownership scales effort.

The next phase of GCC growth will not be decided by who builds the biggest centre. It will be decided by whose people can see their contribution reach the outcome.

For enterprise leaders, that changes the first question to ask of any GCC. Not how big it is, but how much of it is pulling.

‍