The challenges of scaling management as a team grows

A row of jagged grey limestone peaks above a green slope, under a deep blue sky with thin streaks of cloud

There is a size at which a team that was working well starts to work less well, and I think the hard thing is that nothing visible changes. The people are the same. The work is the same. What changes is that the manager's attention, which was enough for eight people, is being spread across fifteen, and attention does not scale.

I am not sure there are answers to all of these challenges, but they are worth seeing early.

Attention gets rationed

At eight, a manager can know what everyone is working on, have a real one-to-one with each person, and notice when someone is struggling. At fifteen, the arithmetic no longer works. The one-to-ones get shorter, the manager knows less, and the noticing happens later.

I think the honest response is to decide, on purpose, what the manager will stop doing, rather than doing all of it a little worse. That is uncomfortable because every one of those things felt like the job, and some have to become someone else's.

Context gets expensive

On a small team, context is free because everyone hears everything. As the team grows, the manager becomes the place context collects, and passing it on becomes a task in itself.

I have come to believe the fix is writing things down where the team can find them before anyone asks. It feels slower than telling people. It is the only thing that scales.

Decisions wait on one person

A growing team generates more decisions than one person can make, and if the manager still makes all of them, they queue. The team just gets slower, and the manager, seeing the slowness, works harder, which lengthens the queue.

The challenge is growing people who can decide. I think that means naming leads, giving them real decisions rather than recommendations, and accepting that they will decide some things differently. The alternative is a team whose speed is capped by one calendar.

Knowing when to split

At some size, the right answer is two teams rather than one bigger one, and the hard part is that the moment is never obvious. Splitting a team that still works creates a seam, a second set of ceremonies, a boundary to manage.

The signal I watch for is whether the team still shares a purpose that fits in a sentence. When the sentence needs a semicolon, when the team is really two groups who attend the same standup, the split has already happened and only the structure has not caught up.

Where this stops being true

A team with strong leads in place, or work that naturally divides, can grow further before any of this bites. And some of what I have described is specific to a manager who started hands-on and is reluctant to let go, which is to say, to me. How soon the challenges arrive depends on how willing the manager is to be less central.

Photo source: https://photos.robertstowe.com/dolomites