Every business has an operating model, even if nobody has ever described it that way. Work arrives, decisions are made, people carry out activities, and customers receive a result. The operating model is simply the arrangement of responsibilities, processes, information, suppliers and management routines that makes this possible.
For a small team, the arrangement may be almost entirely informal. As the business develops, what once worked well can become progressively harder to sustain. The warning is not necessarily a dramatic operational failure. It may be the persistent effort required to produce results that used to be straightforward.
The organisation chart tells only part of the story
A chart can show reporting relationships, but it rarely explains how work gets done. A company may appoint a Head of Operations and still leave every material customer exception with the founder. Another may create a project-management function without defining who has authority to accept a delivery commitment.
That is why structural change should follow an understanding of the services or outcomes the business must deliver. Who is accountable end to end? Which activities are performed internally? Which depend on suppliers? Where are the decisions, information and controls located?
The answers often cross departmental boundaries. If a business changes its structure without resolving those connections, it can simply relocate an existing problem.
Watch for changes in complexity
Growth in employee numbers is an imperfect indicator. A business may double its workforce while retaining the same core offering. Another may remain small but introduce a regulated service, an overseas supplier or a new channel that materially alters its obligations and risk.
I would look for changes in the variety of customer commitments, the number of hand-offs, the need for specialist judgement, the consequences of failure and the proportion of work requiring coordination. These are the conditions under which informal arrangements are likely to become strained.
Consider an illustrative distribution company that adds installation and ongoing support to a successful product business. Sales, logistics and field teams now need to agree dates and acceptance criteria. The company may not need a new layer of management immediately. It does need an explicit owner for the complete customer outcome and a dependable way of coordinating commitments.
Decide which capabilities the business really needs
A useful operating-model review starts with capabilities rather than job titles. What must the company be able to do reliably? Examples might include winning suitable work, pricing it sensibly, delivering consistently, controlling cash, managing suppliers, protecting information and resolving customer issues.
For each capability, distinguish ownership, execution, specialist advice and assurance. These are different responsibilities and need not all sit with the same person. In a small business, several roles will naturally be combined. The important issue is whether any essential responsibility is missing or whether incompatible demands are overwhelming one role.
Some activities can be outsourced effectively. However, the business should still retain someone accountable for the outcome and the commercial relationship. Outsourcing execution does not make a decision about priorities, risk or acceptable service disappear.
Introduce enough management to make decisions
Growing organisations often establish regular meetings because coordination has become difficult. The meetings then multiply, whilst uncertainty remains. A management routine is useful only if it produces a decision, resolves an exception or enables accountability.
A proportionate cadence might include a brief weekly review of customer commitments and operational exceptions, a monthly review of financial and capacity performance, and a quarterly assessment of priorities and material risks. The precise frequency should reflect how quickly the business changes.
Each review needs relevant information, a decision owner and a record of the actions agreed. It should be possible to explain what would become less reliable if the meeting stopped. If nobody can answer, the meeting may not be adding much value.
Avoid creating structure faster than capability
New titles can suggest that a business has matured when the underlying responsibilities remain unclear. Conversely, delaying every formal role until an obvious failure occurs can leave colleagues carrying incompatible workloads.
I would phase the change. Begin with clear ownership of essential outcomes. Establish decision limits and a small set of management measures. Then consider specialist posts, management layers and systems where the workload or risk justifies them. This is less dramatic than a wholesale reorganisation and often easier to sustain. The OECD’s 2026 D4SME survey identifies cost and skills among barriers reported by the SMEs surveyed about digital adoption. [2]
The people affected need to understand which decisions have changed and which have not. An operating model exists in daily behaviour, not solely in the diagram presented at a management meeting.
Test the model against a real journey
A useful test is to choose a representative customer journey, an exception and a period of staff absence. Can the company still accept work, allocate resources, resolve a dispute and account for the outcome without improvised intervention? Does the information reach the person making the decision?
A second test concerns growth. If demand rises materially, which step would fail first? The answer helps separate a need for additional capacity from the more fundamental requirement to change how work is organised. The ScaleUp Institute’s 2025 annual review identifies leadership and talent among challenges reported by its surveyed scaleups. [1]
Make supplier boundaries explicit
An operating model often extends beyond the organisation. Accountants, technology providers, specialist contractors, outsourced delivery teams and commercial partners can be essential to meeting customer commitments. A supplier agreement may define services and response expectations, but it does not automatically clarify who makes the underlying business decisions.
I would distinguish the party performing an activity from the role accountable for the result. A supplier may administer a platform, but an internal leader still needs to decide the consequences of downtime, the priority of recovery and whether a proposed change is commercially acceptable. The same principle applies to outsourced finance, recruitment and specialist delivery work.
Where a capability depends on an external party, record what happens if that party cannot perform, how exceptions are escalated and which information the business can access independently. A small company does not need a complex supplier-governance programme to ask these questions. It does need to know where responsibility remains.
Design for ordinary absences and unusual demand
A structure should work when the founder is away, a team leader is ill or a customer asks for something outside the standard offering. These situations reveal whether the model depends on routine heroics. If a critical decision stalls without one particular person, the arrangement may need a deputy, a clearer authority limit or a defined escalation route.
Similarly, a sudden increase in orders exposes the difference between a capacity constraint and a coordination problem. Hiring may relieve the former. It can worsen the latter unless the hand-offs and priorities are understood. Testing these scenarios on paper, then checking a manageable real example, helps identify which changes are actually required.
Sources and further reading
[1] ScaleUp Institute, Annual Review 2025 Read online
[2] OECD, Empowering SMEs in the age of AI: 2026 D4SME Survey Read online
Sources accessed 6 November 2026. All examples explicitly described as illustrative are hypothetical.
