Scaling 10 to 20: First Managers and Delegation Without Chaos
Somewhere between ten and twenty people, the founders stop being able to coordinate everyone directly. Meetings multiply, decisions queue up and people lose context. The fix is the first layer of management, introduced carefully so you gain coordination without losing speed.
TL;DR
- Signs you need managers: founders are a bottleneck for decisions, one-to-ones are slipping, and new hires lack context.
- Promote or hire people who want to manage, not only your best individual contributors.
- Define the manager's job: outcomes, hiring, feedback, and growth of the team, with clear decision rights.
- Keep the process light: weekly one-to-ones, a short team ritual, and written priorities.
- Train new managers, and give them a way back if it is not for them.
What changes at ten to twenty
With ten people, the founders hold the whole system in their heads. At fifteen or twenty, they cannot. Symptoms usually appear in this order:
- Decisions wait for a founder who is in meetings.
- One-to-ones get skipped, so feedback goes stale.
- New hires take longer to become effective because context lives in conversations.
- People work on different priorities without noticing.
- The best people start to feel unmanaged or overloaded.
These are signs that coordination, not talent, is the constraint.
Decide who becomes a manager
Two common routes: promote from within, or hire an experienced manager. Each has risks.
| Route | Benefit | Risk |
|---|---|---|
| Promote an individual contributor | Knows the product and culture, earns trust | May lack management skills, loses a strong builder |
| Hire an experienced manager | Brings habits and frameworks | May not fit the culture, unfamiliar with the product |
Before you promote someone, ask whether they want to manage and whether they show the early signs: they help teammates unstick, give clear feedback, and care about outcomes more than personal output. Offer a trial period and a clear way back to individual work if it is not a fit. Where the role is mainly technical direction, consider a tech lead without direct reports.
Write the manager’s job
Many first managers fail because nobody defined the role. A short description should cover:
- Outcomes the team owns, written as results.
- People: hiring, feedback, development and addressing performance issues.
- Decisions they can make alone, ones they consult on and ones they escalate.
- Communication: how they keep the founders and the team informed.
A simple frame for decision rights is: decide, consult, inform. Write down which of these applies to common decisions such as hiring, spending, scope changes and priorities.
A light operating rhythm
You need a few rituals that create coordination without paperwork.
| Ritual | Cadence | Purpose |
|---|---|---|
| One-to-one | Weekly, 30 minutes | Feedback, blockers, growth |
| Team sync | Weekly, short | Priorities, handoffs |
| All-hands | Monthly | Direction, results, questions |
| Planning | Quarterly | Set goals with OKRs |
| Written updates | Weekly | Shared context for the whole company |
Add one ritual at a time and drop any that do not earn their place.
Help new managers succeed
Most first-time managers receive no training. Give them:
- A mentor, ideally a founder or an experienced advisor.
- Reading or a short course on one-to-ones, feedback and delegation.
- A regular check-in with you about how the role feels.
- Permission to make mistakes early, with feedback.
Teach delegation explicitly. A common trap is that the new manager keeps doing the old job and neglects the team. Agree which tasks they hand off and to whom.
Handling the founders’ role
Founders also need to change. Resist overruling managers in front of their teams, and give guidance in private. If you keep making the decisions you delegated, managers will stop making them. When you disagree, explain why and agree how you will handle it next time.
What not to do
- Promote everyone’s favourite builder without checking interest or aptitude.
- Create layers too early. A manager with two reports and a full backlog of their own work is a hidden cost.
- Skip the definition of the job, so expectations differ.
- Add heavy process because a larger company uses it.
- Ignore performance issues. Small teams feel one weak fit strongly.
Signals it is working
- Decisions get made without a founder in the room.
- Team members can describe their priorities and why.
- One-to-ones happen and people value them.
- New hires become effective faster.
- Founders spend more time on strategy, customers and hiring.
Looking ahead
As you approach 30 to 50 people, structure matters more, as covered in scaling from 20 to 50. The early hiring decisions are in first ten hires, and the sales equivalent is in the founder-led sales handoff.
The first 90 days for a new manager
- Days 1 to 30: listen. Hold a one-to-one with every report, learn their goals and frustrations, and write down the team’s current priorities and risks.
- Days 31 to 60: set the rhythm. Start the weekly one-to-one and team sync, agree on two or three team outcomes with your own manager and make the decision rights explicit.
- Days 61 to 90: improve. Give each person clear feedback, fix the biggest process problem and delegate one task you used to do yourself.
Check in with the founders at the end of each month and ask what they would like more or less of. Do the same with the team.
Bottom line
Introduce managers when coordination, not talent, becomes the constraint. Choose people who want the role, define the job and decision rights, keep rituals light, support new managers and adjust the founders’ own behaviour. Done well, the first managers multiply the speed of the team instead of slowing it.
Frequently Asked Questions
When should a startup hire its first manager?
Often between 8 and 15 people, when a founder directly manages too many and quality of feedback or speed of decisions suffers. Look at the symptoms, not only the headcount.
Should the best engineer become the engineering manager?
Only if they want it and show the aptitude. Management is a different skill from building. Some strong individual contributors are better as technical leads with no direct reports.
How many direct reports should a manager have?
A common range is five to eight, depending on seniority and how hands-on the manager remains. New managers often do better at the lower end while learning.
How do I avoid bureaucracy?
Add the minimum process that solves a specific problem, write it down, and review it each quarter. Remove anything that nobody can explain a benefit for.
