You're not failing at product transformation. You're playing the wrong game.
Most transformation playbooks were written for companies that were already halfway there. What to do when yours isn't.
Please like ❤️ and restack 🔁 this article so others can find it, too. Thank you!
Something is wrong, but you can’t quite name it. The frameworks are in place. Roadmaps are clean. You’ve read the books, done the conferences, and you genuinely know what good product work looks like. And yet it’s not working. The culture isn’t shifting. The org isn’t changing. And somewhere in the back of your mind, quietly, a question has been growing: is it me?
It isn’t. But the honest answer is more uncomfortable than simple reassurance.
Stephanie Leue, a respected voice in product leadership, put it plainly: you’re not doing it wrong. You’re playing a different game than the one the books describe. And until you understand which game you’re actually in, no amount of effort, good intentions, or borrowed frameworks will get you where you want to go. This thought stuck with me, so let’s elaborate a little.
The advice wasn’t written for you
Pick up almost any book on product transformation and you’ll find the same story told in slightly different words. A company decides to change. Leadership commits. Teams restructure. Culture shifts. Results follow. It sounds logical, because in the right conditions, it is. But those conditions are almost never named, because the people writing those books didn’t have to think about them. They were already there.
Most transformation stories come from companies that had some product mindset baked in from the start. The advice that grew from those stories sounds universal. Restructure your org. Fix the processes. Align the incentives.
It gets repeated at conferences, packaged into frameworks, sold in consulting decks. And it works, in those companies, because the soil was already prepared. What you’re doing is applying a perfectly good recipe in the wrong kitchen. And then blaming yourself when the dish doesn’t come out right.
What you’re actually trying to do
You are not failing at product transformation. You are trying to drive a company-wide culture shift from inside a single function, without the authority, the budget, or the mandate that a real transformation program would have. That is a fundamentally different challenge. One of the hardest things you can attempt inside a large organization, honestly. The people writing transformation playbooks mostly never worked under these constraints. They had executive sponsorship, dedicated resources, and organizations that were already leaning in.
Naming this clearly matters. Not as an excuse. As an accurate diagnosis. You can’t treat the right problem if you keep misidentifying it.
Start small, and actually mean it
The most realistic path forward is to shrink your ambition deliberately, at least at first. Not because you lack vision. Because small is what actually works in resistant environments. Pick one team. Let them operate differently than the rest of the organization. Give them clarity on what they’re trying to achieve and the space to figure out how. Bake the new culture into everyday decisions and conversations, not into big announcements or transformation programs with names and slide decks.
This will feel slow. Sometimes invisible. Your stakeholders may not notice for months. Your peers may not understand what you’re building. But quiet, consistent proof is more powerful than loud promises.
A team that delivers better outcomes, communicates clearly, and treats customers like real people becomes something rare inside a large org. It becomes a reference point. People start to notice. They start asking questions. That’s the beginning of real spread. And it’s far more durable than anything you could have announced in a company-wide kickoff.
Trust people before they’ve earned it
This one is counterintuitive, and it makes some people nervous. The idea is simple: extend trust before it has been formally earned. Not recklessly. But intentionally, and in steps. Let someone own a decision they wouldn’t normally be allowed to make. Let another person represent the team in a room they’ve never been in before. Let a junior team member talk directly to a customer without you there. Each of these moments sends a signal that no culture document ever could.
People rise to the level of trust they are given. Not the level they are tested for. When someone feels genuinely trusted, they start behaving like the culture you’re trying to build, rather than the one that already exists around them.
Build one team this way. Make it a place where people feel real ownership, genuine clarity, and enough psychological safety to say when something isn’t working.
Then step back. Let others watch. Curiosity and quiet envy are far stronger change agents than any top-down mandate, and they cost you nothing.
Don’t burn out before the culture spreads
This is the part that doesn’t get written about enough. Good culture spreads on its own. But slowly. The real danger here isn’t that your strategy is wrong. It’s that you exhaust yourself, or spend your political capital too early, before the culture has had time to take root and become self-sustaining. And once you’re out of either resource, the whole thing stalls.
So be deliberate about where you spend your energy.
Take the loneliness seriously too. Not as something to overcome, but as something to plan for. Nobody will fully understand what you’re doing until it’s already working. Colleagues will question your pace. Leadership will push for faster results. You’ll spend a lot of time explaining a vision that hasn’t materialized yet to people who are, understandably, skeptical. That pressure is real. But it doesn’t mean you’re wrong. It means you’re doing something most people around you haven’t seen done before, and haven’t yet learned to trust.
You’re further along than you think
It’s easy to measure your progress against the polished transformation stories you’ve read, and feel like you’re standing still. But those stories are told in retrospect. Clean narratives. Clear turning points. They skip the years of quiet, frustrating, invisible groundwork that made them possible. You are in that part of the story right now. It doesn’t look like progress because progress at this stage rarely does.
Start with one team. One decision you hand over. One person you choose to trust a little further than feels entirely comfortable. That is not a small or timid beginning. That is exactly how this starts. And for the kind of change you’re trying to make, it may be the only way it ever does.
Please like ❤️ and restack 🔁 this article so others can find it, too. Thank you!
What I read
As usual, I will list some of the best articles I read on the Internet. I will keep a list of the best articles (currently >900) at https://www.digital-product-management.com. These are today’s picks:
With AI, Ship Less: Prioritize high-impact outcomes over feature velocity as AI reduces the cost of building and increases the risk of bloat.
Product Context Driving Growth: Use AI to transform existing product documentation and decision logs into reusable, situation-ready answers that accelerate growth.
Why Estimates Fail (And Why You Still Need Them): Navigate the tension between engineering uncertainty and organizational needs by using estimation as a communication tool rather than a deadline.
Benefits
Save 20 USD when subscribing to Proton: Secure, end-to-end encrypted email, calendar, drive and more.
Save 10% on the first month when subscribing to Krater.ai: Every AI You Need.
One Subscription.
Those are very good and accurate tips. They perfectly match my own experience as well. I completely agree.