A program meets its planned checkpoints because teams keep adapting locally, even after the operating assumptions behind the plan have stopped holding.

A national company was preparing a network of sites for the launch of a new operating model. Each site followed the same readiness sequence: facility changes first, workforce preparation next, then systems validation and final launch readiness.

The sequence worked during the early sites because the assumptions underneath it held. The required equipment arrived before workforce preparation began, local facilities were available on the planned dates, and the systems environment was ready when validation started.

As the program moved into a broader group of sites, one of those assumptions broke.

Equipment that had been expected before workforce preparation was no longer arriving in that order. Site teams kept their checkpoints intact by rearranging local activity, using borrowed space and shifting preparation into whatever time remained available.

At one site, managers moved classroom preparation into another area because the planned space was still being fitted out. At another, supervisors trained people on the new operating sequence before the final equipment configuration was complete, then scheduled a second local session once the setup matched the launch environment.

Both sites still completed the activities the enterprise plan expected to see.

The enterprise plan continued to show steady progress. Sites were completing the activities assigned to them, and the central program team was receiving status against the agreed readiness sequence.

The plan hadn’t become visibly late. It was becoming harder to execute .

Source link