Don't Take Over. Earn the Handover.

The job description stated that I would own the product strategy.

The contract had a start date and a welcome Slack message from the CEO with a rocket emoji and three exclamation marks.

What was left unsaid, however, was that I didn't own anything yet.

He stopped the discussion twice to redirect conversations I thought I'd already closed. He wasn't being difficult; he just hadn't handed anything over yet. I'd been invited in, but that's not the same as being handed the reins.

This is where people typically get caught when they step into product leadership at a founder-led company.

And that first all-hands, where you stand up and everyone claps, makes it feel final. But of course, nothing actually transferred. What you have is just a seat at a table the founder still owns.

Why most new product leaders don't last in founder-led companies

The mistake I've seen most often, including one I made myself earlier in my career, is trying to establish the authority that was supposedly granted.

Reorganising the team. Revamping the roadmap process. At some point there's usually a workshop involving a framework the founder has never encountered, presented as the obvious way forward. All of it reads the same way to a founder: this person does not understand what we built or why it works yet.

The founder spent years making every call. They have views that are often right and occasionally very wrong, but they're always earned. They were in the rooms. They felt which things customers actually cared about and which things customers only said they cared about.

That understanding doesn't live in documents. It lives in them, in a way that's genuinely hard to transfer, and no amount of strategic competence changes that until you've demonstrated you actually get it.

What actually earns the handover

What earns the handover is a series of moments where you say something the founder wasn't expecting to hear from you.

You catch a decision before it goes wrong because you can see what happens three steps later. You speak to a customer and come back with something that changes how they see the segment.

You make the same call they would have made. And when they ask why, it makes sense immediately.

One moment builds on another. The founder stops needing to be in every room. Not because they've consciously decided to trust you. It's less deliberate than that.

At some point, it becomes low-risk to let you run, and they just do.

The pattern that fails, and why it's hard to spot

As I said earlier, the mistake is trying to establish authority too soon.

It feels like the right move. You're expected to lead, to decide, to show impact, right?

But coming in hard, too early, doesn't build trust. It just exposes what you don't know yet.

The new exec brings in frameworks from their last job. Because that's what worked before. Because it feels like progress. Because it's something they can control.

At some point, they pick up the pace. Faster than the founder.

Founders who built it from scratch know where the potholes are. They've hit a few. Avoided a few. And remember the ones that almost broke things.

Move too fast and you'll feel it pretty quickly. Not in a big, dramatic way. Just small things.

The founder starts getting looped back in. Emails you thought were yours now include them again. Nothing is said out loud. But something clearly shifted.

The version that works

The version that works: the exec treats the first six months as a learning period.

You stop looking at what's written down. Start noticing what actually matters.

Who the founder really listens to. Which decisions still carry weight. And which ones are just… still there.

You start to think the way they think. Not exactly the same, but close enough to see what they see.

You can't say this out loud. Describing it as an apprenticeship would be insulting. You just have to do it.

When the gap closes, the handover happens without a ceremony. The founder stops showing up to meetings, and nobody marks it as significant. You start getting fewer questions. Decisions stop being revisited. At some point, you realise you've been running this thing for a while, and the founder has moved on to something else.

That's the version worth waiting for.