The Transformation Capability Management standard
v1.0, 18 October 2026
Its current custodian is BusinessGPS, the trading name of TechShifts Media Limited, which wrote the first draft. The aim is a committee with chairs drawn from outside BusinessGPS.
The standard governs an organisation's ability to change, across programmes and over time
Transformation capability management is the practice of treating an organisation's ability to change as something it holds, measures and governs, as it already governs its cash and its people.
This standard sets out principles for governing the ability to change across programmes and over time. It applies to change of any kind. Artificial intelligence is the pressing case today, both as a tool for making a change and as the change itself.
Consider a company that must replace its finance system in the same year as it integrates an acquisition. Each project has a plan. Neither plan says how much change the company can carry at once, or who may slow one project to save the other.
It sits alongside project, architecture and change standards, and replaces none
Project standards govern how a piece of work is specified, built and handed over. This standard governs the conditions around the work. It asks how much change the organisation can take in and who may slow or stop it. It also asks what the organisation keeps when the work is done. It sits alongside architecture standards and change-management standards as well, and replaces none of them.
For example, a project standard governs the plan to replace a warehouse system. This standard governs whether the warehouse can take in that change in the same quarter as a new staff rota.
The standard defines 3 terms, and 2 of them have a second use
Capacity is the time an organisation can give to change. Capability is whether it knows how to make the change well. A team can have the skill to run a new system and no hours in which to learn it, or the hours and no skill.
Both words have a second use in this standard. The capacity to absorb change is how much change an organisation can take in at once. A capability, in the singular, is one thing an organisation is able to do, such as running its payroll or judging a risk.
To absorb a change is to take in its consequences and keep them going without outside help. Installing a system is not absorbing it, and neither is seeing people use it. A change is absorbed when the organisation runs the new way of working unaided. Unaided does not mean that nothing is hired.
The 10 principles
1. Pace follows the capacity to absorb change
No change should move faster than the organisation can absorb its consequences. When more change arrives than people can take in, the changes fail, however good the technology. Consider a company that can carry one large change at a time and starts 3 at once. Each waits on the same few managers, and none finishes on time.
Evidence: a survey by Forrester Consulting for SAP, published in January 2026, of more than 1,000 senior decision-makers. In it, 52% named employee fatigue from continuous change as a barrier to success. It is a survey of opinion, commissioned by a software company, and not a controlled study.
2. Describe the work before automating it
Work that cannot be described accurately cannot be automated safely. Software built on a wrong description of the work repeats the error at speed. Consider a claims team whose written procedure leaves out the telephone call that experienced staff make before approving an unusual claim. Automate the written procedure, and the call stops being made.
Evidence: Deloitte's survey The State of AI in the Enterprise (2026 edition) reports that most companies had not redesigned jobs around artificial intelligence. It is one consultancy survey. The principle rests mainly on practice.
3. Decide what to own and what to hire, one capability at a time
The choice between owning a capability and hiring it is made for each capability, and made again at set intervals. Hiring is the right answer for routine work. Each decision to hire makes a later decision to own more costly. Left without review, those decisions add up to one that nobody took. For example, an insurer can hire out its payroll without loss, while its method for judging risk is what sets it apart.
Evidence: research on outsourcing published in the 1990s. Bettis, Bradley and Hamel (1992) describe outsourcing decisions that may each make economic sense and that together may give away the ability to compete. Prahalad and Hamel (1990) give tests for telling which of a company's skills are core. They warn that those skills cannot be hired in through outsourcing. Quinn and Hilmer (1994) set out which work to hire: activities for which a firm has neither a critical strategic need nor special capabilities. The warning is well established in that research. The research predates current software.
4. Treat working knowledge as an asset
An organisation's record of its decisions, the reasons for them and the instructions it gives its software are assets, and are governed as assets. Unless someone decides otherwise, this knowledge moves into a supplier's systems through ordinary use. Consider a finance system replaced 3 years ago. Nobody on the staff can say why a control was switched off, and the one person who knew now works elsewhere.
Evidence: thin. It rests on practitioner observation from 2026 and on the wording of the EU Data Act (Regulation 2023/2854). Article 2(38) of that Act leaves a provider's protected assets outside the data it must hand back. No study that measures the loss was found. Nor was any documented case of an organisation rebuilding judgement it had lost, or of a failed attempt to. Whether lost judgement can be rebuilt has not been measured, in either direction.
5. Evidence of a change has 2 parts
A change is judged on the value it created and on the independence the organisation gained. High value with falling independence is a dependency that nobody has counted. Independence with no value is capability on paper. For example, a programme halves the time taken to handle a claim and leaves the organisation unable to alter the process without its supplier. It has gained on one measure and lost on the other.
Evidence: 2 publications from 2026 support judging a change by its results. Kyndryl (February 2026) argues for asking whether the business case paid off, and not what activity took place. Deloitte (June 2026) describes measuring how artificial intelligence changes what an enterprise can do, beyond what it costs or saves. Neither measures the independence gained. That second measure is this standard's own. Both come from commercial firms, and neither is an independent study.
6. Governance is known by its decisions
A body that governs change must have the authority to start, order, slow or stop programmes, and must use it. A board that only receives reports is not governing. Consider a board that has read 12 monthly status reports and has never changed the order or the pace of a programme.
Evidence: one publication of guidance, and practice. In April 2026 KPMG and the INSEAD Corporate Governance Centre published 5 principles for boards that oversee artificial intelligence. They drew on more than 25 board members. KPMG's release says boards will need a clear view of how decision-making by artificial intelligence and by people should work together. It is guidance for boards and not a study. The test in this principle, that governance is known by its decisions, is this standard's own.
7. The consent of the people affected is a condition of change
Trust is governed before a change begins, not repaired after resistance appears. People who do not accept a change as fair work around it or withdraw from it, and the change is not absorbed. For example, staff who distrust an approved tool use an unapproved one, and the organisation loses sight of the work.
Evidence: surveys only. One is the Forrester Consulting survey cited under principle 1. Another is a Gallup survey of employees in the United States from the last quarter of 2025. It found 44% of leaders using artificial intelligence frequently, against 23% of the employees it calls "individual contributors". This is the least tested part of the standard.
8. Continuous change needs standing governance
When change never stops, an organisation needs a permanent function to govern it, not a project office that closes with each project. Project standards were designed for bounded work with an end date. Consider a retailer that replaces its warehouse system one year, its ordering system the next and its staff rota the year after. Each change gets a new team, and each team starts from nothing.
Evidence: 2 established bodies recognise the problem. In a research release of 12 May 2026, the Project Management Institute said organisations "have not built the human capacity and systems required to execute change continuously". The Change Management Institute publishes a maturity model for an organisation's "ability to lead, absorb and deliver change" (page read on 29 September 2026). Neither tests this standard's answer.
9. Independence is the measure of success
At the close of a programme, the question is whether the organisation is more able to govern its own change than it was before. A programme can meet every milestone and leave the organisation more dependent than it found it. For example, a new system goes live on time, and every later alteration still needs the firm that built it.
Evidence: Feeny and Willcocks (1998) identified 9 core capabilities that a business needs to exploit information technology. A UK National Audit Office report of 2014 found a public body dependent on its suppliers' technical capability. That dependence limited its ability to manage the contract commercially. The research is established for the outsourcing of information technology. It has not been repeated for software agents.
10. Classify capabilities first
Until an organisation knows which capabilities it must own, its other decisions about change have no frame. Choices of technology, staffing and programme all assume an answer. Consider a company that chooses a software platform before it has decided whether the work the platform supports is routine or is what sets the company apart.
Evidence: the research cited under principle 3. The claim that classification comes before every other decision is this standard's own, and it rests on practice.
The standard is organised in 6 domains
This release gives each domain by name and definition.
- Change absorption and capacity. How much change the organisation can absorb, how that limit is measured, and how it sets the pace.
- Transformation governance and decision rights. Who may decide what changes, in what order and at what pace, and who may slow or stop it.
- Work and operating-model redesign. Describing how work is really done, and redesigning it, before technology is applied to it.
- Capability sovereignty and ownership. 'Capability sovereignty' is an organisation's ability to understand, specify, judge and run again the things it depends on. The domain covers which capabilities it owns and which it hires. It is not about where data is stored or whose law applies to it.
- Value conversion and evidence. How spending on change becomes lasting strength, shown on 2 measures: the value created and the independence gained.
- Social licence and absorption trust. 'Social licence' is the continuing consent of the workforce and of others affected. The domain covers the trust without which a change is not absorbed.
The standard is reviewed every week, and each week has a public note
Each week has a dated release note. A change is made, documented and versioned only when it is necessary, and it is published and explained in the note, with the reason for the change and how strong the evidence is. Weekly commentary stays in the note. A formal revision is a new dated version of the standard. A week with no change to the text still gets a note, and the note says so. A change to a principle, or to the list of domains, is marked as one. Earlier releases stay available as they were published.
Citing the standard
To cite the standard, give its name, the release line at the top of this page and this page's address.