The Ringelmann Effect
"As a group grows, each member pulls less of their own weight."
"As a group grows, each member pulls less of their own weight."
When people work together on a shared, additive task, the group's total output grows more slowly than the headcount would predict. Each person added contributes, on average, less than they would working alone — more hands do not translate into proportionally more work.
Rated Empirical: grounded in studies or measurable evidence. The other 608.
Two distinct losses combine as the group grows. Motivation loss: individuals ease off in a group, expecting others to make up the difference or feeling their own contribution is dispensable and unnoticed. Coordination loss: even fully motivated members cannot perfectly synchronise timing and direction, so the combined force falls short of the sum of individual maxima. Both accumulate with size. The motivation component is what was later isolated and renamed social loafing.
The modern successor, named by Latané, Williams and Harkins (1979), who reproduced the effect with clapping and shouting and argued the decline reflected reduced individual effort, not merely coordination: a far better-studied framing than Ringelmann's original.
The economic cousin: individuals enjoy the group's output while under-contributing to it, overlapping directly with the motivation-loss account of the effect.
A proposed driver: as the group grows, individual accountability dilutes, so any one person feels less answerable for the outcome and eases off.
It is the founding observation behind the whole study of social loafing and a standing caution against assuming that adding people adds proportional output. It reframes group productivity as something that has to be engineered, through visible individual contribution and accountability, rather than assumed to scale with headcount.
The original data were thin and long obscure; Ringelmann's report was hard to locate for decades until Kravitz and Martin rediscovered it in 1986, and the widely quoted percentages descend mainly from Moede's 1927 secondhand account. Ringelmann's own design could not separate motivation loss from coordination loss. That separation is owed to Ingham and colleagues (1974), and the generalisation and naming to Latané and colleagues (1979). The effect is not universal, either: some evidence suggests people with prior team-sport experience may not show it. It is a genuine foundational finding whose specific original figures should be cited with care.
It is not that people are simply lazy, nor that the whole decline is one thing: Ringelmann's data mixed coordination loss with motivation loss and could not tell them apart. The motivation component, social loafing, was isolated only by later, better-controlled work, and the famous percentages come largely from a secondhand 1927 report rather than Ringelmann's own paper.
Yes, as far as the evidence goes. The Ringelmann Effect is rated Empirical here: it rests on studies or measurements rather than on a saying.
Rated from three sources. 609 of the 1,116 entries carry this rating. How the scale works.
The best-known laws are the least likely to rest on measurement.
Nothing here is the formal negation of The Ringelmann Effect — these are the entry in this index that pulls the other way, so that following both at once forces a choice.
Named for Maximilien Ringelmann (1861–1931), a French agricultural engineer who found in rope-pulling and similar tasks that per-person force fell as more people pulled together. His data were gathered from the 1880s and published in 1913; the familiar percentage figures were popularised through Walther Moede's 1927 German write-up, and the original paper was rediscovered by Kravitz and Martin in 1986.
7 languages, as recorded on Wikidata. These are names the idea already goes by, not translations we made. The whole index by language.
Everything above traces to en.wikipedia.org and researchgate.net, three sources in all, one of them the original publication rather than an account of it. Nothing is written from memory, and the method is written down. Spot an error or a better source? Suggest a fix.