There is a predictable sequence of events in most growing businesses. The team reaches a size where the informal coordination that worked before starts breaking down. Communication gaps appear. Decisions that used to take an afternoon take a week. Accountability becomes unclear. The founder starts spending more time resolving coordination failures than running the business.
The instinct is to blame the people involved. The actual cause is almost always structural. The organisation grew past the design it was running on — and nobody replaced the design.
The Three Structural Failures
Unclear decision rights
In a ten-person team, decision-making is informal and fast. Everyone knows roughly who decides what, and when in doubt, you ask the founder. This works because the social network is small enough to navigate easily.
At thirty people, the informal network breaks down. There are too many relationships to maintain and too many contexts to track. Decisions get made by the wrong people, not made at all, or made twice in conflicting ways — not because people are incompetent, but because the authority structure was never explicitly designed.
The fix is to define decision rights for each function: what decisions can be made independently within a role, what decisions require sign-off, and from whom. This is not a bureaucratic layer — it is a clarity layer. People move faster when they know what they are empowered to decide.
Accountability gaps
Every important business activity should have a single named owner. Not a team, not a function — a person. The person who wakes up at night if it goes wrong.
Growing businesses accumulate activities that no one fully owns. The responsibility is shared between multiple people, which in practice means it belongs to no one. Everyone assumes someone else is watching it.
Mapping your accountability gaps requires a simple exercise: list every recurring business output that matters — client deliverables, financial reporting, sales pipeline management, operational processes — and assign a single named owner to each. Where you cannot identify one person, you have found an accountability gap.
Coordination tax
As organisations grow, they generate more and more coordination overhead: meetings to align people who are not naturally in the same information flow, escalations to resolve decisions that should be made lower down, status updates to compensate for poor visibility into what other parts of the business are doing.
This coordination tax is a structural symptom. It grows when the organisation's structure does not match its workflows — when the people who need to work together to deliver a thing are organised in a way that makes that collaboration unnatural or difficult.
The solution is to design teams around workflows, not functions. If delivering your core service requires close collaboration between design, delivery, and commercial, organise around that unit of value rather than separating those functions into silos that need constant bridging.
The Span of Control Problem
A common structural error in growing businesses is allowing management spans to get too wide or too narrow simultaneously.
A manager with twelve direct reports cannot provide adequate oversight, development, or support for any of them. Twelve reports creates a bottleneck: the manager becomes a resource constraint and the team learns to work around them rather than with them.
A manager with two direct reports creates a different problem: too many management layers relative to team size, and under-challenged managers who spend their time in the operational work their reports should be doing.
The appropriate span of control depends on the work complexity and the experience level of the team. For most knowledge work in SMEs, five to seven direct reports is a reasonable range. More than that suggests the management layer needs expansion. Fewer suggests the org chart has too many management levels.
When to Restructure
Most businesses wait too long to restructure. They wait until the pain is severe enough that it demands attention — at which point the restructure is also dealing with the accumulated fallout of the structural failures: people who have filled unofficial roles, political dynamics around unclear ownership, and teams that have adapted to work around the structure rather than with it.
The right time to redesign structure is slightly ahead of the pain point. When your organisation is approaching a threshold — hiring to double headcount, taking on a significantly larger client base, expanding into a new market — is the time to ask whether the structure that got you here will get you to the next stage.
Restructuring before it is urgent means the business can make the change thoughtfully, with space to communicate and implement well. Restructuring under pressure means cutting corners that create new problems.
Structure Follows Strategy, Not the Other Way Around
The most important principle of organisational design: structure should follow strategy, not precede it.
Before designing an organisational structure, be clear about what the business is trying to achieve in the next two to three years. The structure should make the execution of that strategy easier — by putting the right capabilities together, by designing accountability around the right outcomes, by reducing coordination overhead on the work that matters most.
Structure designed without clear strategic context often locks in constraints the business later has to fight against. Design it deliberately, and it becomes a lever for growth.
Organisational design is one of the areas we cover in our strategic advisory engagements. If your business is growing and the structure is starting to creak, book a consultation to talk through what the right design looks like.
