NORBERT BIEDRZYCKI

Transformation Is Not a Project: Why Organizations Need Continuous Reinvention

Transformation Is Not a Project: Why Organizations Need Continuous Reinvention

Most transformation programs I have seen follow the same lifecycle. A diagnosis by consultants. A target picture. A roadmap with waves. A transformation office reporting to the CEO. A steering committee every two weeks. A closing celebration, typically eighteen to thirty six months later, with a slide that says “mission accomplished”.

And then, often within a year, the next transformation begins.

The project model is reaching its limits

The project model assumes that the world will hold still long enough for the target picture to remain valid. In 2024 that assumption looks increasingly fragile.

Consider what a typical three year program launched in early 2021 had to absorb: the end of cheap capital, a war in Europe, an energy shock, an inflation spike, the arrival of generative AI and a complete rethink of how and where people work. Its target picture was obsolete before the second wave began.

Generative AI makes this even more acute. The capabilities of the tools are changing every few months. Any roadmap that freezes a technology choice for three years will be wrong.

From program to capability

David Teece introduced the idea of dynamic capabilities decades ago: a company’s ability to sense changes in its environment, seize the opportunities they create and reconfigure its resources accordingly. For years it was an academic concept. It is now a practical description of what organizations need.

The shift is from transformation as an event to transformation as a capability. Instead of asking “what is our next program”, leadership teams should be asking “how do we build an organization that changes continuously without needing a program”.

What that looks like in practice

Strategy on a shorter cycle. Annual strategy reviews replaced by quarterly reallocation of resources based on what is working.

Funding teams, not projects. Persistent teams with stable budgets and changing priorities, rather than projects that are assembled and disbanded.

Transformation skills in line management. The capacity to redesign processes and adopt new tools should sit with the people running the business, not only with a central office.

A small, permanent change function. Not a transformation office that runs everything, but a team that builds methods, measures progress and helps the line.

ING’s agile reorganization, launched in 2015, is one of the better known attempts to build this kind of capacity at scale. Its lessons are mixed, and copying it wholesale rarely works. But it showed that the target is not a new structure. It is an organization that can change its structure without a crisis.

The risk on the other side

There is an obvious danger. Continuous transformation can easily become continuous restructuring. Employees who live through a reorganization every year stop investing in their roles. The fatigue I wrote about in 2022 becomes permanent.

The difference lies in what changes. In a healthy organization, priorities, processes and tools change frequently. Structures, values and the core contract with employees change rarely. Stability where it matters is what makes agility possible everywhere else.

Leadership question: Can an organization institutionalize transformation without turning itself into a permanent restructuring project?

Read next

  1. The Transformation ROI: Why Most Change Programs Fail to Deliver Their Promised Value

    Transformation and Leadership series, written in 2026

  2. The Transformation Imperative: Why Incremental Change Is No Longer Enough

    Transformation and Leadership series, written in 2026

  3. The Great Reset: Why Returning to Normal Is the Wrong Strategy

    Transformation and Leadership series, written in 2026