The Institutional Immune System
“Every org has antibodies that attack change. When a rebuild dies, the immune response killed it and the technology takes the blame.”
New systems rarely fail on the technology. They fail because they threaten someone’s status, or the headcount and control that came with it, and the organization’s antibodies quietly go to work. The better the technology, the stronger the immune response it can provoke.
Change reads as a threat
Any change to how work flows reroutes power. The people whose status depended on the old flow resist, often without knowing they are doing it.
Antibodies are quiet
Resistance shows up as “let’s pilot first”, as endless edge cases, and as tools that mysteriously go unused. Open refusal is rare.
Treat the host, not the tech
Give people a new, higher-status role before you remove the old one. Changing an org is an immunology problem.
The person leading the rebuild automates a manager’s weekly status report. Technically flawless. Quietly sabotaged, because the report was how that manager showed control and justified headcount. The antibodies won. The fix had nothing to do with software. It was a more senior role for that manager, and it came before the report went away.
Not all resistance is an immune response. Sometimes the change is genuinely wrong and the antibodies are the people who saw it first. Mistaking a valid objection for politics is how you ship the wrong thing with confidence.
Whose status or headcount does this change threaten, and what new role have you offered them?
- Change fails on people. The software is usually fine.
- Resistance is quiet. Listen for the pilot that never ends.
- New role first, old one removed after.