The stall is predictable and preventable

McKinsey research on transformation stall patterns documents a consistent phenomenon: organisations that build genuine capability during a structured programme frequently experience a stall in the months immediately following programme close. The capability does not degrade. What disappears is the structure that kept it operational: the scheduled reviews, the accountability cadences, the facilitated decision points that sustained momentum. The stall arrives at roughly the three-month mark, which corresponds to the point at which the programme's implicit operating rhythm has fully dissipated and no replacement structure has taken hold.

What disappears when the programme structure is removed

What the programme provided was not just knowledge or tools. It was an operating rhythm: defined moments at which governance decisions were made, capability was reviewed and scaling decisions were taken. When the programme ends without an equivalent rhythm in place, the decisions that were being made in programme sessions begin to accumulate and then stop being made. The backlog is invisible until the momentum disappears. Teams that were making AI capability decisions weekly are now making them quarterly, then annually, then reactively. The capability does not leave the organisation. It becomes dormant because the mechanisms that kept it active are gone.

The organisations that sustain momentum design the operating rhythm before the programme closes

The organisations that maintain capability momentum after programme close are the ones that designed and scheduled the operating rhythm before the final session. Why does timing matter this much? After the programme ends, the competing calendar commitments of a functioning organisation make it structurally difficult to introduce new recurring meetings. The rhythm designed during the programme inherits the authority and commitment of the programme itself. The one introduced after programme close competes with every other business priority. Four cadences have proven durable: a weekly operational check-in for workflow owners, a monthly leadership review of capability and issues, a quarterly governance review that assesses the framework and approves new deployments, and an annual strategic review that updates the AI strategic thesis. The test of a durable rhythm is simple: could the programme lead leave the day after the rhythm is established and have AI capability continue to develop? If the answer is no, the rhythm is not yet adequate to sustain what the programme built.

·
Ready to build institutional AI capability?
Let's talk about your operating model.

setmode.io is a 14-module programme that closes the gap between AI adoption and organisational transformation. Every engagement produces named deliverables that form an AI-enabled operating model.

Start a conversation