Most definitions of transformation management describe an ambition. This one describes a job: deciding which parts of an organisation have to change, in what order, to what level, and proving afterwards that they did.
The short definition
Transformation management is the discipline of moving an organisation from one operating state to another, deliberately, across every dimension that has to move for the change to hold.
It is wider than project management, which delivers a defined output to time and cost. It is wider than change management, which handles the human adoption of a change somebody else has designed. It is wider than programme management, which coordinates related projects toward a benefit. Transformation management sits above all three and answers the prior question: what is the change, how far does each part of the organisation have to travel, who owns each move, and what evidence will show it happened.
Why every dimension is the whole argument
Organisations improve the dimensions they can see. Usually that is two: a system and a process. The cost of a transformation almost never sits in those two. It sits in the dimensions nobody assessed - decision rights, data quality, supplier contracts, capability, the incentive that still pays people to do it the old way.
Our framework, Total Change Management, holds a register of 42 dimensions grouped into three families: People, Process and Technology. Each carries its own maturity model. Each is mapped to the instruments that apply to it - over 300 standards, frameworks and methods, attached to the dimension they belong to rather than listed in the abstract. The register is not completeness for its own sake. It exists because a transformation fails in a dimension nobody assessed, and you cannot assess what is not on a list. The two, ten and forty dimension problem sets out why this is the usual cause of an expensive disappointment.
The two questions a transformation manager has to answer
Which dimensions, and which practices. Across all 42, which actually matter for this organisation, in this industry, at this moment - and inside each one, which standards, frameworks and methods are the right instruments. The output is a weighted shortlist, with the ruled-out dimensions named and the reason given. Naming what is out of scope is half the value; it is what stops the programme quietly re-acquiring it in month seven.
How far, in each one that fired. Inside a selected dimension: what maturity level is the organisation at today, what level is the right target - not automatically the top - and which practices carry it from one to the other. The output is a current level, a target level, the practices that close the distance, and what it costs.
Everything else in a transformation is execution of those two answers.
How maturity models are actually used
Badly used, a maturity model is a scorecard that makes everyone feel assessed and nothing move. Used properly it works in three modes. Descriptive establishes the as-is honestly. Prescriptive adds the rules and criteria that make the to-be actually happen - this is the part most assessments skip, and it is the part that completes the gap analysis. Comparative adds benchmarking across industries and regions, so the target level is argued rather than asserted.
Maturity that does not move is the standing failure of this field. That is why the framework carries more than 130 progress rules and an implementation super-process of over 50 sub-processes: the models say where you are, the rules make the number change.
What the end of a transformation assessment looks like
A costed, owned, dated plan over a three to thirty-six month horizon. Under it: the dimensions that fired and why, the ones ruled out and why, a current and target maturity level for each live dimension, the practices that close each gap, and the oversight processes required to keep it closed - named, with owners and a cadence.
If an assessment ends in a set of themes and a maturity radar chart, you have a diagnosis with no prescription. Ask for the prescription.
Where transformation management meets AI governance
Two of the 42 dimensions are AI governance and AI compliance, which is deliberate. An AI programme that is run as a technology initiative and not as a transformation is the clearest current example of the two-dimension problem: the model works, the workflow does not change, and the obligations attach anyway. If that is your situation, start with you do not have an AI problem and does the EU AI Act apply to my company.
Where to start
The honest starting point is not a strategy document. It is a gap analysis that names which of the 42 dimensions are live for you, and how far each has to move. We run that as a fixed-price week - the dimensions, the method and what the week produces - in Ireland, the United Kingdom, the United States and Australia, where we have representation. If you want to see who we have done this for first, the portfolio is public.