Organisational Transformation Starts with Measuring Change Readiness
I recently completed a course at IIM Indore on Digital Transformation, where there was a course on Change Management, Organisational Behaviour and Leadership that were part of the curriculum.
But one thing stayed with me long after the coursework. Is not a framework or a model, just a question that kept surfacing in different forms throughout the discussions.
Does the organisation actually know if it is ready to change?
In my previous blog, I did explore the Change Dynamics in Different Organisation types (Link); however, I had sensed that the critical question is how to know whether the organisation is ready for change.
After reading and talking to CXOs from different sectors, I sensed the ability to absorb, sustain and follow through on the change makes the organisation ready or not.
The Plan Is Not the Problem
When a transformation initiative fails, the first instinct is to look at execution. Was the plan poorly designed? Was the technology wrong? Did the team not deliver?
Sometimes, yes. But research consistently points to something more fundamental. Over 70% (sources: McKinsey) of change programs fail to meet their original objectives and the root cause, more often than not, is not poor execution. It is that the organisation took on a change that it was not equipped to absorb.
To understand how this plays out in practice, let’s understand the process in detail: a leadership team signs off on a major transformation and then a consultant develops the roadmap. Once the roadmap is finalised, the communication plan goes out and at least on paper, everyone gets aligned because it was ordered by the leaders. And then, somewhere between the kickoff and the 12-month mark, things slow down, resistance builds, priorities shift and the program quietly loses momentum.
Everybody just assumed they were ready and nobody assumed it would fail. However, the assumption was never tested.
Before You Define the Change, Understand the Organisation
This is where the Balanced Scorecard (BSC) becomes a surprisingly useful tool, not just for strategy execution, which is its most common use, but as a diagnostic lens before a transformation even begins.
The BSC was designed by Kaplan and Norton to give organisations a structured, multi-dimensional view of where they stand across four perspectives: Financial, Customer, Internal Processes and Organisational Capacity. Most organisations use it to set targets and track KPIs against strategy.
However, if used before a transformation, it does something more important. It forces leadership to look at the organisation as a whole system, not just from the top down.
Consider what a transformation actually touches. It is rarely just one dimension; for example, a digital transformation will affect how customers interact with the business, how internal processes are designed, what skills and technology the organisation needs and eventually, how costs and revenues shift. Those are not separate conversations, but they are connected and a gap in one will limit progress in the others.
When you lay a transformation agenda over the four BSC perspectives, patterns start to emerge. Are the internal processes mature enough to support the customer experience being promised? Does the organisation have the people capability and technology to deliver on those process changes? Is the financial case built on assumptions that the other three perspectives simply cannot support yet?
These are the questions that get skipped when transformation planning happens in silos, with strategy on one side, operations on another and HR somewhere in the background. The BSC brings them into a single frame and makes the gaps visible before they become expensive.
BSC’s cause-and-effect logic, where organisational capacity feeds internal processes, which drive customer outcomes, which then shape financial results, gives leaders a rational basis for deciding what needs to be addressed first. You cannot improve customer satisfaction sustainably if the underlying processes are broken. You cannot fix the processes if the people lack the skills or the systems to support them.
So before you ask “are we ready to change?”, the BSC helps you ask a more precise question: ready across which dimensions and where are the gaps?
Two Things That Are Often Confused
There is an important distinction between Change Readiness and Change Capability and conflating the two is where many organisations go wrong.
Change Readiness is about where the organisation stands right now. It is the starting point. How stable are the current systems and structures? Is the culture one that responds to disruption or resists it? Do people trust leadership enough to follow them through uncertainty? These are not soft questions. They are measurable conditions that determine how much change an organisation can realistically absorb at a given point in time.
Change Capability, sometimes called Change Agility. It is about how the organisation responds when change is introduced. Does it adapt, or does it freeze? Does it build new ways of working, or does it revert to old habits the moment pressure increases?
An organisation can be willing to change and still lack the capability to do it well. Willingness and capability are not the same thing. Readiness and agility are not the same thing. Treating them as interchangeable is one of the more common and costly mistakes in transformation work.
What the VUCA Reality Actually Means for Organisations
Sometimes it feels like a convenient way to explain why things are hard without really saying anything specific.
But if you sit with it properly, it points to something real. Organisations today are not dealing with one change at a time. They are dealing with continuous, overlapping forces of change, from markets, technology, regulation, culture and competition, often simultaneously and often unpredictably.
The models we have traditionally relied on, Kotter’s 8-step model, Kubler-Ross and others, were designed for managing specific change events like mergers, restructuring or new system (process) implementation. They are useful, but they were built for a world where change was episodic, not constant.
In a VUCA environment, the challenge shifts and it is not just about managing a single change initiative well. It is about whether the organisation has the underlying capability to keep changing as the environment demands. That requires a different level of organisational agility, one that cannot be assumed and cannot be built overnight.
This is also why the BSC diagnostic matters even more in a VUCA context. When external forces are unpredictable, knowing your internal state precisely, across all four dimensions, gives you a much clearer basis for deciding what to protect, what to change and in what order.
The Question Nobody Asks Before Transformation
Here is a scenario that plays out more often than organisations admit.
A company decides to go through a digital transformation. Leadership is committed, the budget is approved, transformation office is set up. And 12 months in, adoption is low, the change management team is firefighting and the programme is being quietly descoped.
What went wrong?
Often, the organisation simply was not at the functioning level required to absorb that scale of change. The culture was risk-averse, Middle management had never been through a transformation before and did not know how to lead through ambiguity. The processes were so deeply embedded that working around them felt impossible. The legacy systems were more entangled than anyone had mapped.
None of this was unknown. But it was assumed away, rather than assessed and planned for.
Every organisation, regardless of sector, operates at a certain functioning level at any given point in time. A manufacturing plant, a retail chain, a hospital, a bank. That functioning level determines not just how well the organisation performs today, but how much change it can absorb and how quickly it can build new ways of working. Trying to push a transformation that exceeds that level, without first building the foundations, is like upgrading a factory floor to full automation when the workforce has not yet mastered the current production system.
The question before any transformation should be: where is the organisation functioning today, and does the scale of change we are planning match that reality? If the gap is too large, you do not abandon the transformation. You calibrate it. You sequence it differently. You invest in strengthening the foundations before you push on the bigger change agenda.
Measuring Over Assuming
Readiness is not something you feel your way through. It is something you measure.
That means asking structured questions before a transformation begins. How aligned is leadership, really, not just in the room, but in day-to-day decisions? How has this organisation responded to past change initiatives? Where are the pockets of resistance, and what is driving them? What capabilities need to be built before the transformation can gain traction?
These are not tick-box exercises. They are the difference between a transformation that sticks and one that consumes two years of energy and budget before quietly fading.
The organisations that get transformation right are not necessarily the ones with the boldest vision. They are the ones who were honest about where they were starting from.
So, Where Does This Leave Us?
If you are involved in any kind of transformation, whether as a leader, a programme manager or an advisor, the most useful thing you can do before the plan is finalised is to test the assumption of readiness.
Not by asking ‘are we ready?’ in a town hall. But by actually looking at the conditions, the culture, the leadership bandwidth. How the teams have responded to change in the past. The organisation’s track record with disruption. Where the gaps are across people, process, customer and financial dimensions. Those gaps are not obstacles to the plan; rather, they are inputs to it.
The plan is only as good as the ground it is built on.
Transformation does not start with a roadmap. It starts with an honest assessment of where the organisation actually is.
If any suggestions/recommendations or help is required, please feel free to contact me.
