You present the strategy.
It's clean. The logic holds. The numbers hold. The board nods.
Then nothing happens.
Three weeks later, sales is still pursuing a different motion. Engineering is halfway into a parallel bet. Marketing is still running last quarter's message.
It looks like an execution problem.
It's not.
It looks like a communication problem.
It's not that either.
Your strategy isn't failing on quality. It's failing on power.
This is where many strong product leaders get blindsided.
Not because their strategy was wrong. But because they walked into the room without knowing who just lost.
Every strategic choice redistributes power inside the company.
Every one.
When you pick a bet, you elevate some functions and demote others. You change whose numbers matter for the next four quarters. You change whose headcount gets protected. You change whose roadmap gets defended. You change whose story gets told in the next board update.
It doesn't feel like that when you're writing the slides.
It feels like problem-solving. It feels like analysis. It feels neutral.
It's not.
A strategy is never neutral inside a company.
The stronger the strategy, the more it reshapes the internal order. The better you've sequenced the bets, the more power you've moved.
And power that moves doesn't stay silent.
Here is the data point most product leaders underestimate:
By default, only about one in four people inside an organization actually understand and execute the strategy.
The rest don't oppose it.
They run on the incentives they already have.
Sales hits the comp plan they were given. Engineering ships against the delivery dates already booked. Marketing generates pipeline on the segments they know how to convert. Customer success protects the retention numbers their bonus depends on.
None of that is resistance.
It's physics.
A strategy that doesn't address those incentives doesn't get executed.
It gets absorbed — quietly, slowly, and without anyone ever saying no.
This is the phase most product leaders skip.
They treat strategy development as a co-design exercise. Gather inputs. Align on KPIs. Write the plan. Present the plan.
They assume adoption will follow.
It won't.
The plan that was perfectly co-developed will still slip.
Not because people disagree.
Because the plan never told them what to do instead of their current incentives.
So they keep doing what they were already paid to do.
Six months later the board reviews the strategy.
The numbers haven't moved.
Leadership concludes the product team didn't execute. The product team concludes leadership didn't support them.
Both are wrong.
What actually happened is simpler.
The strategy was never adopted.
It was approved.
And approval is not adoption.
This is the shift most product leaders have to make:
From writing a strategy that explains what to do →
To running the alignment work that determines whether it gets done
The first is a document. The second is a campaign.
The executive-level product leader does both.
They build the strategy. Then they build the incentive map before they present it.
For each function, they already know:
What this bet gives them in the short term. What it takes away. Where it conflicts with their existing comp or delivery pressure. What they might propose instead — and why.
That is not political work.
That is capital allocation work.
A strategy that cannot survive the incentive structure it lands in is not a strategy. It is a whiteboard exercise.
The incentive map is not complicated.
For each function, you answer four questions.
What does this bet give them in the window they are actually measured on? What does it take away? Where does it collide with their existing comp plan or delivery commitment? What could they propose instead — and how strong is that alternative?
This is not stakeholder management.
Stakeholder management asks who to talk to.
The incentive map asks who the strategy costs — and in what currency.
And there is a sequence that matters.
Talk to the function the strategy costs the most, first.
Not the one most likely to support it. Not the CEO. Not the function you have the best relationship with.
The one that loses the most.
You want the friction early and private. Not late and public.
By the time the deck is in front of the board, the hardest conversations should already be behind you — not resolved necessarily, but known. You should know who will object. You should know what they will say. You should have a position on it.
That is what moving through the organization with authority looks like.
Consider a VP I've been coaching — inside a PE-backed company, preparing her first board strategy.
Two bets. One the board will love on sight. One they have pushed back on twice before.
The quality of the analysis is not in question.
What determines whether either bet actually gets executed is somewhere else.
It's in the comp plans of the functions that have to carry it. It's in the delivery commitments engineering already made to the previous CEO. It's in whether the PE firms on the board — each with a different philosophy — will line up behind the same answer.
The strategy document doesn't touch any of that.
The alignment work does.
And the alignment work starts before the deck is written.
The traditional PM education does not teach this.
PM training teaches you to build consensus around a roadmap. It teaches you to listen, synthesize, and align. It assumes alignment is a conversation.
At the executive level, alignment is a calculation.
It is about knowing — before you walk into the room — which function will absorb the cost of your bet, which function will carry the benefit, and where the two don't cancel out.
The strongest product leaders I work with do this work silently. They map the incentive structure before they present. They walk into one-on-ones already knowing which part of the strategy conflicts with the listener's comp plan. They don't avoid those conversations. They start with them.
They don't present to the board cold.
They present to a room where the important conversations have already happened.
The deck is the last five percent.
There is one more thing worth naming.
If your strategy moves through the organization without friction, that is not a sign of quality.
That is a sign it didn't redistribute anything.
Easy adoption is the signal that nothing was at stake.
The strategies that matter create alignment conversations. Sometimes uncomfortable ones.
The better the strategy, the more of them you have.
The question is not how to avoid pushback.
It is whether you know, in advance, where it will come from — and whether you have a position ready.
There is one question worth asking before every strategy presentation:
Who just lost power in the strategy I'm about to present?
Answer that honestly, and you will know exactly where the pushback will come from. You will know which conversations need to happen before the room forms — and which parts of the strategy need to be defended versus bargained.
Most product leaders don't ask this question.
They write the strategy, ship the deck, and wait to see what lands. By then the alignment work is already behind them. And the strategy is already being absorbed.
The VP of Product who moves into a CPO seat — or the Director being promoted into VP — almost always makes this shift.
They stop thinking of strategy as a document.
They start thinking of strategy as a redistribution of authority inside the company, which happens to be written down.
The document is the artifact. The redistribution is the work.
A question to think about:
💬 When your last strategy didn't get approved — or got approved and then didn't really happen — did you see it coming before you presented, or were you surprised afterward?
Hit reply and tell me — I love hearing your thoughts. The replies shape what I write next.
This is the type of decision-making work I develop further with product leaders inside my Product Executive coaching cohort and advisory work.
We spend as much time on the incentive map as on the strategy itself — because the deck is never what determines whether the strategy actually moves.
Until next week,
Elena Leonova
Executive product & business-strategy leader
I work with senior product leaders, Directors, and VPs to help them master product strategy when decisions are high-stakes, ambiguous, and made at scale - where trade-offs matter and the cost of getting it wrong is real.
This newsletter reflects the thinking behind my work across:
• Product Executive education - From PM to Product Executive (Maven cohort)
• Advisory & coaching - product strategy and executive decision-making
• Writing & research - including my forthcoming book The Art of Platform Products