When a business is small, people can coordinate through direct conversations and shared experience. They know the customers, understand the priorities and can resolve uncertainty quickly.
As the business adds people, services or locations, those informal arrangements become harder to sustain. Work still gets done, but it takes more chasing, intervention and personal effort.
Your operating model is the practical arrangement of responsibilities, processes, information, systems and resources through which you deliver value. It needs to reflect the business you run today and the demands you expect next.
1. Decisions no longer sit where the work happens
Routine decisions travel through several layers of approval. Managers carry responsibility for outcomes but lack the authority to make the trade-offs needed to achieve them. Senior leaders become involved in questions they thought they had delegated.
Some escalation is appropriate. The warning sign is a repeated pattern in which people cannot tell which decisions they own, what limits apply or when they should seek help.
For example, a delivery manager may be expected to meet a deadline but need separate approvals to move people, use a supplier or agree a revised scope. Accountability exists on paper; the authority to act is fragmented.
Start with one recurring decision. Define who makes it, whose input is required and the conditions that trigger escalation. Test whether that makes work move more reliably before extending the approach.
2. Work breaks down between teams
Each department can describe its own responsibilities, yet work loses momentum as it moves between them. Sales considers a contract handed over; delivery is still waiting for essential information. Finance is ready to invoice, but no one has confirmed acceptance.
These gaps become more visible as volume grows. People compensate with extra meetings, spreadsheets and follow-up messages, but the handover itself remains unreliable.
Follow a recent piece of work from customer commitment to completion and payment. Look for queues, missing information, repeated checks and unclear ownership. Ask who is responsible for the overall outcome, as well as each individual step. A useful improvement might be a clearer acceptance standard at one handover, supported by an agreed owner and a way to resolve exceptions. Adding another meeting will help only if it changes how the work proceeds.
3. Exceptions have become the normal way of working
A process exists, but experienced employees routinely work around it. Customer-specific arrangements accumulate. The team relies on a few people who remember what was promised and know how to make the systems accommodate it.
Flexibility can be valuable. The question is whether variation is deliberate, understood and priced—or whether the business absorbs its cost without making a conscious choice.
A service designed for a small number of bespoke engagements, for example, may struggle when sold at a much higher volume. Every new customer brings another configuration, approval or manual step. Review the most common exceptions. Decide which should become standard options, which justify a premium and which should stop. Preserve flexibility where it creates value, with clear boundaries around what the business can reliably support.
4. More reporting produces less clarity
The business has dashboards, but meetings still begin with arguments about whose figures are correct. Teams maintain different definitions of a customer, a completed job or an overdue order. Reports explain what happened without helping anyone decide what to do.
The underlying issue may be inconsistent data, unclear ownership or measures that no longer reflect how the business creates value. A new reporting tool will struggle if those questions remain unresolved.
Choose one important operating decision and work backwards. What information does the decision-maker need, how current must it be and who is responsible for its quality? Agree a small set of shared measures and connect them to action. A backlog measure becomes more useful when the team knows which threshold requires a capacity review and who will lead it.
5. Priorities and resources are planned separately
Leadership agrees ambitious priorities, but teams receive new work without corresponding decisions about capacity. The same specialists appear in every project plan. Urgent requests repeatedly displace commitments, while nobody explicitly decides what will wait.
Hiring may ease a genuine capacity shortage. It will not resolve a planning process that commits the same people several times or treats every request as equally important.
Review demand against available capacity across the business. Include ongoing delivery, improvement work and the management attention required to support both. Identify the constraints before making further commitments. Then make the trade-offs visible. Agree what takes precedence, what will be deferred and when the plan will be revisited. A credible plan gives teams a basis for saying yes, no or not yet.
Start with a recurring point of friction
These signs do not automatically call for a wholesale reorganisation. They indicate where the way work is organised may need to change.
Choose a recurring problem with a visible customer or business consequence. Examine a few recent examples with the people involved, then test a focused change to ownership, a handover, a decision rule or the planning process.
Agree how you will judge the result. Shorter waiting times, fewer avoidable escalations or more reliable commitments are more useful evidence than a newly documented process alone.
Growth will always introduce new demands. The aim is to make the way the business works evolve deliberately, before repeated workarounds become the only way it can function.