Case: the migration two teams refuse to adopt

A senior engineer with no title built the shared payments client everyone approved. Six months later, two squads still run their old copies.

One squad lead resists openly. The other agrees in every meeting and schedules nothing. Security updates for the old SDK end in eight weeks.

You will now hear the full case, one page, 5 minutes. Listen for what has already been tried.

Case: the laws in tension

• Influence: she has no title over anyone, and being right has not moved them
• Buy-In: they approved the library; did they ever accept the engineer?
• Timing: a right move at the wrong moment still fails

Three laws, and they do not point to the same move.

One migration, both tracks

Whether you lead a team of reports or lead technical direction without reports, this case is yours.

The IC track runs on exactly this: scope grows through influence, not headcount.

An EM's failed reorg fails the same way as this migration: people heard the idea, but they did not accept the person.