Henry rang me on a Thursday afternoon. He runs a 20-person professional services firm and four months earlier he had promoted his most senior delivery lead to manage a team of eight. The week before, three of those eight had quietly told him they were looking elsewhere. The new manager had introduced daily activity reports for the team, refused to make any decision without escalating to Henry, and started copying him into every internal email thread. Henry’s first instinct on the call was that he had picked the wrong person. By the end of fifteen minutes it was clear he had picked a fine person, given them no map, and was now watching the predictable outcome.
I have sat with several founders through some version of that call. The names and the team sizes change. The pattern almost never does.
What the failure rate is actually telling us
Gartner’s longitudinal work puts the first-time manager failure rate at sixty percent within two years, and the figure barely moves by industry, sector, or firm size. When a number is that consistent across that many cuts of the data, the cause is not the individuals being promoted. The cause is the structural setup they walk into.
The Chartered Management Institute’s UK research found that 82 percent of managers entering a management role here had received no formal management training. The honest reading is that the firm gave them no expectations, no permission to admit they did not know what they were doing, and no early correction when warning signs appeared.
A common founder reaction to this stat is to assume it applies to other firms. It does not. The figure includes promotions inside well-run owner-led businesses where the founder is thoughtful, the team is decent, and the chosen manager was capable as an individual contributor. None of that protects the manager once the setup is missing.
Why “we promoted the wrong person” is almost always the wrong reading
The “wrong person” reading is comfortable for a founder because it locates the problem outside the founder’s own decisions. The honest reading is harder. The firm picked someone capable, told them they were now a manager, and offered no written role, no clarity on authority, no permission to admit uncertainty, and no scheduled support. The new manager filled the gap with defensive assumptions.
I have only twice seen a first-time manager fail in a way that genuinely traced back to the wrong person being chosen. Both times the founder, looking back, could name the warning signs from before the promotion. In every other case the failure traced back to the firm’s setup, not to the manager’s character. The promotion decision is rarely the load-bearing one. The setup decisions in the first month are.
The fear cluster that drives the visible behaviours
First-time managers rarely fail from lack of effort or care. They fail from a small cluster of fears, and each fear has a signature behaviour the team can see from across the room. Fear of looking bad to leadership. Fear of losing credibility with the team. Fear of being taken advantage of by an underperformer. The manager themselves often cannot name which fear is driving them.
Fear of looking bad turns into over-control and bottlenecking. The manager refuses to make decisions without escalating, copies senior people into everything to manufacture cover, and shows up to meetings carrying written justifications for choices nobody questioned. Fear of losing credibility turns into blanket rules that treat the whole team like the worst performer. Fear of being taken advantage of turns into surveillance, time tracking, hourly check-ins, granular reporting requirements that did not exist before.
Each behaviour is rational from inside the manager’s chair. Each is visibly destructive from outside it. The high performers on the team feel infantilised, the underperformer is unaffected because the policy does not address the actual issue, and the whole team starts looking for somewhere they are trusted again.
The lowest-common-denominator trap
The behaviour I see most consistently in 10-to-50-person services firms is the lowest-common-denominator response. One person on the team is not pulling their weight. The new manager, unsure how to address it directly, introduces a policy that constrains everybody. Daily reports for the whole team because one person is patchy. Removing flexibility for the whole team because one person abused it.
The pattern is common enough in first-line management that researchers have a name for it. The cost is paid by the high performers, not by the underperformer. The high performers experience the new policy as a punishment for doing their job well, decide the firm no longer trusts them, and start interviewing within a quarter. The underperformer continues unaffected because the policy was not designed to address them in the first place.
By the time the founder realises three good people are leaving, the new manager has already burned the credibility they were trying to protect, and the original underperformer is still sitting at the same desk doing the same work.
The week-two test, and the part founders skip
The most useful diagnostic a founder has on a first-time manager is the week-two test. The fear-driven behaviours show up early. By the end of the first fortnight you can usually see whether the manager has started over-escalating, introduced surveillance, or written a blanket policy in response to one issue. Seeing any of those and deciding to give it time buys the firm three more months of the same pattern, deepening.
The honest part founders frequently skip is that a new manager’s failure is almost always preceded by signs the founder noticed and chose not to surface. The over-escalations were visible. The new reporting requirements were visible. The change in the team’s body language in the Monday meeting was visible. The founder made a note to address it at the next quarterly review and went back to a more urgent fire. The next quarterly review was three months too late.
The fix is operational rather than coaching-led. Write down the role and the authority that sits with it. Tell the new manager directly that “I don’t know yet” is the right answer when they do not have one. Schedule a standing thirty-minute check-in for the first ninety days. Address concerning patterns the week you spot them, with the same standard you want them to apply to their team. None of this is rocket science. Almost no firm does it, which is why the failure rate has not moved.
If any of this lands a little close to home, the conversation worth having is rarely about the new manager. It is about what the firm offered them in week one and what got noticed in week two. Book a conversation if you want a second pair of eyes on it before the next quarterly review arrives.
