Built by a practitioner,
not by a methodology vendor.
Twenty five years inside enterprise transformation programmes, and the instrument that came out of it.
AI Change Loop is the innovation and ROI engine of enterprise transformation: architecture that embeds the right level of change into the system, so change becomes measurable, continuous value.
Who built this
I have spent twenty five years inside enterprise transformation programmes, as a change lead, a transformation lead, an OCM practice lead, and an advisor to programme boards and steering committees. ERP and core platform implementations, AI and automation deployments, merger integrations, operating model redesigns, across financial services, healthcare, manufacturing, technology and the public sector.
The pattern that kept repeating had nothing to do with the technology. Programmes failed structurally, and they failed late, after months of green status reports. The delivery plan was sound. The system worked. Nobody had measured whether the organisation could carry what was being handed to it.
The AI Change Loop is that observation turned into an instrument. Four pillars, twenty six instruments, six architecture layers, one measured scale, and the method published rather than described. I built and architected it myself, along with three books and the practitioner guide library that teaches the same architecture the platform runs on.
I am accountable for what this instrument claims and for what it refuses to claim. Both are on this site.
Where the practice came from
The instrument is an abstraction of programmes that actually ran. This is the ground it was built on.
How the instrument came to exist
Not a product roadmap. The sequence in which the observation became a method, and the method became something a client can run.
Programmes fail structurally, and late
Twenty five years of the same pattern. Green status reports for months, then a failure that had nothing to do with the technology. The delivery plan was sound. Nobody had measured whether the organisation could carry what was being handed to it.
Four pillars, six layers, one scale
The observation turned into a structure. Four pillars covering strategy, people, practice and learning. Six architecture layers underneath them, each scored on the same 1 to 5 scale so nothing is compared against a different yardstick.
Twenty six, prescribed not handed over
Each layer needed instruments that measure it rather than describe it. Twenty six of them, and the discipline that your readings select which ones activate. Nobody receives all twenty six on day one.
Published, so the method can be checked
Three books and a practitioner guide library. The architecture written down and put on Amazon, because a method nobody can inspect is a claim rather than an instrument.
From a reading to a governed lifecycle
A diagnostic produces a reading. A platform governs what follows: prescribed instruments, four recorded gate decisions, and a continuous pulse between them. That is the difference between measuring once and governing throughout.
How we work
Measured, never asserted
The model writes interpretation. It never writes the numbers.
Recorded, never remembered
A gate decision without a record is not a decision.
Published, not pitched
The scale, the bands and the limits are on this site.
Start with the free diagnostic
Ten questions and a measured band. The fastest way to see whether this is for you.
Loop Insights
Framework implementation, the Orien case work, and the questions worth putting to a steering committee. Published openly.
Read the insights