← Mental Models
MachineOrganizationServes P in the equation

The Institutional Immune System

“Every org has antibodies that attack change. Transformation fails on the immune response, not the technology.”

The Challenge

New systems rarely fail technically. They fail because they threaten someone's status, control, or headcount, and the organization's antibodies quietly attack. The better the technology, the stronger the immune response it can provoke.

The Framework
01

Change reads as a threat

Any change to how work flows reroutes power. The people whose status depended on the old flow resist, often unconsciously.

02

Antibodies are quiet

Resistance shows up as "let us pilot first," endless edge cases, and tools that mysteriously go unused, not open refusal.

03

Treat the host, not the tech

Give people a new, higher-status role before removing the old one. Transformation is an immunology problem.

A Worked Example

A transformation lead automates a manager's weekly status report. Technically flawless; quietly sabotaged, the report was how that manager demonstrated control and justified headcount. The antibodies won. The fix was not better software; it was giving them a new, higher-status role before removing the old one.

Where it fails · the limit

Not all resistance is an immune response, sometimes the change is genuinely wrong and the "antibodies" are the people who see it first. Mistaking valid objection for politics is how you ship the wrong thing confidently.

Run it on your org

Whose status or headcount does this change threaten, and what new role have you offered them?

TL;DR
  • Transformation fails on people, not technology.
  • Resistance is usually quiet, not loud.
  • Offer a higher-status role before removing the old one.
For you this week · no budget required
01For your next change, name the three people it threatens.
02Design one "promotion" the change makes possible for a likely resister.