The Conversation Nobody Teaches Founders to Have

One of the things I've noticed working with founders is that there comes a point where the company starts asking something different of them than it did in the beginning. The founder who could build the company isn't always the same leader the company needs to continue growing. It's a transition almost every founder eventually faces, but very few people are ever prepared for it.

In the early days, success often depends on the founder being involved in everything. They know the customer better than anyone else. They've built the product, sold the vision, and made hundreds of decisions that no one else even knows existed. They stay close to every detail because they have to. That level of involvement isn't a weakness; it's often exactly what allows an early-stage company to survive.

As the company grows, however, that same level of involvement begins to create a different kind of challenge. There are simply too many decisions, too many people, and too many moving parts for one person to continue operating that way. Founders know they need to delegate. What they often haven't been taught is how.

One of the founders I was coaching recently found themselves in what I would call a classic delegation trap. On the surface, it looked like the executive they had hired wasn't taking ownership. Work kept coming back differently than the founder wanted, and they found themselves stepping back in to make sure things were done "the right way."

Except they weren't stepping back in directly.

They were shadow doing the work.

They were repeating conversations that the delegated executive had already had. They were going two layers down into the organization to gather their own read on what was happening, then making different decisions and giving different direction. Little by little, they were taking pieces of the work back without ever having the conversation that they were taking them back.

From the founder's perspective, this felt necessary. From the executive's perspective, it felt confusing. Role clarity began to erode, trust started to fray, and both people walked away frustrated. The founder felt like they couldn't rely on their executive, while the executive felt like they were never truly being set up to succeed.

As we unpacked what was happening, the founder said something I've heard many times before.

"I shouldn't have to tell them how to do this. That's what I hired them for."

I understood exactly what they meant.

When we hire experienced people, we expect them to bring expertise that we don't have. We hire a Head of Operations because they know how to build operational excellence. We hire a Head of Product because they know how to build products. We hire talented people because we expect them to bring judgment and experience to the table.

But I think there's an important misconception hidden inside that expectation.

There is a difference between someone's capability and their context.

A capable executive absolutely knows how to lead their function. What they don't automatically know is how you think about the business. They don't know the tradeoffs you've been making for the last two years. They don't know which customer relationship you're trying to protect, the mistake you're determined not to repeat, or the risks that keep you awake at night. Those aren't things that come with a job description. They come through conversation.

I sometimes joke with founders that they're trying to delegate through ESP. Somewhere in their mind is the expectation that the role definition, a few meetings, and a handful of conversations should be enough for someone to understand everything that's living in their head. When that doesn't happen, they become frustrated because the work isn't coming back the way they envisioned it.

The irony is that the frustration often isn't about the quality of the work. It's about the gap between the founder's unstated expectations and the executive's understanding of the assignment.

I've found that one of the most valuable things a founder can do before delegating something important is to ask themselves a few questions before they ever walk into the conversation.

What does success actually look like?

What are the guardrails that matter?

What decisions do I want this person to make on their own, and where do I still want to stay involved?

And perhaps most importantly, what am I worried about that I haven't actually said out loud?

That last question is usually where the conversation changes.

Naming your concerns isn't a sign that you don't trust someone. It's giving them access to the context you've been carrying around in your own head. It helps them understand not just what you're asking them to do, but why it matters. More often than not, that's the difference between someone simply completing a task and someone making decisions you would have made yourself.

Before the conversation ends, I also encourage founders to ask one more question: "Tell me what you heard."

Not because you're testing the other person.

Because you're testing your communication.

Those are two very different things.

The founder I was coaching didn't have a delegation problem. They had an expectation problem. They believed they had communicated far more than they actually had, and the executive believed they had been trusted to use their expertise. Both people walked away thinking they understood the assignment, and both were frustrated when the results didn't line up.

The more I coach founders, the more convinced I become that this is one of the first real leadership transitions they have to make. Delegation isn't about getting work off your plate. It's about making your thinking visible so someone else can succeed without you standing beside them.

It's a conversation we don't spend nearly enough time teaching, and yet it sits at the heart of whether a founder can continue to grow alongside the company they've built.

We’ll be diving deeper into conversations like this during SF Tech Week with a small group of founders. If this is a transition you're navigating, We’d love to continue the conversation.