Why does work stall as a team grows?

When a small team is firing, work flows by instinct: everyone sees everything and gaps get filled before anyone notices. As the team grows, the work outgrows the informal structure holding it together, so things start to wait. It is rarely that people try less. It is that the work needs structure that was never needed at five people and is essential at fifteen.

Where does work most commonly get stuck?

In five recognisable places: in the gap between people where handovers are undefined, waiting on a decision only one person can make, lost in an undifferentiated communication stream, going around in loops because "done" was never defined, and everything routing back to the founder because no one else has a clear lane.

Will telling everyone to communicate better fix it?

No. Asking people to be more proactive and careful only works until the next busy week, and it quietly tells a capable team that the problem is them. The work is stalling in gaps that informal coordination used to cover and no longer can. You clear it by building the structure once, not by reminding people to try harder every week.

How do I stop work routing back to me?

When ownership and decisions are unclear, the safe default for the whole team becomes "check with the founder," which turns one person into the place all work quietly queues. The fix is the sum of the others: clear owners, clear decision rights, and explicit handovers, so the work has somewhere to go other than back to the top.

Where Work Gets Stuck in a Growing Team, and How to Get It Moving

As a team grows, work starts to stall in predictable places. None of them are about people trying less. Each one is a gap in how the work is structured, and each has a clear fix.

When a small team is firing, work flows almost by instinct. Everyone can see everything, context is shared in the air, and the gaps get filled before anyone notices them. Then the team grows, the work multiplies, and the same instinct stops covering the distance. Things start to wait. Tasks sit half-finished. The same questions come around again. It feels like the team slowed down, but usually the team is working just as hard. What changed is that the work outgrew the informal structure holding it together.

The good news is that work tends to stall in a handful of recognisable places. Once you can name where, the fix is rarely "push harder." It is almost always a piece of structure that was never needed at five people and is essential at fifteen.

The places work commonly stalls

1. In the gap between people

One person finishes their part and assumes the next person has picked it up. The next person never saw it land. The work sits in the handover, invisible, until it surfaces late as a problem. This is not carelessness. It is that the handover was never defined, so nobody owns the moment of passing it across. The fix is making handovers explicit: who passes what to whom, and how they know it has been received.

2. Waiting on a decision

The work is ready to move but cannot, because it needs a call that only one person is allowed to make, and that person is busy. Multiply this across a week and a surprising amount of the team's time is spent waiting rather than working. The fix is clear decision rights: stating which decisions belong to whom, and the criteria for making them, so most calls no longer need to travel up and back.

3. Lost in the conversation

The urgent, the trivial and the important all arrive on the same channel, so nothing carries the right weight. A key decision gets buried in a chat thread. A request is missed in the scroll. People are not ignoring things, they are drowning in an undifferentiated stream. The fix is channel structure: the right kind of message in the right place, with decisions recorded somewhere they can be found later.

4. Unclear what "done" looks like

A task goes out, comes back, and is not quite right, so it goes around again. Each loop costs time and goodwill. The cause is usually that the outcome was never defined clearly enough at the start. The fix is scoping work properly before it begins: what done looks like, what good is, and what resources to use, so it can be finished in one pass.

5. Everything routing back to the owner

When ownership and decisions are unclear, the safe default for the whole team becomes "check with the founder." That turns one person into the place all work quietly queues, not because they want control, but because the structure never gave anyone else a clear lane. The fix is the sum of the others: clear owners, clear decision rights, clear handovers, so the work has somewhere to go other than back to the top.

Where is your work stalling?

Tick the ones you recognise from this week:

Something fell through the gap between two people.
A task sat waiting on a decision only one person could make.
An important message got lost in a chat thread.
Work came back needing redoing because the brief was unclear.
The default answer to "who handles this?" was still the founder.

The boxes you ticked point straight to which piece of structure is missing.

Why "just communicate better" doesn't clear it

The instinct is to ask everyone to be more proactive, more careful, more communicative. But asking people to compensate harder for a missing structure only works until the next busy week, and it quietly tells a capable team that the problem is them. It is not. The work is stalling in the gaps that informal coordination used to cover and no longer can. You clear it by building the structure once, not by reminding people to try harder every week.

Build the structure that keeps work moving

This is what Mobilise installs. It builds the task-scoping and ownership frameworks so every piece of work has a clear owner and a clear definition of done, the communication structures that put the right message on the right channel, and the decision-making models that let most calls happen without travelling back to the top. It is delivered across three tiers: Ignite to lay the foundation, Embed to practise it live on your real work, and Amplify to roll it out across the whole organisation. The result is work that keeps moving without someone having to chase it. Or explore all three TechAble services.