Operators
Why most growth hires fail
The hire gets blamed. The system stays broken. The next hire repeats the cycle.
Most growth hires fail, and they usually fail for the same reason, which has nothing to do with the hire. They fail because they're dropped into an org with no operational infrastructure and asked to produce growth that the system underneath them can't support. The hire gets blamed. The system stays broken. The next hire repeats the cycle.
The pattern is recognizable on sight. A company hires a growth leader. The leader arrives, surveys the landscape, and discovers that the analytics are fragmented, the onboarding is manual, the pricing is untouched, and the retention motion is reactive. They spend their first year not growing the business but building the plumbing the previous two years neglected. The board, expecting growth, reads the year as a failure of the hire. The hire reads it as a failure of the system. Both are right. Only one gets fired.
The misalignment is structural. The hiring company expects the growth leader to drive the metric it can see, revenue. The growth leader needs to fix the systems that produce the revenue, which are invisible to anyone not doing the job. The expectation and the work are in different layers, and the lag between fixing the system and seeing the revenue is usually longer than the patience of the people watching the revenue.
There's a timing problem underneath. System work pays off in quarters; campaign work pays off in weeks. A growth leader who inherits a broken system has to choose: do the invisible long work that will pay off later, or the visible short work that will pay off now. Most choose the long work, because it's the right answer for the business. Most then get fired before the long work pays off, because the short work didn't move the number. The incentive structure is hostile to the right answer.
There's a scoping failure on the hiring side. The job description asks for a growth leader. The role, as it actually exists, is a growth leader plus a head of operations plus a data lead plus a retention owner, because none of those functions were built before the hire arrived. The hire is being asked to do four jobs and is measured on one. The math doesn't work, but it's invisible on the way in, because the org chart shows one box.
There's a sponsorship dimension that's usually absent. A growth leader fixing a broken system needs air cover from the CEO, because the work will look slow to anyone watching the dashboard. The hires who succeed have a CEO who has explicitly told the board that the first two quarters are build, not ship. The hires who fail have a CEO who nods at that idea in the interview and forgets it by the first board meeting. The air cover is the difference.
There's a diagnostic for whether a growth hire will land. Ask the hiring company what the growth leader will inherit: the analytics stack, the onboarding system, the pricing architecture, the retention motion. If the answers are vague, the hire will spend a year building, and the company will spend a year disappointed. If the answers are specific and funded, the hire can grow on day one. The interview question that predicts the hire's success isn't about the hire. It's about the company.
There's a flip side worth saying. Some growth hires do fail on capability, and the bad system frame can become a shield for underperformance. The way to tell the difference is whether the hire is building the system while the number is flat, or talking about the system while the number is flat. Builders ship the plumbing and the number follows. Talkers explain the number with the system. The distinction matters, and it's the distinction the CEO is actually paid to make.
Most growth hires fail not because growth is hard, though it is, but because the conditions for the hire to succeed were never built. The companies that get growth hires right build the system before the hire, fund the build during the hire, and protect the lag between system-work and revenue. The companies that get it wrong hire the leader, watch the number, and replace the leader, on a loop, while the system they never built keeps producing exactly the flat number they keep being surprised by.