How Leadership Must Change as Your Business Grows
How leadership must change as your business grows is a question many leaders do not ask early enough. The leadership model that helped an organisation succeed can become the thing that prevents it from scaling.
In the early stages, speed often comes from proximity. The founder knows the customers, makes the important decisions, solves problems quickly and can see what is happening across the organisation. Experienced employees carry institutional knowledge in their heads. Informal communication works because everyone is close to the centre.
Then the organisation gets bigger. There are more customers, more employees, more markets and more decisions to make. The founder is still the final decision-maker. Senior leaders get pulled into operational escalations. Managers wait for approval. Experienced employees become indispensable because too much knowledge sits with too few people. Customers start to notice the inconsistency.
The predictable response is to add more people, more technology, more processes or more meetings. But through our work with leaders across African organisations, AMI sees a different question emerging: has the organisation outgrown the way it is being led?
That question shaped a recent AMI Leadership Conversation between Rebecca Harrison, CEO and Co-Founder of AMI and Segun Adeyemi, Founder and CEO of Anchor. Their discussion exposed a distinction that matters for every growing organisation: growth adds resources, but scale requires the organisation to become capable of doing more without becoming more dependent on a few people.
As Segun put it, organisations have to keep asking themselves whether, if the business were to double or grow fivefold, “the processes and the people that we have today” would still be enough to support that level of growth.
That is the real leadership challenge of scale. Not simply how to grow faster, but how to build an organisation that can absorb growth without allowing complexity to overwhelm its people, systems or customer experience.
The Leadership Challenges That Come With Growth
For Segun, the complexity ceiling became visible when Anchor moved beyond its first few customers. Early customers were largely people he and his co-founders already knew. As the company grew to more than 100 businesses, that model stopped working.
“If something breaks,” he explained, customers can no longer simply call the founders directly. “There needs to be a process for them to be able to escalate.” As transaction volumes increased, the same principle applied internally. People needed to know what to do when something went wrong without relying on a founder or a handful of experienced employees to intervene every time.
His approach is particularly relevant for leaders who are growing quickly: solve today's problem, but design with the next level of scale in mind. As Segun described it, organisations should not solve a problem only for today's volume. They should be thinking about what happens if the business grows two or five times larger.
Rebecca sees the same complexity from a different angle. She argues that processes are often the root cause of organisational problems without being where those problems first appear. Instead, leaders see the symptoms. A team is overwhelmed. People are burning out. Customers complain that the experience is inconsistent. Something feels like it is "on fire."
That distinction is important. The place where a problem appears is not necessarily the place where it starts. A burned-out team may be signalling a broken process somewhere else in the organisation. A customer complaint may be exposing an internal handoff problem. A manager who constantly escalates decisions may be operating inside a system that never gave them enough authority to begin with.
For leaders, the implication is to stop treating every visible problem as an isolated performance issue. Instead, work backwards from the symptom and ask what the organisation has designed, or failed to design, underneath it.
When everything feels like a bottleneck, start with ownership
Once complexity increases, one question becomes increasingly valuable: who owns this?
Segun describes this as the role of the Directly Responsible Individual, or DRI. When a problem occurs, the first step is to establish who owns it. If nobody does, the problem eventually finds its way back to the founder or senior leadership.
At Anchor, postmortems are used to make this explicit. After an issue has been resolved, the organisation closes the loop by establishing a DRI. Segun makes an important distinction here: having a DRI does not mean the process has already been solved. It means there is someone responsible for ensuring the problem is addressed and for asking why it happens again.
This is where many organisations confuse accountability with ownership. Giving someone a task is not the same as giving them an outcome to own. And giving someone an outcome without the authority to influence it is not real ownership.
The question leaders should therefore ask is not simply, "Who is responsible?" It is: "Who owns the outcome, and what decisions can they make without coming back to me?"
That is a much more useful test of organisational maturity. If every important decision still returns to the CEO, the organisation may have distributed responsibilities without actually distributing ownership.
Build the Leadership Your Growth Requires
Growth puts new demands on your managers and leaders.
AMI's Leadership Development Programme equips leaders with the skills, judgement and practical tools to lead people, make better decisions and build organisations that can scale.
The hardest leadership shift is letting people struggle
One of the most revealing parts of the conversation was not about systems at all. It was about the difficulty leaders have in stepping back.
Segun described a recurring challenge at Anchor. Many of the company's current leaders started as individual contributors. They were capable, passionate and good at getting things done. But as they moved into leadership roles, some continued to hold onto work that should have been handed to their teams.
The temptation is understandable. A leader gives someone a task. The work takes longer than expected or does not meet the required standard. The leader thinks, "I could do this myself in two hours." So they step in and complete it.
But Segun argues that this is exactly what leaders need to resist. “We would rather lose some time,” he said, allowing someone to learn on the job than have the leader jump in and do the work themselves. The reason is simple: “We have to be able to build shared knowledge and shared context.”
This is one of the most important transitions in scaling. The leader's job changes from being the person who can do the work fastest to being the person who builds a team capable of doing the work well without them.
Rebecca strongly reinforced this point, arguing that fast-growing organisations ask much more of leaders than simply executing a strategy. Leaders have to create the future, translate that direction for their teams, build the processes that enable execution and develop the capabilities people need to deliver.
Her reflection was particularly pointed for AMI: despite being a learning organisation, one of her own lessons has been the importance of being intentional about becoming a learning organisation internally. Leaders need to ask not only what their people are doing today, but what capabilities they will need next year and two years from now if the organisation achieves the growth it is aiming for.
That is a fundamentally different approach to talent development. It moves learning from a response to a performance gap to an investment in future organisational capacity.
Culture has to evolve without losing its core
Scale creates another tension: how do you preserve culture when the organisation becomes too large for the founder to personally transmit it?
Rebecca pushes back against the idea that founders or CEOs ever become irrelevant to culture. Leaders remain powerful cultural signals because people watch what they do, not just what they say. “Kids do what you do, not what you say,” she observed, making the point that organisations behave in much the same way.
But leadership alone is not enough. As an organisation grows, culture has to become operational.
Rebecca described AMI's own experience of this shift. Early on, culture could be transmitted through direct interaction. Over time, that was no longer sufficient. People needed to experience AMI's values through the systems surrounding them: how interviews are conducted, whether people follow up when they say they will, whether someone is welcomed on their first day, whether managers recognise behaviours that reflect the values and whether policies reinforce the culture rather than contradict it.
Segun offered a complementary example from Anchor. Every new employee, regardless of role, spends time with him during onboarding. The purpose is not simply to introduce the CEO. It is to explain what the company's cultural principles actually mean when employees have to make decisions.
One example is Anchor's framework for urgency. Segun explained it through a memorable distinction between a hat, a haircut, and a tattoo. A hat can easily be taken off, so decisions of that type should move quickly. A haircut can be changed, but requires more effort. A tattoo is much harder and more costly to reverse, so it requires more consultation and approval.
The principle underneath the analogy is powerful: culture becomes scalable when people understand how values should guide decisions, not simply when they can recite the values.
Build the process around the business, not the other way around
If growth exposes weaknesses in process, the answer is not to create more process for its own sake.
Segun's advice is to start with the business itself. What are you trying to achieve? What is the organisation's North Star? What are the few metrics that matter most? Only then should leaders design the processes required to achieve those goals.
“The process would break if the goal is not clear,” he argued.
This is an important corrective to a common scaling mistake. Organisations often copy processes from larger companies because those processes appear sophisticated. But a process that works in one organisation can be completely wrong for another because the goals, people, business model and operating context are different.
The right question is therefore not, "What process should we adopt?" It is "What are we trying to achieve, and what is the simplest repeatable way for our people to achieve it consistently?"
For AMI, this distinction matters because organisational capability cannot be separated from context. The leadership practices required by a fast-growing African enterprise are not necessarily the same as those required by a multinational operating under a completely different structure. Scaling is not about importing complexity. It is about deliberately building the capabilities and systems that the organisation's next stage actually requires.
The customer often tells you where the system is broken
One of the strongest themes in the conversation was that leaders need to pay attention to where stress appears.
Rebecca described customer experience as one of the early signals she noticed at AMI. Small details that seemed insignificant on their own, such as inconsistencies in how a workshop was delivered, revealed something deeper. When the founders and most trusted leaders were no longer personally involved in everything, the organisation needed processes capable of translating its standards and vision into consistent execution.
Segun's experience points to the same principle from the customer side. As Anchor moved from a small group of familiar customers to hundreds of businesses and thousands of transactions, personal relationships could no longer be the operating system.
His response was not to pretend that everything would work perfectly during the transition. It was to protect trust through communication. “What we cannot tolerate is silence,” he said. When something goes wrong, customers need to know that the organisation is aware of the problem, understands that the experience is below the promised standard and is actively working towards a solution.
For growing organisations, this is a critical lesson. Customers should not have to absorb the complexity created by your growth. If growth means slower responses, inconsistent delivery or unclear ownership, the problem is not simply customer experience. It is a signal that the organisation's internal operating model has not kept pace.
AI is changing what scale can look like
The conversation also raised a question that increasingly sits at the centre of growth strategy: if AI agents can perform more work, does headcount remain a useful measure of organisational scale?
Rebecca argued that leaders need to move beyond adopting AI because it is fashionable and instead become disciplined about testing its actual impact. At AMI, the question is twofold: how can AI improve the value delivered to customers, and how can it make the organisation more efficient internally?
That includes using AI to personalise learning and improve customer experience, but also changing how work gets done. Rebecca pointed to the increasing ability for one person, supported by agentic tools, to accomplish work that previously required a much larger team.
Segun took the idea one step further in his practical takeaway. He encouraged leaders to calculate revenue per employee, then ask a harder question: if the company's revenue and operations doubled, how many people would it require using today's model, and how might that change if AI agents were treated as potential capacity?
This does not make people less important. It changes what leaders need to think about when designing organisations. The future scaling question may be less about how many people a company employs and more about how much productive capacity its people, systems and AI-enabled workflows can create together.
The leadership question behind every growth strategy
The strongest message from the conversation is that scale is not a single operational project. It is a leadership transition.
The founder who once needed to make every decision has to create leaders who can make decisions. The manager who once solved every problem has to learn to coach rather than rescue. The experienced employee who carries critical institutional knowledge has to help turn that knowledge into organisational capability. The people team has to translate culture into everyday experiences and systems. And leaders across the organisation need to think ahead about the capabilities the business will require before those capabilities become urgent.
Rebecca's final practical challenge captured this shift. Leaders should think strategically about becoming a learning organisation by asking: what are my people going to need to be able to do next year, or two years from now, if we build the business we say we want to build?
That is the question AMI believes leaders need to be asking more often. Because the organisations that scale successfully are not necessarily the ones that grow fastest. They are the ones that deliberately build the leadership capability, decision-making structures, systems and learning cultures required to support that growth.
Growth tells you that the business is getting bigger. Scale tells you that the organisation is getting better at handling bigger.
So before adding another layer of people, another process or another technology investment, leaders should ask a harder question: Can the way we currently lead support the organisation we are trying to become?
If the answer is no, the next stage of growth will require more than more resources. It will require a different organisation.
Ready to build the leadership capability your next phase of growth demands? Explore AMI's Leadership Development Programme to equip your managers and leaders with the skills, judgement and practical tools to lead people, make better decisions and build organisations that can scale.
Comments