Transformation Is Not a Project — It's How You Work
Many organisations treat transformation like a project. It gets a timeline, a budget, a project manager. It sits on the priority list next to delivery, alongside the reorg, alongside the product roadmap. And then, predictably, it loses. When the business needs to execute, when there's a reorganisation happening, when there are initiatives that can't slip—transformation gets deprioritised. Quietly. It's the work that doesn't have a deadline, so it gets pushed. And the organisation learns that change isn't actually a priority. If you've been through this once already—launched the initiative, watched it lose to delivery pressure, wondered why the org looks the same six months later—this is usually the reason.
The Capacity Problem
Here's what happens when you treat transformation as a separate initiative: the organisation is too busy doing the real work to also change how it does the real work. You reorganise the structure. You announce new ways of working. But you don't protect capacity for people to actually learn the new structure, to practice the new ways, to make sense of what's changing and why.
Even worse—you often stop sensing during the transformation itself. You're focused on executing the reorganisation, hitting the product milestones, managing the chaos. You're not paying attention to how people are actually experiencing the change, what's working, what's breaking, how people feel. You pause the inside work—the conversations, the questions, the psychological safety—precisely when people need it most.
Without that sensing and support, momentum dies. The new structure recreates old patterns. People are disoriented and unsupported. And the organisation learns that transformation is something that happens to them, not something they're part of building.
Transformation Embedded in How You Actually Work
Real transformation happens when it's embedded into how the organisation does its everyday work. Not a project. A practice. This means:
Leaders visibly protecting capacity for change—not talking about it, but actually doing it, even when delivery feels urgent
Sensing and observing the organisation continuously, especially during reorganisations and major shifts—because that's when people need it most
Coaching and practice embedded into the real work, not bolted on as training
The mandate to change coming from leaders, repeatedly, visibly, connected to why it matters
When transformation is embedded this way, it doesn't compete with delivery. It enables better delivery. People learn new ways of working by practicing them while doing the actual work. Leaders stay connected to what's real. And the organisation actually changes, not just on paper.
The Hard Part
This requires discipline from leaders. It means saying no to some things so there's space for change. It means staying curious about the organisation even when you're busy. It means repeating the "why" over and over, not just once in a kickoff. It means telling the organisation what is actually happening and what is seen in the organisation, along with highlighting the achieved deliveries. It means not pausing the inside work when things get hectic—that's exactly when it matters most.
But organisations that do this actually transform. The ones that treat it as a project? They reorganise and wonder why nothing actually changed.
This article is the third in a series of five articles about transformation. Most product transformations fail not because of wrong process or structure, but because leaders aren't present, honest with each other, or connected to what's actually happening. This series is about what actually works—and what doesn't.
