The Management Mistakes Founders Make Right Around Employee Number 10

The first sign is usually a Slack thread that nobody owns. Three people have opinions, the founder is tagged twice, and a decision that would have taken five minutes across a table now takes four days and a meeting.

Nothing about the company has broken. It has simply crossed the size at which a founder can no longer hold every conversation in their head. Most first-time founders hit that wall somewhere around ten people, and the habits that made them effective at five are exactly the ones that start slowing everyone down.

The mistakes below are common because they feel like strengths from the inside. Each one has a fix that costs a few hours, not a reorganization.

Mistake one: staying the router for every decision

At five people, the founder in the middle of everything is a feature. Information moves fast because it all passes through one person. At ten, that same person becomes a queue. Work waits for a reply, and the team learns that nothing is final until the founder weighs in.

The fix is to hand over outcomes, not tasks. Instead of approving each step of a hiring process, give one person the goal (a signed offer for a specific role by a specific date), the budget range and the constraints, then step back. Write down which decisions you are keeping. A short list of founder-only calls, such as pricing changes, senior hires and anything that touches the bank account above a set amount, frees everything else to move.

Mistake two: assuming everyone knows what good looks like

Early employees absorb expectations by sitting next to the founder. New hires at a ten-person company often have no such access, especially if the team is remote. They guess at what matters, and they guess differently.

Every role should have a one-page document that says what the person owns, what success looks like in 90 days and a year, and who they go to when they are stuck. It feels bureaucratic to write. It is far cheaper than discovering at month six that an engineer thought their job was shipping features while you thought it was keeping the system stable.

Mistake three: skipping one-on-ones because everyone talks all day

Founders often argue that weekly one-on-ones are unnecessary in a small team where people chat constantly. Group chatter is not the same as a private, recurring slot where an employee can raise a problem before it hardens into a resignation.

Keep them short and keep them owned by the employee. Thirty minutes, an agenda the report writes, and a standing question about what is getting in their way. If you have more direct reports than you can meet weekly, that is a signal you need a manager layer, not a reason to cancel the meetings.

Mistakes four and five: pay and promotions decided on instinct

The first ten hires are often priced individually, based on who negotiated hardest or who the company needed most that month. That works until two people doing similar jobs compare notes, which they eventually do.

Before hire eleven, sketch simple compensation bands: a salary range and an equity range for each level of each function. They do not need to be precise. They need to exist, so the next offer is anchored to something other than mood. If your state requires pay ranges in job postings, the bands also save you from scrambling when you write the listing.

When the first management role opens, the reflex is to promote whoever is best at the work. Sometimes that is right. Often it removes your strongest engineer or salesperson from the work they love and hands them a job they have never trained for.

Ask the candidate directly whether they want to manage people, and describe the job honestly: more meetings, less hands-on output, responsibility for someone else's growth and occasional hard conversations. Offer a way back to an individual role with no loss of face if it does not fit after six months.

What to do this month

Write your list of founder-only decisions and share it with the team. Draft one-page role documents for every current position, starting with the ones that have changed most since the person was hired. Put a weekly or biweekly one-on-one on the calendar with every direct report. Sketch compensation bands before the next offer goes out.

None of this turns a ten-person startup into a corporation. It does stop the founder from becoming the reason the company slows down, which is the most common and most fixable problem at this stage.