Growth can be an awkward kind of success. The order book looks healthy, the team is larger and the business has opportunities that were beyond reach a few years earlier. Yet the working day feels less predictable. Decisions are delayed, important customers rely on one or two people, and small mistakes take longer to resolve than they should.

It is tempting to describe this as a shortage of capacity. Sometimes it is. More often, there is a mismatch between the size of the organisation and the way it is being managed. Habits that were perfectly sensible for five colleagues can become obstacles when there are thirty.

Growth changes the work before it changes the organisation

In a small business, coordination happens almost invisibly. The founder knows which customer requires attention, who can resolve a problem and which trade-offs are acceptable. Colleagues learn by working closely together. Decisions can be made in minutes, often without a formal meeting or documented procedure.

That approach has genuine advantages. It is quick, personal and responsive. The difficulty begins when the volume of decisions grows faster than the founder's available attention. A request that once passed across a desk now moves between sales, delivery, finance and an external supplier. Each hand-off introduces another opportunity for misunderstanding.

The ScaleUp Institute's 2025 annual review identifies access to talent and leadership among the barriers reported by surveyed UK scaleup leaders. That is evidence about a defined scaleup population, not a prediction about every small company. Nevertheless, the underlying management question is familiar: how does an organisation retain its agility while becoming less dependent on informal coordination? [1]

The early warnings are usually ordinary

Operational strain rarely announces itself as a grand failure. Instead, managers begin to recognise a pattern: the same approval is requested repeatedly; a task is completed differently depending on who takes it on; customer commitments are not visible across teams; or a recurring problem has been resolved several times without a permanent owner.

None of these signs proves that the organisation has the wrong structure. A one-off incident may simply be a one-off. I would be more interested in repetition, particularly when the same underlying cause appears in different parts of the business.

Consider an illustrative design agency that has grown from eight to twenty-five people. Sales agrees to delivery dates, project managers allocate work, and finance invoices on completion. Each team is acting reasonably in isolation. However, no one owns the end-to-end view of commitments, capacity and acceptance. The result is not necessarily poor performance by individuals; it may be an operating model that no longer fits the work.

Separate the symptoms from the causes

The natural response to delays is often to recruit someone, purchase software or introduce another approval step. Any of those may be right, but none should be the starting assumption.

A useful diagnosis begins with one important business outcome: an order fulfilled, a customer onboarded, a service delivered or a payment collected. Follow the work from request to completion. Who accepts it? Who decides priority? What information is needed? Where does it wait? Who verifies that the result is acceptable?

This is not a case for documenting every movement in painstaking detail. A simple working map, tested with the people who perform the work, can expose the hand-offs and unclear responsibilities that create most of the friction. Only then does it make sense to decide whether additional capacity, clearer authority, better information or a different process is required.

Formality should follow risk, not fashion

Smaller businesses sometimes resist management structures because they associate them with corporate bureaucracy. The concern is understandable. A weekly reporting pack that nobody uses adds work without improving a decision. Equally, refusing to define responsibilities because the company wants to remain entrepreneurial can create unnecessary dependence on a few individuals.

I would draw the line at what must be repeatable. Customer commitments, financial approvals, access to essential information and the handling of material exceptions need sufficient consistency. Creative work, routine collaboration and low-risk decisions may require considerably less control.

A proportionate arrangement might consist of a named owner for each critical service, clear approval limits, a short weekly review of exceptions and an agreed way of changing commitments. The test is whether these arrangements reduce uncertainty rather than simply produce more paperwork.

Protect the founder's capacity

One of the less visible costs of unmanaged growth is the attention consumed by decisions that need not reach the founder. Individually, they may take only a few minutes. Collectively, they displace customer relationships, strategy, recruitment and the judgement that originally helped the business succeed.

Delegation is not simply passing work to someone else. It requires a decision boundary, access to the relevant information and an agreed point at which an exception should be escalated. Without those conditions, the founder remains responsible for resolving the uncertainty after the work has been delegated.

There is also a people consideration. Colleagues cannot be held meaningfully accountable for outcomes if they lack the authority or information to influence them. Clarity is not only a control mechanism; it gives people confidence about what can be decided without asking permission.

A better starting point than a reorganisation

Before changing job titles or drawing a new organisation chart, select the two or three areas where the business most often loses time or surprises customers. Understand the actual flow of work, agree one accountable owner for the outcome, and remove one recurring decision bottleneck. Check the effect over a few weeks.

A broader operating-model review may eventually be justified, particularly where growth has materially changed services, locations, suppliers or leadership responsibilities. However, a small improvement that works is more useful than an ambitious structure that nobody has time to adopt. For wider policy context, the UK government’s SME plan describes its priorities for supporting smaller businesses. [2]

Check whether the improvement has worked

Management changes can look convincing in a workshop and prove less useful once normal pressures return. A new handover checklist may have been agreed, but is it being used when a customer is demanding an urgent start? A delegated approval may look clear on paper, but do managers have enough information to decide without asking the founder anyway?

I would check a small sample of real work rather than relying on a declaration that the new process has been introduced. Examine recent customer commitments, see where delays occurred and ask which decision resolved them. If the initial problem was missing information, the test is whether that information now arrives consistently at the right point. If it was unclear authority, the test is whether decisions move without unexpected escalation.

Sources and further reading

[1] ScaleUp Institute, Annual Review 2025 Read online

[2] UK Department for Business and Trade, Backing your business: plan for SMEs (2025; updated 2026) Read online

Sources accessed 6 November 2026. All examples explicitly described as illustrative are hypothetical.