Last updated: August 2026

Most product leaders step into the Director or Head of Product role expecting more of what made them good, better instincts, more context, cleaner decisions. What they find instead is a different game.

The skills that got you here don’t automatically transfer. The expectations change. And the people above you are looking for something from you that nobody described in the job posting.

I’ve spent years coaching product leaders through exactly this transition, Directors, Heads of Product, solo PMs wearing every hat at lean startups. Here’s what I keep saying. Usually within the first few months of working together.

In this article

• 1. Move before you’re ready
• 2. Your judgment is the product
• 3. A no without justification is a delay tactic
• 4. Delegation is not assignment
• 5. Know which of your three levers you can move
• 6. Your CEO doesn’t know what you’re doing
• 7. Meeting saturation is a prioritization problem
• 8. Get a sparring partner
• 9. You’re not behind, the game changed
• The PACE Framework
• What to do with this
• Frequently asked questions

1. Move before you’re ready.

The product leader who waits until the strategy is airtight before sharing it loses weeks they can’t get back. And often, credibility too.

The people above you don’t need a polished deck. They need to see that you’re thinking at the right level, making calls, and moving forward. A 70% strategy document that gets refined in conversation is more useful than a perfect one that arrives three months later.

Send the draft. Call it a draft. Ask for input. You’ll get better work done and better relationships while you’re at it.

2. Your judgment is the product so trust it.

I see this constantly. A product leader in a lean org who keeps cycling back to consensus before making a call. Who waits for the CEO to weigh in before pushing forward. Who wants everyone to agree before committing to a direction.

That pattern shows up because the leadership seat is newer than the skills that got you there. But the org hired you to hold a lot of context and make a reasonable call in ambiguous situations. That’s the whole point.

Trust your read. Make the call. Revise if needed. That sequence builds credibility faster than waiting for consensus ever will.

3. A no without justification isn’t a no, it’s a delay tactic.

One of the most common things I hear from product leaders: “My no isn’t really empowered. They’ll just go to my skip, and she’ll say make it work anyway.”

That’s a real problem. But the fix doesn’t start in the moment the ask comes in. It starts well before.

The product leaders who can hold a line have done the work ahead of time: they’ve documented their priorities, they’ve aligned with their skip on what’s in scope, and they’ve made the tradeoffs explicit before anyone tests them. When the override comes anyway, they’re not defending a position. They’re pointing to a decision that was already made together.

You can’t earn the authority to say no in the same meeting where you’re trying to use it.

4. Delegation is not the same thing as assignment.

I was coaching a product leader recently who was frustrated that a delegated initiative wasn’t moving. When I asked how it had been handed off, the answer was essentially: I told him it was his. I checked in. He just wasn’t taking it anywhere.

Here’s what I’ve seen work: require a plan before execution. Not a long one. A paragraph or two covering the problem, the approach, the risks, and what success looks like. The act of writing that plan surfaces 80% of the confusion before anyone does any actual work.

Delegation works when the person doing the work has enough context to think, not just enough instruction to act.

5. You have three levers. Know which ones are actually yours to move.

Scope. People. Time. Every delivery problem comes down to one of these.

When headcount gets cut (and in lean orgs, it does), leadership will sometimes tell you the scope and timeline are staying the same. That’s not a constraint you have to accept without a conversation.

If the people lever is off the table, that means negotiating on scope or time. Document the tradeoffs explicitly. Bring the conversation to the right level before the deadline gets close. A product leader who names the problem early looks like a strategist. One who surfaces it at the end looks like someone who missed it.

You have more room to move on this than most people use.

6. Your CEO doesn’t know what you’re doing.

Strategic visibility isn’t self-promotion. It’s how the people above you stay aligned, stay on your side, and stay out of your way.

I talk to product leaders who are doing genuinely good work and are completely invisible above their direct manager. Their skip doesn’t know what they’re working on. Their CEO couldn’t describe their roadmap priorities. Their cross-functional partners don’t know when to expect what.

That’s a communication infrastructure problem, and it’s fixable.

A short written update. A quarterly check-in with someone above your manager. Making your priorities visible before someone asks. These aren’t political moves, they’re operational ones. The org can’t make good decisions about your function if nobody above you knows where product is headed.

7. Meeting saturation is a prioritization problem.

If your calendar is full of status meetings, you’re maintaining product, not leading it.

