Not with a Bang, but a Whimper: Why Your Transformation Is Failing
All change is hard. But some change is the hardest.
I’ve had a hand in quite a few transformations over the years - from introducing goal-setting frameworks to overhauling discovery practices, from implementing new tooling to fundamentally reshaping how decisions get made. And I’ve noticed something that most transformation playbooks don’t talk about:
The most fundamental changes to company operating models aren’t hard to execute because of their complexity or scale. They’re hard because they directly challenge core beliefs about how the world works.
This isn’t about resistance to change in the abstract. It’s not about “change fatigue” or “organisational antibodies” or any of the other metaphors we use to avoid talking about what’s actually happening. It’s about something much more fundamental: When you change the operating context of an organisation, you’re asking people to reconstruct their understanding of reality itself.
And that’s not something you can workshop your way through.
The Hidden Architecture of all Organisations
We humans are inherently context-driven creatures. Our relationships to one another, our company’s power dynamics, and what behaviors are deemed “safe” and “unsafe” largely determine how we act - far more than any stated values or documented processes ever could.
This is an adaptive mechanism of human nature. In complex social environments, we learn to read context constantly: Who has authority? Where do ideas come from? Who gets rewarded? What happens when things go wrong? How is success defined?
These contextual understandings comprise the invisible architecture that holds all organisations together. They’re rarely written down. They’re certainly not in the company handbook. But they’re what everyone actually operates on.
And regardless of whether a transformation is ultimately for the better, once you start making deep changes to this grounding context, people will lose their footing. Because you’re not just asking them to learn a new way of approaching work - you’re asking them to unlearn everything they understood about how things worked around here.
The Axes of Fundamental Change
I’ve worked with companies at different stages of transformation, size, and maturity, and I’ve noticed the following axes along which transformations challenge core beliefs. These aren’t the only ones, but they’re the ones I see causing the most profound resistance - because they fundamentally reshape organisational reality.
Axis 1: Where Ideas Come From
The spectrum
Ideas come from the top (leadership defines direction, teams execute. So-called “feature factory”)
Ideas come from those who’ve proven themselves (earned authority through track record. If you want to break through, you require sponsorship)
Ideas come from everywhere (distributed ideation across departments, bottom-up innovation)
What’s actually being challenged
When you move along this axis, you’re challenging beliefs about authority, competence, and who gets to shape the future. An organisation where ideas come from the top operates on the belief that leadership has superior information, judgment, or vision. Moving away from this doesn’t just redistribute work - it fundamentally questions whether that belief was ever true. And that’s a terribly bitter pill to swallow if you’ve historically been ‘at the top’.
This is why “empowering teams” initiatives often fail. You’re asking all leaders to accept that their primary value isn’t having the best ideas. At the same time you’re asking ICs to accept that having ideas comes with real accountability - accountability they may not have signed up for or may not be ready to wield.
Axis 2: Who’s Actually in Charge
The spectrum:
Product is in charge (Product strategy drives decisions, Product Manager have real and meaningful impact over what gets worked on)
Sales is in charge (Market demand drives decisions, what sells is what gets built)
Engineering is in charge (Technical excellence drives decisions, Engineering leaders shape the roadmap)
What’s actually being challenged:
This axis determines whose judgment matters most when there’s conflict. In a sales-driven organisation, “the customer wants it” ends the conversation (a powerful argument in B2B environments where lucrative contracts with new clients can make or break a company).
In a product-driven organisation, customer behaviour and strategy are key. Validated prototypes and high-confidence indicators of behavioural change shape the future.
In an engineering-driven organisation, technical excellence stands in focus. Scaling, security, and the integration of new technologies are the priorities all other features work around.
Moving along this axis doesn’t just shift power from one group to another - it erodes the decision-making frameworks people have relied on. If you’ve spent years learning to win arguments by invoking customer requests, and suddenly strategic alignment matters more, you’ve not only lost influence - You’ve had to discover that the skills you developed to “get things done” are no longer sufficient.
Axis 3: What Failure Means
The spectrum:
Failure is bad (avoid it at all costs, you are punished when it happens)
Failure doesn’t exist (reframe everything as a learning, move goalposts to signify success retroactively)
Failure is good (seek it out, celebrate it, integrate it as a step to getting better)
What’s actually being challenged:
This might be the most psychologically loaded axis of all. How a company treats failure shapes everything from what risks people take (and how many!), to what information they share, to how they interpret their own competence.
Moving from “failure is bad” to “failure is good” is an often undervalued and overlooked aspect of customer-centricity focused transformations, where the road to customer value is littered with failed experiments. If you have a workforce that has built their career on not failing (especially publicly), being told that failure is now good and even desirable doesn’t feel empowering. It feels wrong - and like a trap.
The “failure doesn’t exist” middle ground is perhaps the most insidious, because it often means failure still matters enormously, but we’ve agreed to pretend it doesn’t. This creates cognitive dissonance that makes honest evaluation impossible. In many ways, it’s easier to go from “failure is bad” to “failure is good” than move away from “failure doesn’t exist”, because the latter contains interlocked layers of denial.
Axis 4: Who Owns Outcomes
The spectrum:
I am ultimately accountable for my product area’s success (I recognise and own the fact that I can succeed or fail)
My manager is ultimately accountable for my product area’s success (I have some responsibility, but only insofar as my immediate environment)
Nobody is ultimately accountable (I am at the mercy of the tides of my leaders and stakeholders, and that absolves me of any responsibility - note that this works even at higher hierarchical levels!)
What’s actually being challenged:
This axis determines what accountability in your company actually means. In organisations where individual PMs actually own outcomes, success and failure are personal. In organisations where managers own outcomes, PMs are somewhat involved, but ultimately they execute against someone else’s strategy. In organisations where nobody feels ownership over outcomes, accountability is pushed away to the point of meaninglessness.
The interesting thing about this axis is that the lowest level of accountability is often seen co-existing with accountability-heavy frameworks such as OKRs. Needless to say that if that’s the case, the accountability framework becomes pure theatre, and it’s in some cases even implemented in a way that reinforces low-accountability behaviour.
Each model here creates different incentive structures and different definitions of what it means to do the PM job well. Moving between them changes what ‘performing’ means. A PM who excels at autonomous ownership may struggle in a manager-driven model. A PM who excels at execution may struggle when given full ownership.
Bonus: The Data Special Case
And then there’s data. Data deserves particular attention because increasing data maturity isn’t typically framed as a “transformation” at all. It’s positioned as capability building: Giving people better tools and information to make better decisions.
But in practice, better data practices do something very disruptive: They make the invisible visible. They surface stories about success or failure that few people want to hear. They directly challenge what people believed to be true up until that point. I’ve seen it in action time and again.
When you introduce rigorous measurement to an organisation that hasn’t had it, you’re invalidating narratives people have built their reputations on. That feature everyone believes was successful? The data says 8% of users touched it. That market everyone thinks we’re winning? The data says we’re losing share. That strategy everyone’s proud of? The data says it’s not working - and it hasn’t been for the last three years.
This is why better data often faces fierce adoption resistance even when everyone claims to want to be “data-driven.” Because data-driven means being willing to let data prove you wrong, publicly and for all to see and verify. And that’s a fundamentally different world.
Why Traditional Change Management Fails
Most organisational change frameworks operate on the assumption that resistance is about fear of the unknown, lack of understanding, or insufficient buy-in. So they prescribe more communication, more training, more stakeholder engagement.
These things absolutely can help. But they fundamentally misdiagnose the core problem.
Because the problem isn’t that people don’t understand the change. The problem is that they understand it perfectly - and they can see exactly what it threatens.
When you’re moving an company along one of these axes, you’re not just asking people to learn new skills or adopt new processes. You’re asking them to accept that:
The competencies they built their careers on may no longer matter
The judgment they’ve honed for years may no longer be valued
The success they’ve achieved may have been circumstantial rather than earned
The reality they operated in may have been wrong all along
But most of all… that things are changing, and that they’re never going back to ‘normal’
This isn’t irrational resistance to change. This is people accurately perceiving that their position in the organisation’s social and power structure is being fundamentally renegotiated.
What This Means for Transformations
If we accept that transformations fail because they challenge core beliefs rather than because of poor execution, what does that mean for how we approach them?
1. Name What You’re Actually Asking For
Stop pretending that the transformation is just about new processes. Be explicit about which axis you’re moving along and what that means for how people will need to operate.
If you’re shifting from sales-driven to product-driven, don’t just talk about “customer centricity”. Acknowledge that you’re fundamentally changing which argument wins when there’s disagreement. This honesty won’t eliminate resistance, but it will at least make the resistance legible. People can engage with “I’m uncomfortable with how this changes prioritisation dynamics” in ways they can’t engage with “the rug’s being pulled from under my feet”.
2. Understand That Some People Will Lose
In any transformation that shifts fundamental context, some people will genuinely be worse off. Not because they’re incompetent, but because the skills and judgment that made them successful in the old context don’t transfer to the new one.
This doesn’t mean you shouldn’t do the transformation. But it does mean you should be honest about the fact that not everyone will successfully adapt - and have a plan for what happens to those people that doesn’t involve pretending they’re just “resisting change.”
3. Don’t Rely on Voluntary Adoption
Transformations that depend on people choosing to change will always fail, because the people most invested in the old context have the most to lose from the new one.
This doesn’t mean you should railroad people. But it does mean you need to create conditions where the new context becomes the default, not an option. Change the incentive structures. Change the decision-making forums. Change what gets recognised and rewarded. Simply put: Make it harder to operate in the old context than to adapt to the new one.
4. Accept That Culture Follows Structure
There’s a persistent myth that you need to change culture before you can change how work gets done. This is backwards.
Culture emerges from structure. If you change the structure, culture will eventually follow. But if you try to change culture directly through brand-new value statements and leadership messaging while leaving the old structure intact, all you’ll get is cynicism - from both sides of the camp.
This is particularly relevant for Product Ops practitioners who often get pulled into “cultural transformation” work. Your leverage isn’t in defining values - it’s in designing systems that make new behaviors the path of least resistance.
The Particular Challenge for Product Operations
All of this has specific implications for Product Operations work, because so much of what we do involves moving companies along these axes.
When we introduce better discovery practices, we’re often shifting where ideas come from. When we define decision rights, we’re clarifying who’s in charge. When we implement OKRs or introduce data accessibility, we’re changing how success and failure are defined and measured. When we create frameworks for autonomy, we’re reshaping accountability.
Product Ops work is by definition transformation work - whether we explicitly frame it that way or not.
This is why “process-only” Product Ops roles are so vulnerable. If you’re just facilitating ceremonies or managing tools, there’s no way you’re actually engaging with the deeper contextual shifts that determine whether product organisations succeed or fail. You’re optimizing within the existing context rather than reshaping it. And that might be enough for some - but be aware that optimisation gains can only get you so far.
Changing the World, One Day at a Time
I’ve found that when I struggle to make sense of transformation dynamics in my client engagements, it helps to remind myself that all companies are made up of humans, each with their own goals, wants, needs, likes, dislikes, histories, opinions, and baggage.
At the end of the day, that’s what makes transformation inherently difficult. The same psychological mechanisms that help humans navigate complex social environments also make us resistant to having those environments fundamentally restructured.
But that’s also what makes transformation work inherently fascinating. Because when you begin to understand these dynamics - when you can see not just what people are resisting but why they’re resisting it - you can design transformations that work with humans rather than against them.
And sure, you can’t eliminate resistance by understanding it. But you can make resistance legible. You can design around it. You can create conditions where the new context becomes survivable, then tolerable, then eventually, the new normal.
And that’s the real work of transformation. Not the three-year roadmaps or the communication plans or the training programmes. The real work is understanding what you’re actually asking people to give up, and creating conditions where they can survive the loss.