A platform migration with a real business case is rolled out so that one group gets poor access, late training, and partial data, and the group drifts into irrelevance without anyone firing it.
An example
An engineering services firm moved its project delivery and pricing onto a new platform championed by a younger managing director. Her group and the platform team got early access, structured training, and a say in the configuration. The senior project directors, whose standing rested on client relationships and twenty years of estimating spreadsheets, were in the last training cohort and received view-only licenses at cutover. Only half their historical bid data was migrated. When one of them needed to issue a change order to a container terminal client, it took four days and a ticket to the platform team. The client's program manager called the managing director instead. Within two quarters, three of the senior directors had taken early retirement, and their accounts were reassigned to her group with no performance review on anyone's file.
Why it works
It works on all four fronts. Each person in the target group who disengages frees headcount, budget, and room for the sponsor's coalition. Removing the group directly would mean reviews, severance, legal checks, and a visible fight, and a neutral system migration avoids all of it. The group's expertise is stranded on a dying platform, and every routine action now costs a fight for access that looks like incompetence. Cover matters: the migration has to be defensible on its merits, the sponsor has to control provisioning, training, and data scope, the target group must lack outside sponsors, and rollout friction must be common enough that "they could not keep up" sounds plausible.
The thinking behind it
Oliver E. Williamson Williamson's The Economic Institutions of Capitalism (1985) describes asset specificity: expertise tied to one firm's systems loses its value outside that relationship. A migration turns a group's mastery of the old platform into a stranded asset overnight. That explains why the group's influence collapses so quickly, and why making their knowledge part of the migration, for example through data mapping, restores its value.
Jeffrey Pfeffer In The External Control of Organizations (1978), Pfeffer and Salancik argue that whoever controls a critical, scarce resource gains power over those who depend on it. After cutover, access to the system of record is that resource: licenses, training slots, and data scope. A sponsor who controls provisioning controls the target group's ability to work, which is why equal-access provisioning and an outside party who needs the group functional are the defenses.
Warning signs
After cutover, one unit is last in every training cohort and on the lowest license tier. Its historical data was only partly migrated. It had no input into configuration. Its access requests route through the sponsor's people. The story around the building is that the group could not adapt to the new system. Exits and early retirements cluster in that group, and its accounts move to the sponsor's team.
How to defend yourself
Read the rollout plan as a political document: who trains first, whose data is fully moved, who holds the access keys after cutover.
- Ask in writing, early, for equal-access provisioning, full data migration, and a training slot, each with a date.
- Log every access delay and its effect on a client or a deadline.
- Make your institutional knowledge part of the migration, for example by owning the data mapping for your accounts.
- Bring in someone outside the sponsor's reach who needs your group working: a client, a board member, or an internal champion.
A client or director who demands that you stay functional can force equal access faster than any internal appeal.
How a leader shuts it down
Review provisioning, training order, license tiers, and data scope as decisions with consequences for people, and approve them as such. Make equal access the default, and track adoption and exits by group after every migration. When one group's decline follows a rollout, look at how the rollout treated them before accepting that they could not keep up.