One Head of Product I worked with was spending a significant portion of her week in meetings that existed mostly to update people on what other people were doing. The fix wasn’t just saying no to meetings (though that helped). It was switching to async updates for anything that didn’t require a real decision.

When your calendar has space, something changes. You start thinking ahead. You have the conversations that are hard to schedule, with engineers, with customers, with your own team. You start making proactive moves.

Protect that space. That’s where the actual leadership work happens.

8. Get a sparring partner.

The leadership seat is lonely. Not in a dramatic way, in a practical one. There’s very little around you that gives you useful, unfiltered feedback. Your team is too close. Your manager is too busy. Your peers are dealing with the same pressures.

The product leaders I see make the fastest progress have someone outside the org to think with. A peer, a coach, a former colleague who will push back without internal stakes. Not someone who validates everything, someone who asks the harder question.

“Is that the real problem? What would you do if you couldn’t add people? What does your skip actually need to see from you right now?”

You don’t need a formal engagement. You need one person who will tell you the thing you’re not hearing anywhere else.

9. You’re not behind. The game changed underneath you.

I hear this a lot: “I feel like I’m always two steps behind. Like I’m constantly reinforcing the idea that I’m not strategic enough.”

Here’s my honest take: the PM role has changed more in the last three years than it did in the decade before. AI is generating more ideas, more analysis, more roadmap inputs than any team can process. The executive layer wants business impact more than it wants process. The frameworks that shaped how most of us learned the job (discovery, delivery, empowered teams), they’re still valid, but they don’t fully account for what’s happening on the ground in 2026.

You’re not bad at this. You’re navigating a fundamentally different version of the job than the one you trained for.

That gap doesn’t close by working harder. It closes by building the operating model that fits the situation you’re actually in, not the one the playbooks assumed you’d be in.

The PACE Framework

Nine lessons is a lot to hold. When I look across the product leaders I coach, four moves show up consistently in the ones who gain traction fastest, and they’re all counterintuitive enough that most people don’t do them naturally.

I call it the PACE framework.

P: Plan before you delegate. Require a brief before anyone starts work. The act of writing it surfaces the confusion before it costs you.

A: Act before you’re ready. Ship the 70% draft. Move on the incomplete strategy. Waiting for polish isn’t caution, it’s stall.

C: Create visibility before it’s needed. Your CEO and your skip should know your priorities before you need their support. Build that communication infrastructure now.

E: Establish your no in advance. You can’t earn the authority to say no in the same meeting where you’re trying to use it. Align on scope and tradeoffs before anyone comes with a request.

These four moves are the infrastructure of the leadership seat. The other lessons in this post matter, but if you’re starting somewhere, start here.

What to do with this

Pick one. Not nine.

Ask yourself which letter of PACE you’re weakest on right now. Then look for the one specific thing you’re not doing yet, the conversation you haven’t had, the document you haven’t shared, the calendar block you keep letting disappear.

That’s the place to start.

If you want to think through where you are in the leadership seat, I work with product leaders one-on-one. Book a call to learn more.

Joni Hoadley is a PM coach with 20+ years in product, including more than a decade at Sonos. She helps product leaders at startups build strategic clarity, lead confidently in lean orgs, and navigate the shift to AI-era product work.

Frequently asked questions

What’s the hardest part of stepping into a product leadership role?

It’s not the work, it’s the shift in what the job rewards. The instincts that made you a strong PM don’t automatically transfer, and the people above you start looking for judgment and business impact, not cleaner execution. Most new leaders feel it as the game changing underneath them.

How do you say no as a product leader when your manager can just overrule you?

You can’t earn the authority to say no in the same meeting where you’re trying to use it. The leaders who hold a line do the work ahead of time: they document their priorities, align with their skip on what’s in scope, and make the tradeoffs explicit before anyone tests them. Then a no is just pointing to a decision that was already made together.

What is the PACE framework?

Four moves that show up in the product leaders who gain traction fastest: Plan before you delegate, Act before you’re ready, Create visibility before it’s needed, and Establish your no in advance.

How do product leaders build strategic visibility with executives?

Not through self-promotion. Through a short written update, a quarterly check-in with someone above your manager, and making your priorities visible before anyone asks. It’s operational, not political.

Why do I feel behind even though I’m doing good work?

Because the PM role has changed more in the last three years than in the decade before it. AI is flooding teams with inputs, and executives want business impact over process. You’re not bad at the job, you’re navigating a different version of it than the one you trained for.