The rollout had been stuck for a year.
The transformation program had been discussed for nearly a year, with process work, system changes, integrations, cleanup and training dependent on one large launch. The ambition was coherent, but the dependency chain prevented a complete usable improvement from reaching the team.
Launch one complete working journey
The pilot was selected for a meaningful operational outcome and an achievable first release. A baseline established current effort and processing behavior, then essential requirements were separated from features that could wait.
The future journey was designed before system work expanded. Process, data and integrations needed to connect end to end within the selected scope, while the wider target architecture stayed visible so the first release would support later growth.
Let the pilot inform the next release
The first release covered one complete journey, including integrations, user tasks and what to do when something failed. The team could use it from beginning to end.
Adoption and processing time showed what needed changing before expansion. The pilot still respected the wider architecture, so a local shortcut would not become a costly dependency in the next release.
Release one journey people can actually complete.
The pilot covered the full task, its users and a recovery path. That created a usable first release instead of another partially connected rollout.
- Select the outcomeThe journey has a meaningful operational benefit and a baseline worth improving.
- Connect the essentialsProcess, required data and integrations work together inside the chosen scope.
- Prepare live useThe relevant team can perform the work and recover from a release problem.
- Review before expansionAdoption, processing effort and friction inform the next rollout decision.
Adoption and processing time informed the next release. Going live was the start of the operating test.
Evidence from the pilot
The sixteen-week pilot produced a live journey, 86% adoption and a 30% processing-time reduction. Those results describe the selected workflow and user group. The wider program still required a rollout decision informed by integration effort, friction and actual use.
Adoption and the next rollout
Reducing scope was only useful if the released journey worked completely. A collection of disconnected partial features would leave the original operational problem intact, even if the program could report more tasks completed.
Reversible releases and a limited user group gave the team a way to learn before wider migration. Adoption belonged in the definition of done, since a launched workflow that users avoided would provide little evidence for the next investment.
A complete pilot gave the business something it could use and assess. Expansion depended on adoption and processing performance, with a recovery path available if the new workflow failed.