A note: The situations in these case studies reflect patterns observed across many organizations over fifteen years of people work. Identifying details have been changed or composited. The dynamics, the decisions, and the outcomes are real.

The situation

Everyone saw it. No one said it.

The head of product had been with the company since the beginning. He and the founder had built the first version together, stayed up through the hard nights, and carried the company through its earliest pivots. The founder trusted him completely. That trust had become a kind of protection.

By the time I came in, three people had left in four months. Exit interview feedback pointed in the same direction every time: the environment felt punishing, feedback was unpredictable, ideas got shot down publicly. The team had learned to stay quiet in meetings and route their best thinking around him.

The founder knew. Had known for a long time. But this was his person, someone who had earned deep loyalty, who was technically exceptional, who made the product genuinely better. Letting it continue felt easier than confronting what it was costing.

"I've tried to bring it up a few times. It never lands. I think he just doesn't see it. Maybe no one has ever really told him in a way that got through."

The pattern I've seen many times: high performers who move into leadership roles because they're exceptional at their craft, not because they know how to build the conditions for others to do their best work. Over years, the feedback loop never develops. They become harder to manage, harder to reach. Not out of malice, but because no one has ever interrupted the pattern.

The work

The work nobody else wanted to do.

I started by listening. Not to the founder's read on the situation, but to the team's. One-on-ones with eight people across the org. What I heard was consistent: not a dislike of this person, but an exhaustion. People genuinely respected his capability. What they couldn't sustain was the unpredictability, the dismissiveness, the way disagreement felt like a risk.

01
Preparing the founder
Before anything could happen with the leader in question, the founder needed to get clear on what he actually wanted, and whether he was willing to act on it. This meant separating loyalty from accountability. We worked through what staying the course was actually costing the business, and what it would take to have the conversation without it becoming a rupture.
02
The feedback conversation
I led the first conversation directly — not as HR enforcement, but as a neutral party without history. I was specific, grounded in examples, and direct about the impact. He was defensive at first, which was expected. People who have never received real feedback often hear it as an attack. The goal wasn't to win the conversation — it was to put the truth on the table clearly enough that he couldn't unfeel it. We gave him time with it before any decisions were made.
03
Designing the path forward
Within two weeks, he came back wanting to understand what change could look like. This was the opening. We worked together, the three of us, to design a role that played to what he was genuinely exceptional at: product thinking, technical depth, strategic input. A principal-level individual contributor track, with real scope and visibility, but without people management. We involved him in shaping it. That mattered.
04
Building what the org actually needed
Removing someone from a management role creates a vacuum if you don't fill it thoughtfully. We hired a strong VP of Product with real people leadership experience, someone who could build the team culture that had been missing. We managed the internal narrative carefully, framing the transition as an evolution of his role, not a demotion. His standing in the company remained intact.
05
The exit scenario: when it doesn't take
In this case, the transition worked. But I've seen versions where it doesn't. Where the feedback doesn't land, or the person can't make peace with a changed role. In those situations, the work shifts to designing an exit that is fair, dignified, and protects the business. Amicable separations are possible, even from long relationships, when handled with care and clarity from the start.
The outcome

The team didn't just stabilize. It started to breathe.

Within 90 days of the transition, the mood inside the product team had shifted noticeably. Ideas were surfacing in meetings again. Two people who had been close to leaving changed their minds. The new VP of Product built quickly on a foundation that was finally ready for her.

The leader himself, six months later, told the founder it had been the right call. He hadn't realized how much of his energy had gone into managing the part of the job he wasn't suited for. He's still at the company today, doing some of his best work.

The founder's reflection: he'd waited two years. The conversation took forty minutes.

0
Additional departures in the 6 months following the transition
40 min
The first real feedback conversation, after two years of avoidance
Still there
The leader, 6 months later, in a role that actually fits

Recognize this situation?

Most founders do.

Let's talk → ← Back to Vivarium