Practice 06 · Operating model transformation
APEX.
Rebuilding how a function works, with the capability transferred rather than rented — and judged on what changed downstream rather than on what was deployed.
Any depth · Ignition through Transformation
01Why it exists
The problem underneath.
A great many AI programmes in this industry have produced pilots rather than capability. The pilots often worked. What did not happen is that anything downstream changed.
The distinguishing question is uncomfortable and rarely in the brief: six months on, is anyone’s daily work actually different? If the honest answer is no, the programme produced a demonstration.
APEX starts from work already being done rather than from a capability map, because the constraint is almost never the technology and almost always whether a person’s Tuesday changed.
What arrives: a capability gap map naming the actual constraint behind each gap — usually not the tool — a sequencing plan that starts from live work, and an honest assessment of what changed downstream.
02The boundary
The conflict we declare
We own the platform our engagements run on. Where APEX would have us assess whether that platform creates value for you, we say so before we start and will step aside for an independent assessor if you prefer. Selling you the audit of our own product is not a position we want to defend, and we would rather lose that piece of scope than defend it badly.
03How it runs
Senior judgement, on a method that already exists.
Runs as a Discovery Lab instance, usually followed by Deep Academy — an operating model nobody can operate is a diagram.
The person who scopes it delivers it. The structure — the questions in order, the evidence pathways, the review gates — is already built, so the engagement starts from a frame rather than a blank page. The reasoning is captured as the work happens, in your tenant.
And a person signs it. Where the machine sits →
04Fit
Who this is for, and who it isn’t.
It fits
A functional head or transformation lead who has budget, some pilots behind them, and a growing suspicion that the pilots are not compounding into anything.
It does not fit
An organisation that wants a transformation programme designed before it has one function working differently. We will propose the smaller thing, which is often not the brief.
05Proof
Read the output, not a case study.
Our clients have not agreed to be named, and a track record described by the firm that produced it is worth nothing to a buyer doing their job. So we bring the artefact to the first conversation instead — every section of what an engagement hands over, walked through before you commit to anything.