What Is Organizational Transformation, and Why Most Stall

Organizational transformation (organisational transformation, in British spelling) is a deliberate, large-scale change to how a company creates value: its strategy, structure, operating model, technology or culture. It differs from ordinary improvement, which makes the existing organization better at what it already does. A transformation changes what the organization is set up to do in the first place.

That is the definition. The more useful question is why so many transformations announce a new structure, run a year of workshops, and leave the company making decisions the same way it did before. The short answer is that most programs change what is visible, the org chart, the tools and the slogans, and leave untouched the things that actually govern behavior: who decides, what people are measured on, and how money moves. Everything below explains that gap and how to close it, with a worked example from the function we know best.

What counts as a transformation, and what does not

The word gets attached to almost any change program, which makes it less useful. Three distinctions help.

A transformation is not continuous improvement. Making a process faster or a team more efficient refines the current model. Transformation replaces part of it.

It is not the same as change management. Change management is the discipline of helping people adopt a change: communication, training, support. A transformation needs change management, but the transformation itself is the decision about what changes.

It is not just a restructuring. Moving boxes on an org chart is one lever among several, and on its own it changes remarkably little.

Transformations usually fall into a handful of types, often combined. Strategic transformations change what the company sells or to whom. Structural ones change how units are organized and how they relate. Operating model transformations change how work actually flows: processes, planning cycles, decision rights. Digital transformations change the technology and data the work runs on. Cultural transformations change the norms people follow when no rule tells them what to do. The last one is the hardest and is rarely achieved directly; culture tends to change as a consequence of changing the others.

The models, and what each is actually for

There is no single organizational transformation model, and the well-known frameworks are best understood as instruments that answer different questions rather than competing philosophies.

Lewin’s three-stage model, usually summarized as unfreeze, change, refreeze, answers the question of sequence. People and systems first have to be loosened from the current state, then moved, then stabilized in the new one. Its most useful insight is the last step: a change that is never refrozen drifts back.

Kotter’s eight steps, set out in his 1995 Harvard Business Review article on why transformation efforts fail, answers the question of leadership. Establish urgency, form a guiding coalition, create and communicate a vision, remove obstacles, generate short-term wins, consolidate gains, and anchor the change in the culture. It is essentially a list of the ways leaders lose momentum, arranged in the order they tend to happen.

The McKinsey 7-S framework answers the question of alignment. It treats strategy, structure, systems, shared values, style, staff and skills as interdependent, and its value is diagnostic: a transformation that changes strategy and structure while leaving systems and skills untouched will be pulled back toward the old configuration.

ADKAR, from Prosci, answers the question of individual adoption. Awareness, desire, knowledge, ability and reinforcement are the stages each person has to pass through, and it is most useful for finding where a particular group is stuck.

Use them together. Lewin for sequence, Kotter for leadership, 7-S to check alignment, ADKAR to diagnose adoption. The mistake is choosing one and treating it as the plan.

The seventy percent failure rate is not a real number

Almost every article on this subject repeats that seventy percent of transformations fail. It is worth knowing where that comes from, because it shapes how programs are run.

The figure circulated through management books of the 1990s and has been repeated ever since. When Mark Hughes examined the claim in the Journal of Change Management in 2011, tracing it back through its published sources, he found no valid empirical evidence supporting a single failure rate for organizational change. The number persists because it is useful to the people who sell help with change, not because anyone measured it.

That correction matters more than it sounds. Failure is common, but it is mostly unmeasured, because most programs never define success precisely enough to fail against it. A transformation that begins with a vague ambition will end with a vague assessment. The practical lesson is to decide before starting what would have to be observably different, and by when, for the effort to have worked.

Transformations stall where the org chart meets the calendar

Here is the pattern behind most stalled programs. The new structure is announced. Teams are renamed. Tools are bought. And six months later the organization is making the same decisions in the same meetings, because four things did not change.

Decision rights. If the same people still approve the same things, the new structure is decorative. Transformation has to state explicitly who now decides what, and remove the old approval paths rather than layering new ones on top.

Incentives and measurement. People do what they are measured and rewarded on. A team reorganized around customer outcomes but still bonused on its old departmental metrics will optimize for the old metrics, reasonably and predictably.

Money. Budgets encode priorities more honestly than strategy documents do. If funding still flows through the old units on the old annual cycle, the old organization retains control of what actually gets done.

Operating rhythm. The recurring meetings, planning cycles and reviews are where the organization actually thinks. If those stay the same, the conversations stay the same.

