For the past two years, I've been working with an organisation on a major transformation. The first phase went well, with clear progress, strong engagement, and measurable results. Then they layered on another significant change initiative. Now, despite everyone working incredibly hard, the work is stuck.
I've known the CEO for many years. Our monthly conversations aren't formal reviews; they're honest diagnostics. She doesn't want reassurance. She wants to know what's actually happening, where the real barriers are, and what she might be missing. Over time, I've noticed we always circle the same territory: Are people clear on why this matters? How are they really experiencing it? Where does authority actually sit? Are workflows enabling or blocking? What needs to shift in daily practice?
The 5 Lenses framework emerged from codifying that pattern, not just from this project, but from similar conversations across very different organisations over 3 decades. It isn't a methodology I impose; it's a map of how experienced leaders and consultants think when they're trying to understand why change sticks or stalls.
This organisation is doing a huge amount of activity. Teams are launching initiatives, running pilots, and firefighting local issues. The problem isn't effort or commitment. It's that they're acting before they see, diagnosing too narrowly or too quickly, then locking in solutions before they understand the system they're trying to change.
The question that changes everything is simple:
"What might we be missing?"
Asked honestly, it can save months of effort poured into the wrong places.
Complex organisations don't behave like simple machines with discrete parts. They behave more like ecosystems where everything connects, often invisibly, until something breaks.
That's exactly what's playing out in this project. Each team has sensible reasons for the changes they're making in their own area. But because nobody internally is looking at how these moves interact across the whole organisation, local optimisations are cancelling each other out. Some are even reinforcing the very patterns keeping the work stuck. From inside each silo, it feels like progress. From a whole-system view, it's wheel-spinning.
One conversation with the CEO made this visible. She said: "Every team thinks they’re doing the right thing." She was right, but they were each working to different implicit definitions of "right". What looked like poor coordination was more of a clarity problem: the purpose was clear at the top but fractured everywhere else.
In complex systems, the gap between action and outcome is large. We fix visible symptoms such as delays, frustration, and "resistance", but rarely touch the structures and assumptions producing them. What we notice depends heavily on our default lens: finance sees budget constraints, operations sees workflow issues, HR sees capability gaps, technology sees system limitations.
All might be partially true. None might be the leverage point.
A simple question to use daily:
"If this isn't the real issue, what else could be driving it?"
This isn't about doubting yourself; it's about checking whether you're looking at the right problem from enough angles.
Traditional change frameworks are designed to help you navigate once you know where you are and roughly where you're heading. They offer structure and shared language, which can be useful, especially in large, complex organisations. But they can only take you so far.
This organisation is using a light-touch, iterative approach, running experiments, gathering insights, and adjusting as they go. That worked brilliantly in Phase 1. But now, with multiple change layers and stretched bandwidth, their experiments keep addressing local symptoms rather than systemic patterns.
The problem isn't their approach. Most methodologies assume the hard diagnostic work has already been done. They help you navigate, but they don't tell you where you are. So you end up with plenty of structure but not enough shared sensemaking.
There are plenty of plans and artefacts: project charters, timelines, status reports, risk registers. The teams aren't short of process. What they're short of is a shared view of the system they're trying to change: why this work matters now, how people are actually experiencing it, where authority really sits, how work really flows, and what behaviours are reinforced day to day. Right now, the organisation has navigation tools but no shared map of the terrain.
This theory-practice gap, knowing what good looks like but struggling to implement it in context, explains why well-intentioned change efforts stall. It also explains why headline statistics about change "failure" are so misleading. Claims that 70% of initiatives fail ignore how rarely "success" is clearly defined, how context-dependent outcomes are, and how often benefits emerge over time rather than on a project end date.
The real question is:
"How will we define success in our context, given our constraints, culture, and capacity?"
In my conversations the same diagnostic questions keep surfacing, not because we're following a checklist, but because these are the places where complex change reveals what's really going on. I think of them as five lenses: five ways of seeing the same situation that each reveal something the others miss.
The diagnostic question:
"Does everyone understand why this change matters to our mission right now?"
That conversation about teams working to different definitions of "right" is a Purpose lens moment. As change layered on change, departments developed informal definitions of success. Local wins didn't add up to system-level progress because people were aiming at different targets.
When purpose is unclear, every other lens distorts.
The diagnostic question:
"Do we know how people are actually experiencing this change?"
When we were are puzzled over why a team pushes back on changes they'd helped design. The easy diagnosis was resistance. But when we explored workload and competing demands, the real issue emerged. They agreed with the change but had no capacity to implement it without something else breaking.
Leaders often believe teams have "bought in" because they nodded in the meeting. Meanwhile, people quietly adapt the change to make it survivable, not out of disagreement, but exhaustion.
The diagnostic question:
"Are decisions and authority aligned with what this change demands?"
Decisions that should take days are taking weeks, not because people are slow, but because informal veto power sits with people rarely in the room. It's not on any org chart, but everyone knows whose objection will quietly stall a decision.
Governance structures matter less than governance realities. Who actually makes decisions? Whose permission is sought? Who can stop progress without ever attending a meeting?
The diagnostic question:
"Are our workflows enabling progress or quietly blocking it?"
We'd launched new tools and procedures. The team asked: "If we follow a piece of work through the actual system, not the designed system, what happens?"
Mapping it showed why adoption was slow: people weren't being difficult, they were being rational. The new way required more steps, more handoffs, and more effort than the old workarounds. When the easiest path after the meeting is still the old way, that's the one people take.
Process isn't just about efficiency. It's about how work moves, where handoffs break, how information flows, and whether systems create friction.
The diagnostic question:
"Have we made the daily behaviours of change easy and visible?"
The Practice lens became clear when I asked: "What does this change look like in someone's Tuesday morning?" We realised we couldn't answer for most roles. Strategy had been translated into plans and communications, but not into behaviour.
Without clear expectations for daily practice, and support to make those shifts realistic, people default to old habits, even when they agree with the change in principle.
This is where change sticks or doesn't. You can redesign structures, improve processes, and clarify purpose, but if daily practice doesn't shift, nothing fundamentally changes.
The power of this approach isn't in examining each lens individually, but in how they interact:
In this project, the stuckness isn't one thing. It's the interaction of multiple factors that single-lens thinking can't see. The 5 Lenses create five conversations you've probably not been having, but urgently need.
Before reaching for the next big solution or system, pause. Resist the fix for a moment. Reach for a broader view.
Ask:
Which lenses have we looked through carefully, and which have we ignored because they feel uncomfortable or outside our day-to-day focus?
The 5 Lenses framework emerged from noticing that pattern across very different organisations. When experienced leaders genuinely try to understand why change isn't working, they instinctively ask versions of these questions. The framework simply makes that implicit practice explicit.
If you've got five minutes right now, try this:
Complex change doesn't reward perfect plans. It rewards the willingness to keep looking honestly, keep asking uncomfortable questions, and keep adjusting based on what becomes visible. It isn't a methodology but a practice. Like any practice, you get better by doing it repeatedly, with people you trust.
Over the coming months, we'll explore each lens in depth, not as separate boxes to check, but as interconnected ways of understanding why change sticks, stalls, or surprises you. The organisations that navigate change well aren't the ones with the most sophisticated frameworks. They're the ones that learn to see clearly together, keep looking again, and act on what they learn.
This article was co-created through a human-led process using several AI models – including ChatGPT, Claude, Gemini, and Perplexity – as thinking partners. It reflects our commitment to ethical, transparent, and accountable use of AI, where human judgement, curiosity, and oversight remain central.