How Change Actually Spreads

Most product transformations fail not because the strategy is wrong, but because leaders launch the change and then disappear. Senior leadership aligns on the vision, briefs the organisation, and assumes the rest will follow. But in the middle—where area leaders are supposed to translate vision into daily work—silence. If those leaders are new to their roles, which is common when you shift from project to product organisation, they're left alone to figure out how to lead teams, set direction, run meetings, and model new behaviour. No shared language. No practice together. No sense of what actually works.

The result is incoherence. Some teams move forward, some stall, some go backward. Progress slows. People get confused about direction. And the transformation loses momentum before it gains any. The gap isn't in strategy—it's in leadership. The speed you want doesn't come from a better framework or a clearer vision statement. It comes from building the same sensing and problem-solving practice into every level of leadership so that small moves happen continuously, safely, and always in the direction you've set. That's what actually accelerates value delivery.

The Shift Nobody Plans For

The transformation you're launching won't work if it lives in leadership meetings. It works when every level—area leaders, product managers, team leads—starts operating differently. And the shift is simple: from a culture of waiting for direction to a culture of sensing what's broken and moving it forward.

Most organizations have built a waiting culture without meaning to. People see problems but don't act. They spot opportunities but ask permission first. They wait for the perfect plan instead of making a small move and learning. That culture is slow. It's also demoralizing—people disengage because they're not actually leading their own work.

What you're building instead is a culture of ownership. Every leader, at every level, develops the same practice: observe what's happening in your part of the system, probe what small move might nudge it toward direction, learn what works, and tell the story to mirror the successes to the organisation itself. That's not a framework. That's how the system learns to move itself.

When that happens, two things shift. First, speed increases because decisions don't wait for permission—they happen at the level closest to the work. Second, you build organizational learning into the daily rhythm, so change becomes normal instead of frightening. The organization learns to evolve on its own.

What It Looks Like in Practice

Consider a team stuck in a cycle of technical debt and bug fixes. The product quality has degraded, leadership is frustrated, and the team is disengaged. Why? Because nobody asked them what was possible. Leadership saw the problem, set the timeline, assigned the work. The team executed—or tried to—but without ownership. They were following orders, not leading their own work.

An area leader sees this and does three things. First, they sense the real problem: it's not the bugs. It's that the team has no say in what quality means or how to get there. Second, they probe by flipping the question. Instead of "here's what you need to fix," they ask "what do you as a team think is possible to achieve in this timeframe?" That single question shifts everything. Now the team is thinking like owners, not executors. They start seeing the system, spotting what matters most, making trade-offs. Engagement moves. Third, they narrate it—tell the leadership team and the organization why this worked. "When we gave the team agency over the plan, they took ownership of the outcome." That story spreads. Other area leaders start asking different questions. The culture begins to shift.

That's how change actually spreads. Not through announcements. Not through frameworks. Through leaders at every level developing the same practice—sensing, probing, narrating—in their own corner of the organization, every day.

When that practice is genuinely embedded, something important happens: the transformation stops depending on you to carry it. You're no longer the engine—you're the person who built an organization that knows how to move itself forward. That's what sustainable change actually looks like.

This article is the fifth 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.