Leaders were ready to change how the whole function worked, and almost any group looked like a reasonable place to start.
Not Everywhere at Once
A global IT organization had done the hard diagnostic work. Its leadership team had turned dozens of findings into five themes, each with a defined outcome and a set of activities. Someone on the team asked whether all of it would now roll out across the whole function.
Yes, but not all at the same time. A change launched everywhere at once creates risk for everyone at once. A change pilot running in one area gives the organization a laboratory: a place to learn what works, what does not, and what needs adjusting before broader adoption, and just as important, how to adjust it. Scale the change before that is understood and all you scale is dysfunction.
Which left the harder question. Where?
Two Filters Before Any Favorites
The team put every area where a pilot could run on the whiteboard, one sticky note each. Many change efforts pick pilots for the wrong reasons: the least risky group, the one with the most problems, the most excited, or the first to volunteer. A pilot has to produce meaningful results and meaningful learning at the same time.
Candidates went through two filters, fit first, because it is quick and removes the most options. Fit asked whether the group's work mattered to the business, whether its demand crossed functional boundaries, whether it was willing to take part rather than being volunteered, whether it faced complications others would recognize, such as vendors, outsourced resources, and hybrid arrangements, and whether it was large enough to show real coordination patterns without adding so many variables that cause and effect blurred. Roughly, that meant three to nine delivery teams, or fifteen to forty-five people.
Readiness took longer and was more precise, looking at the group's product, process, and people, down to whether at least one leader would champion the change. A technical leader on the team summed up the whole filter in one question: would the pilot spend its time testing the changes, or building prerequisites? A pilot is meant to improve how work flows through an existing environment, not to construct missing foundations from scratch.
Fit cleared much of the board with little debate. Readiness removed more. Four finalists remained.
-
Every candidate area One sticky note each
-
Fit filter Value, boundaries, willingness, size
-
Readiness filter Product, process, people
-
Four finalists Three ruled out for cause
-
The choice One pilot group
-
The commitment Leaders commit Selection is not commitment
Three Good Groups That Were Wrong to Start With
The first finalist looked strong. Its work crossed boundaries, supported critical functions, and faced the same challenges the assessment had surfaced. But it was in the middle of a restructuring: reporting lines were changing and leadership responsibilities were shifting. None of that was bad. It made the pilot unreadable. One team member asked how anyone would know whether improvements came from the change or from the reorganization. With two major changes under way, cause and effect blur, and an ambiguous result is hard to scale. The group stayed on the list as a strong future candidate.
The second had the opposite problem. It was stable, its scope was well understood, and little was competing for its attention. One team member disagreed: it was too clean. The change was being designed to improve how work moves across boundaries, and this group had few of them. A pilot there might prove the approach in a controlled environment and say nothing about the messy places where most of the organization's problems lived. The worry was not that it would fail. It was that it would succeed too easily, and a successful pilot that produces nothing transferable is more of a problem than a failed one.
The third had strong fit and weak readiness, and its leaders had said so openly. Existing initiatives were consuming their attention, new requests were arriving faster than work could be finished, and team members had voiced concern about taking on another major effort. The room's conclusion was simple: when a group tells you it is not ready, believe it. Forcing a pilot on a group already struggling with its commitments creates resistance before the work begins.
| Finalist | Fit | Readiness | Decision |
|---|---|---|---|
| Group mid-restructure | Strong | Confounded | Later candidate |
| Stable platform group | Few boundaries | Stable | Too clean |
| Stretched services group | Strong | No capacity | Removed |
| Client-facing delivery | Strong | Leaders asking | Chosen |
The Group That Looked Like Everyone Else
The last note on the board was a client-facing delivery group. Its work crossed several business units. Vendor relationships were common, outsourced resources were involved, priorities arrived from several directions, and coordination across teams was part of every day. The more the team discussed it, the more it resembled the organization they were trying to improve. If the change worked there, the lessons would apply almost everywhere else.
Its work connected clearly to business outcomes, and its stakeholders were engaged, but its processes were not in good shape: work entered through multiple channels, intake was inconsistent, prioritization was reactive, and vendor dependencies added delay. Those findings strengthened the case. The problems were visible, the leaders understood them, and the change was designed to address exactly them. And long before the themes were formally named, this group's leaders had been describing the same challenges and asking for better visibility and better prioritization. The pilot would not need to create energy. It would give existing energy direction.
Selection was still not commitment. Interest expressed in interviews is not the same as agreeing to go first. The following week the team walked the group's leaders through the rationale, the readiness criteria, the projected time investment, and what being the pilot would ask of them. They asked how much executive engagement it required, whether ongoing vendor integration work might affect the timeline, and how success would be measured. Then they agreed.

What One Group Proved
The pilot ran for eight months under live demand. Intake paths were consolidated, delivery practices were standardized, release cadence moved from unstructured to defined intervals, and reporting began producing data leaders trusted. Not everything took hold. The new prioritization forum was running, but it was not yet the place where every priority call got made, and getting a team the resources it needed remained the weakest area the pilot group reported.
Because the pilot group carried real demand and its leaders put real constraints on the table, the results, including the unfinished parts, were credible enough to carry the model into other groups. A pilot in the clean group might have produced a better-looking result. It would have made a weaker argument.
Choose a pilot for what it can teach the rest of the organization, not for how easily it will succeed.
Share With Your Team
Choose who it is for. You send it yourself from your own email; Agileon never writes to your colleagues.


