“As useless laws weaken necessary laws, those that can be evaded weaken legislation.” – Montesquieu, The Spirit of the Laws, 1748
Most founders who resist adding structure will tell you the same thing: they built the business by moving fast, and they do not want to slow it down. The instinct is entirely understandable. In the early years, speed came from directness – fewer people, fewer layers, decisions made in the room by whoever was there. Adding structure felt like adding friction. In many cases, it was. The difficulty is that the business has changed, and the instinct has not.
By the time a business has grown beyond its early stages, many of the conditions that once made informality effective have disappeared. The founder is no longer sitting beside every key person. Teams have formed around functions. Decisions now affect areas the founder no longer sees directly. The business carries more clients, more commitments, more operational complexity and, frequently, more risk than it once did. Yet many businesses continue trying to operate without the business structure their size now requires.
That is often where the drag begins.
The Decision That Still Travels Too Far
This tends not to announce itself as a structural problem. It shows up instead as a manager who pauses before responding to a customer complaint, checking whether this falls within his decision authority or whether it needs to go upstairs. A supplier issue that sits in someone’s inbox because the person who could resolve it is not sure they are permitted to. A meeting that ends with everyone aligned but nothing decided, because the actual authority to act belongs to someone who was not in the room.
These are not failures of competence. In most cases, the people involved are perfectly capable of making the call. The hesitation comes from somewhere else – from years of operating in an environment where the boundaries of decision authority were never made explicit, where decisions drifted upward not because anyone asked them to but because that was simply what happened. The pattern becomes normalised. The friction becomes background noise. And eventually, the business stops noticing that it is waiting.
That waiting is where pace goes. Not to poor execution, not to market complexity, not to the difficulty of the problem at hand. To uncertainty about who is permitted to decide – because decisions are travelling further through the business than they should need to.
The Instinct That Made Sense
It is worth being clear about where the resistance to structure comes from, because it is not irrational. In the early stages of a business, informal authority works precisely because the founder could move directly from issue to decision without needing to coordinate across multiple teams or functions. Decisions travel to the top because there is no meaningful difference between the top and everywhere else. Speed comes from proximity, not from design.
That period leaves a strong imprint. The founder experienced the business at its most agile – lean, direct, responsive – and came to associate that informality with what a healthy business looked like. The founder learned, correctly, that excessive process slowed movement. They learned that bureaucracy often appears before genuine organisational maturity. They learned that some people hide behind meetings, reports, and procedure rather than exercising judgement.
The problem is that imprint tends to persist long after the conditions that produced it have changed. The business is now several times the size it was then. There are layers of people between the founder and the customer, between the decision and the consequence. But the operating assumptions are still those of a business that could fit around a single table, and the absence of structure does not preserve speed, but reduces it as more and more traffic goes through a few people.
What the Business Has Become
By the time operational drag becomes uncomfortable, it has usually been building for some time. The pattern that tends to emerge in growing SMEs is not dramatic – it is incremental. Decisions that should sit with a department head arrive consistently one level higher. Meetings multiply to coordinate what clearer role design would resolve. People spend increasing amounts of time checking alignment rather than moving work forward. Work stalls, not because people lack the ability but because nobody is quite certain who can say yes, and the cost of being wrong feels higher than the cost of asking.
The founder’s natural explanation for this is external. The market has become more demanding, the clients more complex, the pace of change more relentless. These things may be true, but they rarely account for the shape of the drag. The shape of it – the repeated escalations, the stalled approvals, the information that somehow always needs to reach the top before anything moves – is a business structure problem. It is the organisation doing what it has learned to do.
There is a subtler problem underneath this, though. As a business grows, the economics of the founder’s attention shift. Early on, a founder being involved in everything added momentum – their presence accelerated decisions, clarified direction, resolved structural ambiguity on the spot. That same involvement, at scale, begins to do the opposite. The business slows at the points where it waits for the founder’s input, and those points multiply as the organisation grows. What was once the engine becomes, gradually, the bottleneck – the point at which founder dependency begins to cost the business more than it contributes.
What Business Structure Actually Removes
This is the part that tends to get lost in the conversation about structure. The argument is not about adding more – more process, more oversight, more control. It is about removing the conditions that generate friction in the first place.
Where authority is genuinely understood, decisions tend to be made at the level where they belong. The manager dealing with the customer complaint knows what they can authorise and what requires escalation. The supplier decision moves because the person responsible for it knows it is theirs to make. The meeting produces a resolution because the people in the room are the right people for the decision at hand. None of this is remarkable. It is simply what happens when clarity about who owns what replaces the accumulated ambiguity that grows in its absence.
The behavioural shift that follows this kind of clarity is worth noting. People move with more confidence when they understand the scope of their decision authority. They stop seeking reassurance for decisions that fall within their remit. They stop escalating things that do not need to be escalated. The reduction in upward traffic is not a result of people suddenly working harder or faster – it is a result of them no longer needing to pause.
That pause, repeated across a team of any size throughout a working day, adds up to something significant. Businesses that have worked through this tend to discover that much of what they experienced as overload was not the volume of work but the friction generated by structural ambiguity around it. Organisational clarity, it turns out, functions less like an administrative exercise and more like a competitive advantage, as Patrick Lencioni’s work so clearly illustrates.
Leadership capacity, in this light, is not simply a question of hiring better people or developing stronger individuals. It is at least partly a structural question. When authority is distributed clearly, the organisation carries more of its own weight. It becomes less dependent on the accumulated knowledge and judgement held at the centre.
The Difference Between Bureaucratic and Enabling Design
The founder’s resistance to structure is not entirely without foundation, and it is worth acknowledging that directly. Bureaucratic structure – process added to process, approval layers that exist because they were never removed, reporting requirements that satisfy no clear purpose – does slow things down. It is also recognisable, because it tends to generate paperwork rather than decisions, takes time and energy away from important tasks, and accumulates rather than evolves. Anyone who has operated inside a large organisation will have encountered it. The founder who built something lean from scratch has good reason to be wary of it.
But that is not the only kind of structure, and conflating the two is where the instinct goes wrong. Enabling business structure looks quite different. It defines where authority sits, what the escalation paths are, and at what threshold a decision moves upward. It creates an operating rhythm that makes work predictable rather than reactive. It removes the need for constant intervention by making clear, in advance, what does and does not require it. Once that clarity is in place, the daily traffic – the questions, the approvals, the check-ins that fill a founder’s day – largely resolves itself. The founder does not disappear from the business. They simply stop being the default answer to questions the structure should already have settled.
The distinction between these two kinds of structure is, in practice, the difference between constraint and capacity. One adds weight. The other redistributes it. The question is how to keep that redistribution in place once the pressure of a working week reasserts itself.
What Governance Holds in Place
Even well-designed business structure will generally erode over time, particularly in growing businesses. This erosion is often underestimated. A business can invest seriously in clarifying decision authority and thresholds, establish a sensible operating rhythm, and see real improvement – and then watch it gradually erode as the pressure of day-to-day operations reasserts the old patterns. The founder steps in on something because it is urgent. An exception becomes a precedent. The escalation path that was supposed to stop at the department head gradually extends back to the top. Within a year, much of what was designed has dissolved, not through any deliberate decision but simply through the accumulation of habit.
Business governance is what prevents that from happening. Not governance in the sense of compliance requirements or board formalities, but business governance understood as the discipline of maintaining the design under pressure. It is what keeps authority where it was placed when urgency argues for bypassing it. It is what ensures that the structure evolves as the business grows rather than calcifying into something that no longer fits. And it is what creates the conditions for a business to function with consistency across people and time – which is, ultimately, what makes it less dependent on any single person at its centre.
A business whose operating design holds under pressure carries its weight through distributed authority and clarity rather than through increasing central involvement. That is a different kind of resilience to the one that depends on the founder always being available, always being across things, always being the one who knows. It is also, over time, a more durable kind of value.
When Workarounds Become the Process
Founder-led businesses rarely become slow all at once. The friction accumulates in increments small enough to feel manageable in isolation: one extra approval added because a decision went wrong once, one escalation that became the path of least resistance, one more thing that it is simply easier to handle yourself. The organisation adapts itself around these patterns. It learns where the bottlenecks are and routes itself accordingly. After a while, the workarounds become the process.
The founder, through all of this, still experiences themselves as protecting speed. They are involved because involvement works, because it always has, because stepping back has felt like a risk they could not quite justify. What they may not have noticed is that much of the business has, in the meantime, settled into a pattern of waiting for them.
The question worth sitting with is not whether your business has structure. Every business has structure, in the sense that it operates in some consistent pattern. The more uncomfortable question is whether the pattern it has settled into is one you actually designed – or simply one that formed while you were busy doing something else.
If you enjoyed this article you can subscribe here to receive future articles.
—
0 Comments