Team reality

The Director Who Couldn't Delegate

Six direct reports, a backlog reviewed line by line, a team waiting on calls it was hired to make. The promotion was right. The training never happened.

The Director Who Couldn't Delegate
Illustration · Deimar Gutiérrez

Marcus ran 6 direct reports and a backlog he was still reviewing line by line. His team waited on him for calls he'd hired them to make. Approval cycles that should have closed in hours were running three to five days. Two of the six had stopped surfacing edge cases, because they'd learned he would take the decision back. Team velocity had dropped roughly a fifth since his promotion.

Promoting Marcus was the right call. He was the strongest IC on the team, the most fluent in strategic context, the most senior in tenure. The vote was unanimous. What never happened was training him to be a director, because the company had no such training. The unspoken assumption was that the best IC would intuit the job.

He didn't intuit it. He delegated reluctantly, second-guessed the handoffs he made, and pulled work back whenever the team's first attempt looked different from his own. None of it was malice. It was the predictable behavior of a senior IC rewarded for individual judgment and never coached to let a team be wrong on the way to being right. I've written before about how promoting your best engineer costs you the IC and rarely produces the manager for free.

This is the most common failure in growth-stage director promotions. The company elevates the best IC. Everyone agrees it's a management role. Then the actual transition, from doing the work to enabling the work, gets left to the new director to solve alone. Most don't solve it cleanly. Some never do. The team below them runs at reduced velocity for the length of that learning curve, which can stretch past a year.

The cost hides in plain sight. From the outside the function looks operational: the team ships, meetings happen, reports get filed. The drag lives underneath, in the slow approvals, the edge cases nobody raises, and the senior people who quietly checked out. None of it lands in a standard performance metric. It surfaces months later, when a strong report resigns and the exit interview names the director's decision-making as the reason. That's the same dynamic behind a promotion that quietly kills a function.

What works is unsentimental and cheap. Give the new director an external coach for the first six months. The coach meets weekly. The first handoffs get reviewed together: what was delegated, how well the context transferred, and what the director did when the team's execution diverged from his instinct. The coach isn't there to lecture on delegation in the abstract. The coach is there at the exact moment the old IC reflex tries to override the new manager one. That presence is what changes the behavior. If you're unsure whether you're delegating or offloading, I've drawn the line between delegation and dumping.

Most growth-stage companies skip this because it looks like a luxury. A coach engagement runs a few thousand dollars a month, against a director role that already feels expensive. The math is hard to make up front. The velocity you preserve is invisible. The report who doesn't quit never shows up as a save. The cost feels speculative.

It isn't speculative. Run an under-trained director for a year and the bill includes a departure or two, a stretch of compressed team velocity, and the founder's own time spent later repairing or replacing the role. That aggregate lands in the low six figures, conservatively. The coach costs the low five. The comparison isn't close.

The deeper habit is to treat promotion into management as a change of role, not a change of title. The role needs a different skill set. Most companies say this in their review rubric and then don't fund it in their development budget. Saying it isn't the commitment. The budget is.

Marcus found his footing eventually, after about ten months and one resignation. Velocity recovered. By his second year he was a genuinely good manager. That intervening year was the price of promoting him without supporting him.

Before your next director-level promotion, ask:

  • Has this person ever managed a function the way the new role demands, or are we betting on potential?
  • What management training will the company provide in the first six months, and who owns making sure it happens?
  • What specific behavior or tradeoff will tell us the transition has happened?
  • Are we willing to fund a coach, or are we hoping the candidate figures it out?