In many organizations, confusion starts with language. Teams say they are “transforming” a process and then assume the initiative is therefore a “transformation”. In practice, the label should be based on the scope and operating model’s impact, not the intensity of change within a single area.
By mislabeling, change, and transformation are not just semantic issues. It shapes expectations, drives the wrong delivery approach, and leads teams to measure the wrong things. A well-bounded operational improvement gets elevated into “transformation”, the narrative inflates, fatigue grows, and people become numb to the next initiative. In other cases, leaders face work that genuinely requires a shift in capabilities and identity, but they manage it like a standard rollout with a project plan and communications calendar.
The label is not cosmetic. It determines the design, the leadership posture, and the metrics. This article aims to illustrate the importance and to offer practical diagnostic guidance. Change and transformation in the business world are not interchangeable; they are distinct and should be handled very differently. Within both lies a third reality that leaders often underestimate: transition.
The three-layer leaders must separate
- Change is the visible work
Change is what you can point at: a new process, a system rollout, a restructuring, a revised policy, a new cadence of meetings. It is a visible shift from A to B and is often manageable through structured implementation discipline” (Lewin, 1947; Kotter, 1996).
Change can be significant. However, it tends to remain compatible with the organization’s existing logic: how decisions get made, how power flows, what “good” looks like, and what gets rewarded.
- Transition is the human reorientation
Although transition is a distinct layer, it sits underneath both change and transformation. It is the human process people move through, regardless of the size of the initiative. Transition is the psychological and social process of letting go of an old way of being competent, moving through uncertainty, and rebuilding confidence in the new state (Bridges, 2009).
This is where many “successful” implementations quietly fail. The process is live, the tool is launched, the training is complete, yet the behavior does not stick because the psychological transition has not yet been completed. People comply, but they do not commit to the long term and often revert to the old way of doing things.
- Transformation is a shift in organizational identity and capability
Transformation occurs when the organization’s underlying assumptions must change: what it sells, how it creates value, the capabilities it relies on, how it is structured, and how it learns (Burke & Litwin, 1992; Schein, 2010; Teece, 2007).
Transformation cannot usually be delivered solely through adoption tactics. It requires changes to the organizational system: incentives, governance, decision rights, talent choices, leadership behavior, and cultural reinforcement mechanisms (Schein, 2010).
Questions a diagnostic leader can use tomorrow morning
If you want to avoid “transformation theatre”, ask these five questions, but note that no single question provides a perfect classification; taken together, these signals help you diagnose whether you are dealing with change or transformation in most organizational situations.
Question 1: Are we improving performance, or changing how “value” is created?
- If it is performance improvement within the same process and value stream, then you are most likely experiencing a change.
- If the value proposition, customer promise, or business model must evolve, you are likely facing transformation (Teece, 2007).
Question 2: Can we fully specify the target state now?
- If the destination is clear and definable, it is typically a change.
- If the destination must emerge through learning, iteration, and sensemaking, it is more likely a transformation (Weick, 1995).
Question 3: What must people learn and unlearn?
- Change often requires training and learning something new.
- Transformation actually requires us first to unlearn what previously made the organization and people successful, which is psychologically harder and politically riskier (Schein, 2010).
Question 4: Do incentives and decision rights need to change, and at what scale?
If you can succeed with limited, local KPIs or incentive adjustments within the current operating logic, it is usually a change.
If success requires redesigning decision rights, governance, and incentives across functions, you are likely dealing with a transformation, because authority and reward mechanisms reside within the organization’s structure and systems (Burke & Litwin, 1992).
Question 5: Is this complex change within the current operating model, or an operating model shift?
If multiple teams are involved and the work can be integrated into the current operating model, it is usually a change, even when complex.
If success depends on redesigning the operating model and coordinating a portfolio of interdependent initiatives over time, it is more likely a transformation (Burke & Litwin, 1992; Schein, 2010).
The most common trap: confusing a “big change” with transformation
A significant change is not automatically a transformation.
A multi-country system rollout can be enormous, complicated, and seem to be impacting the entire organization. However, if the business model, decision logic, and the organization’s long-term strategy remain intact, it is still fundamentally a change.
The opposite is true of transformation; it can seem small at first, especially when it has only a minimal impact on the organization’s operating logic. The difference is whether they remain local improvements or trigger shifts in capabilities, governance, the definition of success, and the overall strategy over time.
The real test is not the size, but the depth.
A practical warning sign is the increasing number of “patch”-type changes being made to solve symptoms, but that do not resolve the underlying constraint. When you find yourself stacking changes on top of changes, it is worth rerunning the diagnostic and checking whether the operating model still aligns with the strategy.
What changes once you name it correctly
Correct labelling is not semantic. It determines the approach, the leadership posture, and the metrics.
If it is a change:
Focus on adoption and operational stability.
Define “what good looks like”, remove friction, and reinforce the new way of working until it becomes routine (Lewin, 1947; Kotter, 1996). Measure adoption and performance outcomes, including usage, compliance, cycle time, error rates, and service levels.
If it is “transition” heavy:
When people are letting go of an old way of doing things, communication alone is not enough. Leaders need to acknowledge the uncertainty; the people involved may even doubt their competency. You have to create space for questions, boost confidence through visible support, offer training, and celebrate early wins (Bridges, 2009). It is not enough to focus solely on compliance; if commitment is absent, the transition or change is incomplete.
If it is a transformation:
Focus on the operating model and capability.
Transformation requires more than adoption tactics and training. It will generally lead to a new strategy, often affecting who or where decisions are made. The organizations, governance, incentives, and KPIs will, in most cases, be completely redone. Transformation requires capability-building so the new assumptions are reinforced by the system itself (Schein, 2010; Burke & Litwin, 1992). Measurement and incentives should shift toward the desired state. Leading indicators of becoming different, such as decision speed and quality, cross-functional throughput, customer outcomes, and capability maturity (Teece, 2007).
A simple warning sign is a measurement mismatch. In change, adoption metrics such as training completion can be a meaningful part of the measurement set. In transformation, training metrics may still matter. However, they are not sufficient unless paired with system-level and outcome indicators that demonstrate whether the organization is actually operating differently.
A final thought
If leaders mislabel change or transformation, the work inevitably gets mismanaged. When leaders call everything a transformation, they create fatigue and cynicism. When they treat transformation like change, they rely on plans and communications while leaving the operating model untouched. The point of this diagnostic is simple: name the work correctly, then lead and measure it accordingly.
One final cause of confusion is perspective. A department can undergo a significant overhaul and experience it as “transformational”, especially when it has autonomy over its own processes. However, if it continues to function as part of a broader value stream, it constitutes an organizational change, and not a transformation.
Transformation occurs when the operating model needs to evolve or shift direction entirely, which alters how multiple “parts” work together.
External expertise can support transformation through analysis, facilitation, and capability-building. However, you cannot outsource ownership, accountability, and visible leadership, nor can it be delegated. If senior leaders keep behaving like the old organization while asking everyone else to become the new one, people will follow what is seen and done, not what is announced (Schein, 2010).
About Author
Doug Clark is a business leader, consultant, and author with 25+ years’ experience across operations, project delivery, general management, and organizational change and transformation. His career spans retail, technology, software, personal security, and manufacturing, with leadership experience across Africa, Latin America, and the Middle East. He is known for building practical execution systems that turn strategy into results, including operating rhythms, cross-functional governance, and performance frameworks that strengthen accountability and decision quality.
He writes at the intersection of leadership and management, with a particular interest in how organizations distinguish change from transformation and avoid “hero leadership” dynamics that create dependency and fragility. His work blends hands-on delivery experience with evidence-informed insight, translating complex ideas into actions leaders can apply immediately. Based in the UAE, Doug holds an MBA and is a Black Belt in Lean Six Sigma, and he is currently preparing for the PMP certification.
He supports organizations through consulting and delivery engagements and is currently open to senior leadership opportunities.
“Leadership and management are too often taught as theory without practical application. I write to bridge that gap with actions leaders can use.”
Discover more Leadership articles at Green Growth for MSMEs: How CSIR Is Driving Sustainable Manufacturing in India
