In this article, I want to explore the disciplines that claim ownership of the transformation body of knowledge. Strategy teams, Programme Managers, Business Architects, Technologists and Change Practitioners all have a legitimate claim, and each brings real depth. Each brings a way of understanding and managing change. Yet when any one discipline becomes the owner of the end-to-end endeavour, something essential can fall between the gaps.

Before asking who owns transformation, we need to be clear about what the word means.

What do we mean by transformation?

It is often assumed that transformation and change mean the same thing. The more I work in this field, the more I find “transformation” being used as an umbrella term that covers any kind of change. It is applied to a system upgrade, a restructure, a new product launch and a cultural reset alike.

In my view, Transformation is a change in what an organisation is capable of doing and how it delivers value. It sits at the far end of the change continuum. At one end are the incremental improvements every organisation makes: a refined process, a new tool, an adjusted role. At the other end is transformation. For change to be transformational, it has to shift the fundamentals of the organisation. That means how it creates and captures value, how it is structured and governed, how work flows through it, and how its people think and behave. If the operating model, the business model or the culture comes out the other side materially different, you have transformed. If not, you have changed, which is valuable but a different undertaking.

This distinction matters. Transformation touches everything at once, so it cannot be delivered through one lens.

The disciplines around the table

Now that I have set out what I mean by transformational change, let’s turn to the essence of this article: to prompt discourse on assessing transformation through the lense of the disciplines core to its success – I call them the Transformation Players. In doing so, I hope to show the danger of undermining a transformational effort by approaching it through the lense of any single method or management approach.

The Business Transformation Management Methodology, known as BTM², offers a useful way to see the breadth of that work. It brings together nine management disciplines: Meta Management, Strategy Management, Value Management, Risk Management, Programme and Project Management, Business Process Management, Transformational IT Management, Organisational Change Management, and Competence and Training Management. Its central insight is that transformation requires these perspectives to work together across the journey from envisioning change to optimising its results.

Each discipline answers a necessary question:

• Strategy Management: What are we trying to become, and why?
• Value Management: What outcomes justify the investment, and how will we know they have been achieved?
• Risk Management: What could prevent those outcomes, and what must be controlled?
• Programme and Project Management: How will the work be sequenced, governed and delivered?
• Business Process Management: How must work flow in the future organisation?
• Transformational IT Management: What technology and information capabilities will support that future?
• Organisational Change Management: How will people understand, accept and adopt new ways of working?
• Competence and Training Management: What skills must people build to perform effectively?
• Meta Management: How will leadership, culture, communication and decision-making connect the other disciplines?

A structural weakness in the field

Each of these disciplines is a mature profession in its own right, with its own bodies of knowledge, certifications and communities of practice. That maturity is also the problem. These disciplines have often been adopted separately from one another, and this has left a genuine structural weakness in the transformation field.

We see it in practice. A programme is delivered on time and on budget but realises none of its intended value. A new operating model is designed elegantly but never adopted. A technology platform goes live into an organisation whose roles and skills have not changed. In each case, one discipline did its job well while the connections between disciplines were left unmanaged.

Transformation therefore needs to be treated as an umbrella domain assembled from mature specialist professions, not as the property of any one of them.

This is why I see transformation as an enterprise integration challenge. Strategic intent must shape enterprise design; design must guide execution; execution must enable adoption; and adoption must produce measurable value. Risk, governance and leadership run through every stage.

The work of orchestration

BTM2’s central proposition is that the transformation disciplines must be orchestrated as peers within a larger transformation system.

Yet the field still lacks a universally accepted integrative professional standard: a shared way of connecting these disciplines into one coherent effort.

That addresses the requirement of knowing which expertise is needed and when, how one discipline’s decisions affect another, who owns decisions that cross professional boundaries, and how competing priorities will be resolved. If a proposed technology solution is faster to deliver but weakens the intended client experience, for example, the answer cannot sit with the technology team alone. It is a business decision informed by several disciplines.

Orchestration competence is not deep mastery of every discipline, and it is certainly not mechanical compliance with a framework. It is orchestration.

The transformation leader needs to know:

• what specialist capability is required;
• when it is required;
• how its outputs connect to other disciplines;
• who owns cross-disciplinary decisions;
• how disagreements between professional lenses are resolved.

BTM² calls this Meta Management. In my experience, it is the discipline organisations are least likely to resource, and the one that matters most. Mastering it matters more than mechanical compliance with any framework, BTM² included.

One model gaining traction to deliver this competency is where Business Leaders remains accountable for transformations and its outcomes. Alongside that Leader, Transformation practitioners provide a different capability: orchestrating the specialist work so that it forms one coherent journey

Does BTM² give us the recipe, or just the ingredients?

BTM² is the most complete attempt I have found at closing this gap. It is more than a structural framework. It sets out a four-phase lifecycle of Envision, Engage, Transform and Optimise, and gives each discipline its own activities, deliverables and methods, mapped against that lifecycle. Meta Management then provides the overarching frame: the leadership, culture, communication, structures and roles that link the disciplines together. In culinary terms, BTM² supplies the ingredients and a recipe for each course, served in the right order. What it cannot fully script is the head chef’s judgement in the moment, when the dishes compete for the same heat. When the programme timeline collides with change readiness, or the value case pulls against risk appetite, the framework tells you who is in the kitchen, not exactly how to settle the argument. That judgement is what I call orchestration competence.

Closing thought

Transformation is not owned by programme management, change management, architecture or technology. It is owned by the organisation, and it is delivered when these players perform as an ensemble rather than as soloists. The organisations that transform successfully are not those with the best individual disciplines. They are those that connect their disciplines around value.