When Growth Quietly Increases Effort

There's a pattern that shows up across organisations at different stages of growth. The work expands. The team gets bigger. Revenue increases. And yet — something gets harder. Not just busier. Actually harder. Decisions slow down. Coordination takes more energy. The output per person quietly drops.

The situation we keep seeing

A team of five can move quickly and adapt without much overhead. A team of twenty needs more structure. A team of fifty needs even more. But the structure that's introduced often adds friction rather than removing it. Meetings replace decisions. Documentation replaces judgment. Process replaces trust.

The people doing the work feel it first. Tasks that used to take an afternoon start taking a week. Projects require sign-off from people who are too removed from the details to add value but too central to the org chart to skip.

Why This Happens

Growth creates specialisation. Specialisation creates handoffs. Handoffs create the need for coordination. And coordination, when not designed carefully, creates drag. The drag isn't immediately visible. It accumulates slowly — in small delays, in meetings that produce no action, in decisions that get deferred.

Part of what makes this hard to address is that each individual piece of process usually exists for a good reason. The approval workflow was added because something went wrong. The weekly sync was scheduled because people felt out of the loop. The documentation requirement came from a real gap. Individually, none of it seems unreasonable. Together, it becomes the problem.

The Cost of Letting It Continue

When effort quietly increases, the people closest to the work absorb the cost. They work longer. They work around systems rather than through them. They develop informal workarounds — Slack threads that substitute for decisions, shared docs that bypass the CRM, direct messages that replace the ticketing system.

These workarounds aren't laziness or noncompliance. They're adaptive behaviour. They're what happens when the formal systems don't match the actual shape of the work. But they also create invisibility. The work gets done, but the organisation can't see it clearly. It can't learn from it. It can't improve it.

What Tends to Help

The interventions that work tend to share a common quality: they make the actual work visible rather than adding more management of it.

• Mapping how decisions actually get made — not how they're supposed to — and removing steps that add delay without adding value.
• Identifying which handoffs are creating the most friction, and whether that friction is necessary or historical.
• Reducing the number of people who need to be involved in routine decisions, while keeping accountability clear.
• Creating lightweight documentation that captures decisions without requiring a meeting to produce them.

What This Means in Practice

In practice, this often means resisting the urge to add more structure when things get complicated. The instinct — especially for founders and leaders who want to stay in control — is to add oversight. More reporting. More reviews. More checkpoints. But the more disciplined response is usually to remove something rather than add it.

It also means paying attention to where energy is going, not just where output is going. If a significant portion of a team's time is spent on internal coordination rather than external value creation, that's a signal worth taking seriously.

How This Connects to Our Work

When we engage with organisations navigating this, the starting point is rarely the org chart or the strategy. It's the day-to-day experience of the people doing the work. Where does effort feel disproportionate? What decisions feel like they take too long? What would move faster if one thing changed?

From there, it's usually possible to identify two or three changes that would have an outsize effect — not because they're dramatic, but because they're well-placed.

Where This Might Be Relevant

This pattern tends to show up most clearly in organisations that have recently scaled — either in team size, in product complexity, or in customer base. It's also common in teams that have added process in response to past failures without revisiting whether that process is still serving its original purpose.

• Teams that have grown from under 10 to over 30 people in under two years.
• Organisations managing multiple product lines or service offerings without clear operational separation.
• Leadership teams spending more time in internal meetings than in work that touches customers.

Closing Reflection

Growth is supposed to make things easier over time — more resources, more capacity, more leverage. When it doesn't, it's worth asking why. Usually the answer isn't that the people are wrong or the strategy is flawed. It's that the systems haven't kept up with the shape of the work.

That's a solvable problem. But it requires looking at the work honestly, without defending the systems that were built to support it.