The first manager layer is a scale-up’s real operating test
A strong specialist is promoted to manager because they know the work, deliver consistently and have earned the team’s trust. Six months later, they are still solving the hardest problems themselves, their team waits for direction, and the founder is being pulled into disagreements that should have been handled much closer to the work.
The promotion made sense. What was missing was a clear definition of the new role.
This is a familiar transition in growing companies. People who built their reputation by delivering personally are suddenly expected to produce results through others. That requires a different use of time, authority and judgement, and a new title alone will not make the shift happen.
What changes when someone becomes a manager
An individual contributor can often measure a good week by what they finished. A manager has to look beyond their own output and ask what the team can now do independently. They are responsible for setting priorities, making trade-offs, giving feedback and resolving tensions before they reach the executive table.
In a scale-up, this becomes more difficult because the work itself keeps changing. Product priorities shift, customers ask for exceptions, and a funding plan may accelerate hiring before the management layer is ready. Managers need to give people enough direction to keep moving while recognising when a decision requires wider leadership input.
The founder’s behaviour matters here, too. Even after appointing a manager, founders sometimes continue giving instructions directly to the team because it feels faster and avoids unnecessary discussion. Over time, however, people learn that the real authority still sits with the founder. The manager remains accountable for results without having enough room to make the decisions needed to achieve them.
The practical question is straightforward: which decisions does the manager own, and which still belong to the founder or executive team?
Train for the conversations the role actually demands
New managers rarely need another collection of abstract leadership principles as much as they need practice handling the situations that come with the job. These include setting a clear outcome when the route is uncertain, giving feedback while the work is still recoverable, addressing underperformance before a formal review, and coaching a capable employee instead of taking the work back.
They also need to learn how to handle disagreement across functions. Escalating a problem is sometimes necessary, but a manager should be able to explain what has happened, outline the available options and recommend a course of action rather than simply passing the problem upwards.
A generic leadership course can introduce useful ideas, but development becomes more effective when managers practise these conversations using situations from their own company. They can review an upcoming customer commitment, work through a missed delivery or prepare feedback they have been putting off, then return to the situation to assess what changed.
Experienced leaders have an important role in this process. By explaining why they chose one trade-off over another, what evidence they considered and where they drew a boundary, they make their judgement visible. New managers can learn from that reasoning instead of having to discover everything through avoidable mistakes.
Look at the environment around the manager
When a first-time manager struggles, it is tempting to assume that the individual is not suited to leadership. Sometimes that is true, but often the role itself contains conflicting expectations.
A manager may still carry a full individual workload, leaving little time to lead. They may manage people across several countries without a clear operating rhythm, or be expected to improve performance while having little influence over pay, staffing or priorities. Training will only go so far if the structure makes the role difficult to perform well.
The executive team needs to look for patterns rather than treating every case as an isolated problem. Which decisions keep returning to the founder? Where do managers give conflicting instructions? Which teams depend on one particularly strong individual to keep delivery moving?
These are useful signals. They help show whether the company is genuinely building a management layer or simply adding titles to an operating model that has not changed.
A useful test for the next quarter
Choose one team and identify three decisions its manager should be able to make without the founder’s involvement. Agree on the boundaries, give the manager access to the information needed to decide, and review the results after a quarter.
Look at both the quality of the decisions and the amount of escalation required. If the team is making sound decisions and fewer issues need to return to the founder, the organisation has gained management capacity.
If the manager remains blocked, examine the authority, workload and support available to them before concluding that the problem lies with individual capability.
The first management layer is not simply another step in the organisational chart. It is where a scale-up begins to test whether its people can lead work through others, make decisions within clear boundaries and take responsibility without constant founder involvement.
How well that layer develops will influence how much complexity the company can absorb as it grows.
Related Insights
When “good performance” means something different in every team
Growth makes inconsistency visible. A product lead may reward speed, a commercial lead may reward persistence, and an operations lead may put reliability first. Each standard can make sense on its own. The trouble starts when people move between teams, managers make promotion decisions, or the board asks whether the organisation is ready for its next stage of growth. The company needs a clearer understanding of what good performance actually means—and whether that understanding is shared across the leadership team.
Read More
What progression and pay decisions reveal about a scale-up
The first difficult pay conversation often arrives before a company thinks it needs a formal framework. A strong employee has grown beyond their original role, another has been hired at a higher market rate, and a manager promises a promotion to keep someone engaged. Each decision seems manageable on its own. Taken together, however, these decisions begin to define how the company values contribution, recognises capability and decides what it is prepared to pay for.
Read More
Before hiring for a skill gap, find where the work breaks
A strong specialist is promoted to manager because they know the work, deliver consistently and have earned the team's trust. Six months later, they are still solving the hardest problems themselves, their team waits for direction, and the founder is being pulled into disagreements that should have been handled much closer to the work. The promotion made sense. What was missing was a clear definition of the new role.
Read More
Your team is only as strong as its weakest AI user
A founder starts reading things more closely than they used to. A client proposal, a board paper, a market summary. Nothing is clearly wrong, but some details cannot be verified. Gradually, more work needs checking before it can be trusted, and the responsibility falls on the same people. Uneven AI adoption is not just a skills gap. It is a leadership question about standards, ownership and accountability.
Read More
Leadership commitments hidden inside a Series A plan
A Series A plan can look straightforward on paper: revenue targets, a product roadmap, hiring plans and market expansion. But behind those numbers sit assumptions about leadership. Every growth target requires greater decision capacity, every new function requires meaningful ownership, and every expansion plan assumes the organisation can carry more complexity without sending everything back to the founder.
Read More
When European expansion exposes leadership weaknesses
A company can perform exceptionally well in its home market and still discover that it is not ready to operate across several European countries. Expansion often exposes weaknesses that were hidden by proximity, informal decision-making and founder involvement. The question is no longer simply whether the company can enter another country. It is whether the leadership model can travel with it.
Read More
Why an experienced corporate executive can fail in a scale-up
The CV looks right. The executive has led large teams, managed significant budgets and worked across several markets. Yet six months later, both sides are frustrated. Sometimes the hire was wrong. But often, the problem is not the executive's experience. It is the environment in which that experience was built — and whether that experience translates to a scale-up.
Read More
Why Scale-Ups Slow Down: Leadership Becomes the Bottleneck
As scale-ups grow, hiring feels like the logical next step. Yet in many cases, the issue isn’t who you add, but how decisions still move. Leadership becomes the bottleneck long before it’s recognised.
Read More
Leadership Problems Rarely Show Up as Failure
Growth can mask structural strain In founder-led companies, leadership problems rarely present themselves clearly. Revenue is growing. Customers are satisfied. The numbers look broadly fine. From the outside, there is no visible reason to worry. That is exactly why the issue is often missed. When nothing breaks, strain is explained away as normal growth. Slower […]
Read More