How to structure a growing team: the thresholds at 15, 50 and 150 people

Below fifteen, everyone reporting to one person works because the owner still has direct context on every task. Past it, one-to-ones stop happening and approvals queue behind a single calendar.

The first move is two or three team leads over functions that already exist — field, admin, sales — rather than a new layer of managers hired from outside. Promote the person people already ask.

At fifty, informal coordination fails. You need named department owners, written responsibilities and a chart that exists somewhere other than the owner's head. This is the point where an out-of-date chart starts costing money: onboarding takes longer, approvals route to the wrong person, and two teams do the same work.

Spans of control land best between five and nine direct reports for managers of professionals, and can run wider — twelve to fifteen — for uniform frontline work with a strong lead.

Past roughly 150, nobody knows everybody. Departments need their own operating rhythm, and the chart becomes a genuine navigation tool rather than a reference. Expect three to four layers between the newest hire and the owner; more than five layers in a company this size usually means a manager was created to solve a title problem rather than a workload one.

Span too wide: any manager with more than twelve direct reports of mixed function. Span too narrow: a manager with one report — usually a title, not a role. Too deep: more than five layers under 200 people. Orphans: anyone whose manager field is blank other than the owner.

Orgline flags orphans, loops and duplicates after every import, so the structural problems surface as a list rather than as something you have to spot by eye. Keeping the chart current covers the maintenance routine.