The Team Grew, Why Did Work Slow Down?
“The team grew but work slowed” is something every growing business says at some point. Work that ran fast with five people slows with ten — and logic rebels: more hands, less work? 🐢
Short answer: people increased, decision points didn’t. Ten people still wait at the same door; same door, twice the queue. What slowed isn’t the work but the time it takes a decision to reach it.
Below: the mechanism, the three growth thresholds, how to measure the slowdown, the false fixes and the real one. 🔍
How does the mechanism work?
The team grew but work slowed is an arithmetic problem.
Why do newcomers ask more?
Because there’s no written rule and they can’t reach the knowledge in the old hands’ heads. A new person is the most frequent asker in a disorderly business — not because they’re bad, but because information doesn’t reach them.
The three growth thresholds
BU BÖLÜMÜN ÖZETİ
- First threshold: the owner can’t see everyone
- Second threshold: old hands managing newcomers
- Third threshold: the owner can’t leave the floor
The slowdown always happens at the same points.
First threshold: the owner can’t see everyone
Usually at five to seven people. The owner no longer knows what everyone is doing; not knowing, they start asking and checking more. As checking rises, decisions slow. 👁️
Second threshold: old hands managing newcomers
At ten to fifteen. The experienced employee is in effect a manager but has no authority; they still carry everything to the owner. There’s a layer in the middle but decisions don’t pass through it — they only stop by. 🪜
Third threshold: the owner can’t leave the floor
Toward twenty. The owner is still approving materials where they should be making growth decisions. The business grew; the owner’s job didn’t — the bottleneck logic sits in the bottleneck article. 🪑
What are the false fixes?
BU BÖLÜMÜN ÖZETİ
- Hiring more people
- Holding more meetings
- Buying software
The first three things that come to mind, none of which work.
Hiring more people
Adding people to a queue lengthens the queue. Every person hired without adding a decision point brings the owner a few more questions a day. 👥
Holding more meetings
A meeting isn’t a decision point; if the decision still sits with the owner, a meeting only makes the waiting collective. Everyone waits for the owner in the same room. 🗓️
Buying software
It doesn’t speed up a disorderly decision; it makes it visible. If every task entering the task tool still waits for the owner’s approval, the screen changed, the queue didn’t. 💻
How is the slowdown measured?
Not a feeling; two numbers.
Waiting time and question count
Of the time from a job starting to finishing, what share is waiting? And how many questions reach the owner a week? Tracked alongside headcount, these two make the picture clear: if waiting share and question count rise as people are added, no decision point has been added. A growth decision made without measuring lengthens the queue by guesswork. 📊
What’s the real fix?
Adding decision points, not people.
Multiplying decision points
A decision map: which decision belongs to whom, up to which limit. A ten-person team should have three decision points — the owner, the experienced employee, and the written rule. The rule is the point for decisions applied without asking anyone, and it’s the fastest. 🗺️
Giving the old hand authority
Written authority for the person already managing in practice: which decisions end with them. That’s both cheaper and faster than hiring a manager, because the person already knows the work; the only thing missing is permission. Timing sits in the manager article, all questions on the consulting page. 🔑
📝 Field Notes
A business had gone from five to twelve people in six months and delivery times had stretched. The owner said “the newcomers are slow”. We looked: the most experienced employee was managing three people in practice but had not a single authority, carrying everything to the owner. They were given three lines of written authority. Delivery times returned to normal — without anyone being hired. What was missing wasn’t a person; it was the authority of the layer in the middle. 🪜
📖 Quick Glossary
Decision point: where a decision gets made and ends. Growth threshold: the headcount the current system can’t carry. De facto manager: an experienced employee managing without authority. Written authority: the record of which decision ends with whom.
⚡ Quick Summary
People increased, decision points didn’t. 🐢 In a small team proximity hides disorder. Three thresholds: the owner can’t see, the old hand manages without authority, the owner can’t leave the floor. False fixes: people, meetings, software. Real fix: multiply decision points.
🎯 Next Step
Let’s find which threshold you’re at and who your de facto manager is: the quote page. Scope on the consulting page. 🔍
Frequently Asked Questions
Sık Sorulan Sorular
Because everyone was in the same room as the owner; a question got asked, an answer came in seconds. Even with no written rule there was no problem, because the distance was short. In a small team disorder is invisible, because proximity compensates for it. 🏠
Distance grew, questions grew, the owner stayed the same. Five people generated twenty questions a day; ten generate forty; the owner can’t get to all forty, and a queue forms. What grew isn’t the work, it’s the waiting. ⏳
No, the hiring was right; what was missing was multiplying decision points before the hiring. When the order is reversed, every new person becomes a load on the owner. Adding rules before adding people makes growth cheaper.
If authority is written to the role rather than the person, resentment falls: “these decisions end in this role.” If they’re already managing in practice, the team knows; making it written reduces uncertainty rather than adding to it. The problem isn’t giving authority but not writing its limit.
Once the decision map exists it’s very useful; it makes rules and checkpoints visible. Software bought before the system is built carries the broken system onto a screen. Order: rule first, then tool.