You’re not short on conviction. You’ve read Transformed. You’ve seen what happens when companies actually adopt the product operating model. And now you’re the person trying to make the case internally.
So why does the conversation keep stalling?
Here’s what I see with product leaders stuck in this fight: they walk into that exec meeting ready to justify the new model. Why it works, why teams that use it outperform, why leadership should trust the process.
And leadership says: “We can’t afford to slow everything down right now.”
Meeting over.
The problem isn’t your conviction. It’s your frame. You’re making it a debate about the new model when it should be a reckoning with the current one.
The objection you’re going to hear
Leadership’s real concern isn’t philosophical. It’s operational. They’ve seen transformation initiatives before. They know what “we’re changing how we build” means in practice — friction, confusion, slower delivery while everyone figures out the new way of working.
That’s a legitimate concern. And if you walk in pretending it isn’t, you lose credibility before you’ve made a single point.
Acknowledge it directly: “yes, there’s a transition cost. There always is.” Then pivot: “but let’s talk about what it’s already costing us to stay where we are.”
Most product leaders skip that pivot entirely. The moment you stop defending and start exposing, the conversation changes.
The number that changes the room
In Transformed, Marty Cagan writes that the percentage of features and projects on most roadmaps that actually generate positive ROI is somewhere between ten and thirty percent.
Sit with that for a second.
That means right now, this quarter, on the roadmap your leadership just approved — somewhere between seven and nine out of every ten things your team ships aren’t moving the needle. Not driving revenue. Not solving real customer problems. Just consuming engineering capacity and delivering nothing.
That is not a transformation risk. That is the current cost of doing nothing.
Most product leaders hear this stat and nod. Then they leave it out of the room. They don’t translate it into language their CFO cares about. They don’t make it concrete. That’s the miss.
If you want to go deeper on how to connect your roadmap decisions to commercial outcomes, I’ve written about that here.
How to make it land
Your CFO doesn’t think in product models. They think in money in, money out.
So translate it. Engineering hours spent building features that were abandoned six months after launch. Revenue that never materialized because the roadmap was a delivery schedule dressed up as strategy. Customer churn from problems that went unsolved while the team executed a stakeholder wish list.
None of that shows up in a transformation budget. But it’s happening right now. In your org.
When you surface this — specific and concrete rather than theoretical — you shift the entire frame. You’re no longer asking leadership to take a risk on something unfamiliar. You’re asking them to stop bleeding resources on something that isn’t working.
That’s a fundamentally different conversation. And it’s one you can win.
If you’re in this fight right now
The argument works. But getting it right — the framing, the data, the language that lands with your specific leadership team — is where most product leaders need support. If you want help thinking through how to walk into that room and come out the other side, that’s exactly the kind of work I do. Book a call at jonihoadley.com/apply.