By Deep Work Club · Last updated: October 2026 · Reading time: 7 minutes
Your team has doubled, the funding round has closed, and yet everything lands on your desk again. Many leaders at scale-ups have to learn how to delegate a second time in hypergrowth: what worked with five people no longer holds with fifteen. This article explains why more people don't automatically mean more speed, what the Ringelmann effect has to do with it and how levels of delegation help.
Key takeaways
Growth creates coordination work. With five people there are 10 possible communication lines, with ten there are 45, with twenty 190. A large share of them runs through the manager.
The Ringelmann effect: Groups achieve less than the sum of their members, through coordination and motivation losses (Ringelmann, 1913; Ingham et al., 1974).
Structures don't grow on their own. In our work with leaders and people teams, missing structure for growth is a topic that comes up again and again, for leaders and people leads alike.
Delegation is not either-or. The seven levels of delegation from Management 3.0 (Jurgen Appelo) range from "I decide and tell you" to "you decide on your own."
The 80 percent rule is a rule of thumb, not a study: hand off what someone else can do about 80 percent as well as you.
Why do you become the bottleneck again as the team grows?
You become the bottleneck again during growth because the number of coordination needs grows faster than the team, while decision paths and responsibilities stay the same. What used to get settled in a hallway chat now needs structure. Without it, every open question lands with the person who has the overview: you.
Many leaders in growing teams describe it like this:
"The team keeps getting bigger, but the structures can't keep up."
In our work with leaders and people teams, this pattern comes up again and again, including with people leads looking for development for their company's leaders. Two closely related patterns go with it: finding it hard to let go and being stuck in operations. It often ends in the same realisation: the bottleneck is me.
What is the Ringelmann effect?
The Ringelmann effect describes how output per person falls as a group gets bigger. Twice as many people don't achieve twice as much. Part of the loss comes from coordination costing time and friction, part from individuals feeling less responsible within the group.
In the 1880s, the French agricultural engineer Max Ringelmann had people pull and push loads alone and in groups and measured the force. Group performance fell short of the sum of individual performances, which Ringelmann attributed mainly to coordination losses. That is how David Kravitz and Barbara Martin (1986) describe it after rediscovering and summarising his original article, published in 1913.
Alan Ingham and colleagues tested this experimentally in 1974. Output per person dropped clearly when one person became two or three, and barely after that. It also dropped when participants pulled alone but believed they were pulling with others. So part of the effect is motivation, not just coordination.
Rope pulling is not knowledge work, so these experiments are an illustration, not proof about your team. But the picture fits a calculation Fred Brooks described for software teams in 1975 in The Mythical Man-Month: the number of possible communication lines grows with n × (n − 1) / 2.
Team size | Possible communication lines |
|---|---|
5 | 10 |
10 | 45 |
15 | 105 |
20 | 190 |
If a team doubles from 10 to 20 people, the number of possible communication lines grows to more than four times as many. Without clear ownership, the manager becomes the switchboard. What keeps teams fast anyway is covered in the article on what makes a high performing team.
Why is letting go so hard?
Letting go is hard because in the short term it feels like losing control, and because you would probably do the task faster and better than the person taking it over. But if you only hand off what others can already do just as well, you practically never hand off anything.
A sentence we hear again and again in our work with leaders describes the reflex after handing something off:
"The moment it's handed off, I want to go back and control all of it."
Behind this is often the curse of knowledge: if you know a topic very well, you underestimate how much context others are missing and mistake bad handovers for bad performance. More on this in the pillar article Your First Leadership Role at a Startup: The First 90 Days.
In hypergrowth, there is the time crunch on top. Many leaders are still fully involved in day-to-day work on the side. The wish to pull out of it and hand off more is clear anyway.
What are the levels of delegation?
Delegation is not a yes-or-no decision but a scale. A widely used model for it is the seven levels of delegation from Jurgen Appelo's Management 3.0. They range from "I decide alone" to "you decide alone" and make visible who has the final say on which decision.
Appelo describes the model in his book Management 3.0; as a team exercise it is called "Delegation Poker". He recommends applying the levels not to individual tasks but to decision areas, such as hiring, choosing tools or sprint priorities.
Level | Name | What it means | Scale-up example |
|---|---|---|---|
1 | Tell | You decide and announce it. | Budget limit for the quarter |
2 | Sell | You decide and convince the team. | New reporting rhythm |
3 | Consult | You gather input, then you decide. | Shaping a new role on the team |
4 | Agree | You decide together. | Team goals for next quarter |
5 | Advise | You advise, the team decides. | Choosing a new tool |
6 | Inquire | The team decides, you ask about it afterwards. | Splitting tickets in the sprint |
7 | Delegate | The team decides on its own. | Format of team retros |
A lot of frustration in delegation comes from manager and team silently assuming different levels. You think "level 5, I'm only advising"; your team hears "level 3, they'll decide in the end anyway." Say the level out loud and revisit it every few months.
What is the 80 percent rule in delegation?
The 80 percent rule is a practical rule of thumb, not a scientifically established finding: hand off a task when someone else can do it about 80 percent as well as you. The missing 20 percent is the price for freeing up time for work only you can do, and for someone else to learn.
As a question: what would you hand off right away if you were sure it would turn out 80 percent as good? If something comes to mind quickly, what you lack is not insight but trust in the handover.
For this to work, you need two things:
Clear quality criteria. "80 percent" doesn't mean "somehow." Describe what a good result looks like.
Agreed checkpoints instead of checking afterwards. Decide in advance when you will look at the work, instead of reviewing everything at the end.
Three things for this week
Bottleneck log: For one week, note every request that lands with you and waits on you.
One decision, one level: Pick one decision area from the log and agree with your team which level of delegation it sits at from now on.
One 80 percent candidate: Hand off a task someone can do 80 percent as well as you, with quality criteria and a fixed checkpoint.
Frequently asked questions
How do I learn to delegate as a manager? Start with a task someone can do about 80 percent as well as you. Describe the result you want, agree on checkpoints and say out loud who decides. You don't learn delegation in theory but through many small handovers.
What is the Ringelmann effect? The finding that output per person falls as a group gets bigger. Max Ringelmann observed it in pulling and pushing experiments in the 1880s. Later experiments (Ingham et al., 1974) showed that both coordination losses and motivation losses are behind it.
What are the seven levels of delegation? A model from Jurgen Appelo's Management 3.0: Tell, Sell, Consult, Agree, Advise, Inquire and Delegate. It ranges from "the manager decides alone" to "the team decides alone" and helps you set, for each decision area, who has the final say.
Why is my team getting slower even though it's growing? Because the number of possible communication lines grows faster than the team: with 10 people there are 45, with 20 already 190. Without clear ownership and decision paths, coordination lands on the manager.
In summary
When your team doubles, coordination work grows faster than headcount. You don't get out of the bottleneck by working longer days but through structure: clear levels of delegation for decision areas, handovers with quality criteria and the courage to let 80 percent results stand.
In short: if you decide everything yourself in hypergrowth, you slow down the very growth you are supposed to organise.
How others solve it is what you hear in the Leadership Circle. Why peers often help more than another book is covered in the article on peer learning for leaders.
Don't want to figure this out alone? In the Leadership Circle, up to ten leaders from Berlin startups and scale-ups meet regularly to exchange experiences, facilitated by Lea Mersch. Book a free intro call
Sources
Ringelmann, M. (1913). Recherches sur les moteurs animés: Travail de l'homme. Annales de l'Institut National Agronomique, 2e série, 12, 1–40.
Kravitz, D. A., & Martin, B. (1986). Ringelmann rediscovered: The original article. Journal of Personality and Social Psychology, 50(5), 936–941. doi:10.1037/0022-3514.50.5.936
Ingham, A. G., Levinger, G., Graves, J., & Peckham, V. (1974). The Ringelmann effect: Studies of group size and group performance. Journal of Experimental Social Psychology, 10(4), 371–384. doi:10.1016/0022-1031(74)90033-X
Brooks, F. P. (1975). The Mythical Man-Month: Essays on Software Engineering. Addison-Wesley.
Appelo, J. (2011). Management 3.0: Leading Agile Developers, Developing Agile Leaders. Addison-Wesley.
Management 3.0. Delegation Poker. management30.com/practice/delegation-poker