Release note, 7 October 2026
No change to the text this week, and one proposal: claim less ground
The Transformation Capability Management standard has a dated note every week. This is the note for the week of 5 October 2026. Transformation capability management is the practice of treating an organisation's ability to change as something it holds, measures and governs.
Nothing changed in the text
No change was made to the text of the standard in the week of 5 October 2026.
One correction is proposed, and it has not been made
The standard has a section, not yet released, that compares it with established bodies of knowledge. The draft of that section says every established body of knowledge is designed for bounded change. It also says none of them governs continuous change across a whole organisation. The draft reason under principle 8 makes the first of those claims as well, of project management, architecture, requirements analysis and change management.
The proposal is to replace that claim with a narrower one. Established bodies now recognise continuous change, and one publishes a maturity model for an organisation's ability to change. What the sources read so far do not hold is narrower. They hold no requirement that an organisation keep its own record of judgement, and no measure of the independence it has gained. They also show no standard that is updated weekly in public.
The draft claimed more ground than the evidence gives
The draft claim was tested against published sources on 29 September 2026, and it did not hold in full. A standard that overstates its ground gives a careful reader a reason to doubt the rest of it. So the claim should be cut back to what the sources support before the section is released.
The evidence is 2 published statements and one search
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". Its page says: "Change is no longer an occasional disruption. For most organisations, it is a constant operating condition." The page carries no date, and it was read on 29 September 2026.
A search of the field on 29 September 2026 found no standard with this one's scope.
That is enough to withdraw the claim that no established body addresses continuous change. It is not a survey of the field. So the narrower claim is provisional as well, and a fuller survey could cut it back further.
It would change one section and the draft reason under one principle
If the correction is made, it changes the section that compares the standard with other bodies of knowledge. It also changes the draft reason under principle 8. That reaches a principle, and it is marked here as one. The principle itself stays as it is: continuous change needs standing governance. On the standard's page, its reason already says only that project standards were designed for bounded work with an end date. The correction changes none of the 6 domains.
This note is dated 7 October 2026. It belongs to v1.0, 13 October 2026.
The standard's 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.