Subscribe to our newsletter to receive business tips, learn about new funding programmes, join upcoming events, take e-learning courses, and more.
Take the first step to successfully starting and growing your business.
Join for free)
Posted: Fri 31st Jul 2026
Last updated: Fri 31st Jul 2026
5 min read
Most small business owners can describe their org chart.
Far fewer can describe their operating model. And that gap is usually what breaks first when the business tries to grow.
An org chart tells you who reports to whom. An operating model tells you how work actually gets done – which capabilities the business needs, how decisions get made, how information flows between teams, and which processes and systems support it all.
You can redraw the chart a dozen times and still have the same bottlenecks, because the chart was never the problem.
At small scale, an informal operating model works fine – the founder knows everything, decisions happen in hallway conversations and process lives in people's heads.
The trouble starts once headcount passes the point where one person can hold the whole business in their head.
A deliberate operating model answers four questions.
Structure: How is the business organised, and where do the reporting lines create friction?
Business architecture is the discipline that maps these four elements together.
As a result, a change to one – say, adding a new decision-maker – can be traced through to its effect on process and systems, rather than discovered by accident three months later.
Of the four elements, decision rights deserve the closest attention, because small businesses' leadership structures tend to fail in one of two directions.
Too flat, and everything still routes through the founder or a tiny senior team – efficient early on, but it caps growth at their personal bandwidth.
Too layered, and growth triggers a defensive response of adding management "to cope," so every decision passes through several approvals before reaching whoever actually has to act on it.
Both failure modes are structural, not personal, and both are fixed the same way. So, ask, for every layer of leadership, what does this layer decide that the layer below can't?
If the honest answer is "nothing, it just reviews and forwards," that layer is overhead, not leadership.
Decisions consistently wait for one or two people regardless of size.
New leadership hires get absorbed into "helping out" rather than genuinely owning decisions
Growth plans assume more revenue without addressing who will make the extra decisions that revenue creates.
Once decision rights are clear, the next question is whether the structure can adapt when conditions change – a new product line, a big client demand, a shift in the market.
Real agility isn't speed, but the ability to reconfigure how work gets done without the whole business grinding to a halt while it happens.
Most small business teams are organised around fixed functions.
That works fine when conditions are stable and falls apart when a change needs several functions to move together, because nobody owns the cross-functional outcome, only their slice of it.
The fix isn't dismantling functional expertise in the name of agility, as sales still needs sales skills, delivery still needs delivery skills, and so on.
Instead, it's forming small, temporary cross-functional pods with a single accountable owner for specific outcomes, while functional teams remain the home for skill development.
Teams organised around outcomes, with decision rights pushed close to the work, can be recombined as priorities shift rather than requiring a full reorg every time.
A 25-person consultancy kept missing delivery deadlines.
The founder assumed it was a resourcing problem and hired two more consultants – but still the deadlines kept slipping.
The real issue was structural on two fronts:
Every project needed the founder's sign-off to reassign staff (a decision-rights bottleneck).
There was no standing mechanism for delivery, sales and account management to co-ordinate on a stretched project (an agility gap).
Reassigning approval authority to project leads and creating a lightweight weekly cross-functional review fixed what two new hires never could.
Pick one capability under real strain right now – delivery, onboarding, whatever hurts most.
Map who currently makes decisions in that area, what layers a decision has to pass through, and how the team currently copes when something unexpected happens.
You'll usually find the constraint is design – and design is something you can change without waiting for the org chart to catch up.