These four are the refreeze that Lewin described, and the systems in 7-S. They are also the least glamorous part of any program, which is why they are the part most often skipped.

A worked example: transforming a marketing function

Marketing is where many companies first feel the need for transformation, because the environment around it has changed faster than almost any other function. Channels have multiplied, measurement has become harder rather than easier, and automated platforms now make many of the decisions people used to make by hand. It is also the function we work inside every day, so it makes a useful case.

Most marketing departments are organized by channel: a search team, a social team, a content team, an events team, often each with its own agency and its own report. Each reports success on its own metrics, and each claims credit for the same customers. The transformation that works reorganizes around a single outcome, total new customers at an acceptable cost, and makes every channel accountable to that rather than to itself.

Applying the four levers makes the change concrete. Decision rights move from channel owners to whoever owns the overall number, with authority to move budget between channels. Measurement moves from channel-reported results to incrementality testing and a single source of truth the company owns rather than one each platform supplies. Money moves from fixed annual channel budgets to allocations reviewed on a shorter cycle and shifted toward what the evidence supports. And the operating rhythm moves from monthly reporting meetings, which describe what happened, to decision meetings, which decide what changes.

A few structural choices sit underneath. The company should own its advertising accounts, analytics and customer data regardless of who operates them, so that changing an agency or a team never means losing history. The split between in-house staff and outside partners should follow capability rather than habit: keep strategy, measurement ownership and customer knowledge inside, and buy specialist execution where it is cheaper or better. And testing needs to become a standing habit with a budget of its own, rather than something done when there is spare time.

Where does this usually stall? At the incentives. An agency paid on a channel metric, or a team bonused on its own reported numbers, will resist a structure that judges it on shared outcomes, and it will be right to by the terms it was given. Change the terms first. The honest starting point is a clear read of what currently exists: which channels run, who owns which accounts and data, how results are measured and who decides what. Most organizations discover their current state is less coherent than their org chart suggests.

When the transformation changes what the company is, the brand has to follow

Some transformations change the company’s strategy enough that its public identity no longer describes it. A services firm becoming a product company, a regional business becoming international, a company moving upmarket or into a new category: in each case, the internal change is well ahead of what customers see.

Customers experience a transformation last, through the brand, and a mismatch between what the company now is and how it presents itself costs trust in both directions. Existing customers are confused, new ones are not reached. That is the point at which repositioning the brand stops being cosmetic and becomes the external half of the transformation, and it is worth planning alongside the internal changes rather than after them.

How to tell whether it is working

Announcements, workshop attendance and new job titles are signs of activity, not of transformation. Better indicators are behavioral. Are different people making the decisions the program said they would make? Are decisions being made faster, and with different evidence? Has budget actually moved? Are the metrics people report on the ones the new model says matter? Would someone who left a year ago recognize how work gets done today?

If the honest answer to most of those is no, the transformation has not happened yet, regardless of what the org chart says. That is not failure. It is a signal that the program has reached the part that was always going to be hardest, and that is where the effort should now go.

Frequently Asked Questions

What is organizational transformation in simple terms?

It is a deliberate, large-scale change to how a company creates value, affecting some combination of its strategy, structure, operating model, technology and culture. The difference from normal improvement is scope: improvement makes the current model work better, while transformation changes the model. Most real transformations combine several types, with culture usually changing last and as a consequence of the rest.

What is the difference between organizational transformation and change management?

Transformation is the decision about what changes in the organization: its strategy, structure, processes or technology. Change management is the discipline of helping people adopt that change through communication, training and support. A transformation without change management tends to stall in adoption; change management without a clear transformation has nothing substantive to manage.

What are the main organizational transformation models?

The most widely used are Lewin’s unfreeze, change and refreeze model for sequencing, Kotter’s eight steps for leadership, the McKinsey 7-S framework for checking alignment across strategy, structure, systems, values, style, staff and skills, and Prosci’s ADKAR model for individual adoption. Each answers a different question, and they work best used together rather than as competing methods.

How long does an organizational transformation take?

It depends on scope, and anyone quoting a standard duration is guessing. A structural change can be announced in weeks, but decision rights, incentives, budgeting and operating rhythm take far longer to shift, and culture follows them. Rather than fixing a timeline, define in advance what would have to be observably different for the effort to have worked, and review against that.

Why do organizational transformations fail?

Most commonly because they change visible elements, the structure, the tools and the messaging, without changing the mechanisms that govern behavior: who decides, what people are measured and rewarded on, how budget is allocated, and how recurring meetings and planning cycles run. When those stay the same, the organization gradually returns to its previous way of working, whatever the new chart says.