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.

Great at being liked. Not yet great at being trusted.

By every external measure, the founder was doing well. He had raised a Series A, built a product people loved, and assembled a team that genuinely wanted to be there. He was warm, charismatic, and deeply committed to the company's mission. His team liked him. Most of them would have said so without hesitation.

But underneath the warmth, something was off. Underperformers were staying too long because nobody had a hard conversation with them. Decisions were delayed because he avoided anything that might create friction. When conflict surfaced between team members, it quietly got routed around him. Senior hires were leaving within a year, frustrated not by the work but by the lack of direction from the top.

The team had stopped expecting him to make the hard calls. They had started working around him instead of with him. That gap between the founder people liked and the leader people trusted was costing the company in ways that didn't show up on a dashboard.

"Everyone loves him. But I don't think anyone actually knows what he expects from them. Including me."

This is one of the most common and least talked-about leadership failures in early-stage companies. The founder who excelled at the scrappy, relationship-driven early days and never made the transition to leading an actual organization. Not because they aren't capable, but because no one ever told them the transition needed to happen.


You can't build around a leadership gap forever.

The challenge with this type of engagement is that the person who needs to change is also the person who hired you. That requires a particular kind of trust, and a willingness to deliver feedback upward, carefully and honestly, without losing the relationship that makes the work possible.

01
Naming what the team couldn't say
I spent the first few weeks listening to the team. Not to build a case against the founder, but to understand what the experience of working for him actually felt like. What I heard, consistently, was confusion. People didn't know where they stood. Feedback was rare and usually vague. Hard decisions got postponed until they became crises. Nobody wanted to say it out loud because they liked him. That's often how these situations persist.
02
The founder's feedback
Delivering this feedback required separating two things: his intentions, which were genuinely good, and his impact, which was creating drift. He wanted people to feel trusted and autonomous. What they actually felt was unclear and unsupported. That gap was not a character flaw. It was a leadership skill that hadn't been built yet. Framing it that way made it possible to hear. I was direct, specific, and grounded in what his team had experienced. Not what I thought of him personally.
03
Learning to lead through discomfort
The work that followed was coaching, and it was ongoing. We worked on the specific situations he avoided: the performance conversation he'd been putting off for six months, the misaligned senior hire he knew wasn't working, the co-founder dynamic that needed to be addressed directly. Each one was practice in making decisions based on what the business needed, not what would preserve the relationship or keep everyone comfortable. The goal wasn't to make him harder. It was to make him clearer.
04
Hiring the leaders he'd been avoiding building
Part of the problem was structural: he had delayed hiring strong leaders because strong leaders would require him to delegate real authority, which felt like losing control. We worked through what he actually needed versus what he was afraid of, then built a hiring process for two senior roles he'd been circling for over a year. Bringing in the right people with real ownership over their functions changed the dynamic significantly. He stopped being the bottleneck for everything.
05
Building the operating habits that replace personality
Charisma can carry a company to about 20 people. After that, it needs to be replaced by systems. We built a simple operating cadence: clear quarterly priorities communicated to the whole team, a regular leadership meeting with real accountability, and a direct feedback loop between him and his senior hires. None of it was complicated. All of it required him to show up differently than he had been.

He didn't become a different person.
He became a better leader.

Nine months in, the team had more clarity than it had ever had. The two senior hires were running their functions with real autonomy. The underperformer who had been quietly draining morale for a year had been transitioned out. The founder had led that conversation himself.

What changed wasn't his personality. He was still warm, still mission-driven, still the person his team wanted to work for. What changed was that warmth was no longer a substitute for direction. People knew what was expected of them. They knew where they stood. They trusted him. Not just liked him.

He told me late in the engagement that the hardest part wasn't the difficult conversations. It was realizing how much he had been prioritizing his own comfort over his team's clarity. That's the shift. When a founder makes it, everything else gets easier.

2
Senior leaders hired into roles the founder had been avoiding filling for over a year
0
Senior departures in the 6 months after the leadership shift
1
Founder who learned that being trusted and being liked are not the same thing

Think this might be about you?

That instinct is worth following.

Let's talk → ← Back to Work