“Most of our so-called reasoning consists in finding arguments for going on believing as we already do.” – James Harvey Robinson, The Mind in the Making, 1921
There is a moment that many founders will recognise, although it rarely feels like anything worth pausing on at the time. It sits inside a pattern that most growing businesses encounter sooner or later: the leadership habits that built the business beginning, almost imperceptibly, to limit its scale.
A management meeting ends, the agenda has been covered, the team has contributed, the right things were said. And yet the founder walks out carrying a mental list of things they will need to follow up on themselves. Not because anything went wrong. Not because anyone let them down. The list is there, the way it always is, and it will have to be worked through before the week is out.
That weight has been accumulating for some time, despite the business being larger, more experienced, and better resourced than it was. As the business has grown, execution has tended to feel more demanding rather than less – not dramatically, but persistently, in the way that a load feels heavier over a long walk than it did at the start.
It is natural, at this point, to look at the structure around the founder, or at the capability of the team, or at how clearly direction is being communicated. What is less natural is to look at the patterns of behaviour that have carried forward unchanged from an earlier stage of the business, even as the context around them has shifted.
Where These Leadership Habits Came From
The habit of staying close to decisions rarely begins as a preference. It forms because, at a certain stage of the business, there are few viable alternatives. A decision needs to be made, context is uneven, and the founder’s understanding of how things fit together is materially ahead of everyone else’s. The quickest, safest path is for the decision to sit there.
These moments tend to be familiar: an operational call is needed, something fairly routine, and it finds its way to the founder. Not necessarily because anyone consciously directed it there. Sometimes because the founder was available. Sometimes because whoever was handling it was not entirely sure where the decision authority sat. Sometimes simply because it was faster. The founder makes the call, the issue moves on, and nothing is recorded about who made it or why it landed where it did.
In an early founder-led business, that kind of direct involvement made complete sense. When the team was small and the founder’s knowledge of every part of the operation was genuinely superior, staying close to decisions was not a flaw. It was effective leadership. The demands of leadership at scale are simply different. Mistakes were expensive then, context was hard to transfer, and speed mattered above almost everything else. The habit formed precisely because it worked. That matters, because any examination of where habits lead has to begin with honest recognition of where they came from.
What the Team Learned to Expect
The structural cost of that habit is not always clear. It tends to become visible in a specific kind of moment: a capable senior person walks into the founder’s office or appears in a message thread, bringing a decision that they had, by any reasonable measure, both the authority and the knowledge to make themselves.
It’s not a question of lacking confidence. They’ve simply learned, from months of observation, that the founder will be involved at some point regardless – and bringing it earlier is more efficient than waiting. So the founder’s diary fills. The organisation moves on, and nobody notices that the decision was made in the wrong place.
This is not a people problem. It is an adaptation. The organisation has read the real operating rules rather than the stated ones, and it is responding accurately to them. When a founder reliably steps into decisions, the organisation gradually stops building the muscle for independent decision-making. Initiative does not atrophy through carelessness, but through experience. People stop reaching for decisions they have come to understand sit outside their decision authority. The result is a team that is technically capable but structurally dependent – and a founder who carries a load that was never supposed to be theirs alone.
Handling Conflict Without Structure
A similar dynamic plays out around conflict. The moment tends to look something like this: two senior people are in disagreement – about a decision, a priority, a boundary between their areas. Both of them are capable adults. Between them, there is enough seniority and enough organisational authority to work through it – they don’t. The issue arrives on the founder’s desk anyway. Not because anyone asked the founder to resolve it, but because both parties knew, from experience, that it would find its way there eventually.
The founder resolves it. Often quickly, effectively, drawing on a broader view of the business and a deeper understanding of the individuals involved. The immediate issue is dealt with and the business moves forward.
In the early stages, this is efficient and often preferable to any form of process. The founder’s judgement is a valuable resource, and using it directly avoids unnecessary delay. Over time, however, something else begins to take shape. The organisation learns that conflict is not truly held within the structure between people, but above it. The relationships within the team begin to rely less on their own capacity to absorb and resolve tension, and more on the presence of someone who will settle it when needed.
At scale, however, the cost of that habit is not the decision itself – it is what never gets built around it, and the execution pressure that accumulates as a result. Teams that have learned their conflict will be resolved upward stop developing the relational mechanisms and the structural clarity to hold it themselves. The founder becomes the de facto architecture of the business. And when the founder steps back, or is simply unavailable, there is often very little structure underneath to carry the load.
The Relationship the Business Doesn’t Own
The same pattern applies, less visibly, to client relationships. The moment here is a client issue that escalates – something that needs careful handling. The founder steps in personally. Not because no one else could have managed it, but because the client expects it. Because the relationship, over years, has become personal. Because the founder would not feel entirely comfortable leaving it with someone else, and the client would notice if they did.
The original logic is easy to understand. The founder won those clients. They built the trust, understood the context, and the personal relationship was a genuine commercial advantage. At scale, however, that same advantage carries a cost that rarely shows in normal operating conditions. The business appears commercially healthy, the client relationships look strong, and everything seems to be working. What is harder to see is that those relationships sit at the individual level rather than the organisational level. They are not, in any meaningful sense, owned by the business. They are personal assets that appear on the balance sheet as organisational ones – a form of founder dependency that rarely shows until it matters most.
That fragility does not usually reveal itself gradually in a founder-led business. It tends to surface all at once – when the founder is unwell, or unavailable for an extended period, or eventually transitions out of the business.
Direction Given Verbally, and What Happens to It
Perhaps the habit that produces the least visible friction, and therefore gets examined least often, is the practice of setting priorities through conversation rather than through any formal process.
The moment is this: the founder has had a clear conversation about direction. A strategy discussion, a leadership meeting, a corridor exchange with a senior person. The intent was communicated, the founder was clear, and the conversation felt productive. Three weeks later, the business is still operating largely on the previous understanding, because nothing formally changed. The direction was spoken, but the organisation had no structural home for it.
In the early business, this was not a problem. The founder could communicate with the entire team in an afternoon. Verbal clarity was enough because the team was small enough for it to carry weight. At scale, verbal priorities pass through more layers, get filtered through different interpretations, and compete with what was already in motion. The gap between what the founder said and what the organisation understood tends to widen, not through anyone’s negligence, but because nothing in the business had really taken hold of it.
This is often where an outside perspective becomes useful – not because an advisor or board member is more insightful, but because they are not inside the habit. They can see the gap between the stated direction and the lived one more clearly than anyone close to it can, because proximity and habit are closely related. Distance is what makes a pattern visible; it is rarely wisdom alone.
The Organisation Is Responding Precisely, Not Failing
There is a thread running through each of these leadership patterns: the organisation around them is not underperforming. It is adapting, with considerable accuracy, to the conditions created.
Teams that wait for decisions have learned, correctly, that decisions tend to be made above them. Managers who escalate conflict have observed, correctly, that it will find its way upward regardless. Clients who call the founder directly have been taught, through experience, that this is how the relationship works. People who interpret strategic direction loosely have understood, through repetition, that the formal version of things rarely carries the weight of the verbal version.
Marshall Goldsmith’s observation in What Got You Here Won’t Get You There – that the behaviours which produce success in one context can become the obstacle in the next – is not a comfortable thought for people who have built something real. But it is a precise one. The leadership habits examined here were not errors. They were rational responses to real conditions. The conditions changed. Effective leadership at scale asks something different of those same habits.
What the Habit Signals Now
None of these patterns are the problem in themselves. Each of these leadership habits formed for a reason, and in most cases that reason was sound at the time. That is what makes them difficult to look at directly. They do not feel like mistakes, but like continuity.
Over time, though, continuity begins to carry weight of its own. A way of working that once made things easier starts to add some friction. A decision that would have moved cleanly now takes another step. Something that should have been handled lower down comes back, almost automatically. Nothing here is dramatic. It rarely is. But the pattern repeats, and the execution pressure builds accordingly.
The execution pressure that comes with scaling a business is not usually the result of a single structural issue. It is more often the accumulation of things that were never revisited, simply carried forward because they worked once and were never challenged again.
The business tends to reflect that, although not always in ways that are immediately obvious. A delay that keeps appearing. A conversation that returns. A decision that never quite settles where it should. Those signals are easy to miss while they are still small, and the leadership habits remain, until they become impossible to ignore.
The question is not what needs to change. It is whether you are seeing what is already there.
If you enjoyed this article you can subscribe here to receive future articles.
—
0 Comments