Finding the atomic problem inside a transformation programme

Corporates · May 2026 · by Arpit Goyal

Every forty-slide programme hides one sentence worth solving. A field guide to extracting it before the committee does.

Every transformation programme we have ever read contains one sentence worth solving. It is rarely on the first slide. Sometimes it hides in the risk register. More often it sits in the appendix where someone quantified the leakage, or in a footnote written by the one analyst who watched the process actually run.

The programme exists because the sentence was too small to fund. A €2.1M reconciliation leak does not justify a steering committee; a "finance transformation" does. So the atomic problem is wrapped in strategy language until it is large enough to survive governance — and too large to ever be finished.

Our field method is extraction. We read the programme the way an editor reads a manuscript, looking for the sentence with a number in it, an owner near it, and a system behind it. That sentence becomes the engagement. Everything else goes back on the shelf, unharmed.

The committee can keep the programme. You keep the working system and the numbers. In our experience, the second thing quietly ends the first.

Annex — the sentence extracted from an innovation programme, running in production (Case 03)
Annex — the sentence extracted from an innovation programme, running in production (Case 03)