Information Immunity

Definition

Because bug reports and test results can feel threatening, people build an "immune system" against unwanted information, activated whenever it breaks a personal "survival rule" — such as "I must always be perfect" or "I must always be on schedule." Drawing on family therapist Virginia Satir, Weinberg defines FEAR as Fantasy Experienced As Reality: the threat itself may be imagined, but the defense it triggers is real, and it can defeat even technically excellent testing.

In the Book

The chapter opens with a chorus of fear-driven reactions — a project manager afraid of missing schedule, a developer afraid a bug exposes incompetence, a marketing manager afraid of missing sales numbers, a tester afraid of reporting bad news late — each protecting a different survival rule. Weinberg then works through named defense mechanisms: repression (denying the unacceptable), illustrated by a tester who dismisses a colleague's crash demo with "users shouldn't do that" and admits he doesn't want more bugs found until existing ones are fixed, and by developers' stock line "I didn't change anything" (meaning nothing that should matter — except what changed); plus rationalization, projection, displacement, overcompensation, and compulsiveness as further named categories the book examines one by one.

Why It Matters

This explains why technically sound information routinely fails to change behavior: the blocker isn't a logic gap, it's a threatened survival rule, and no amount of additional data fixes that. Recognizing which survival rule is under threat — job security, competence, control, likability — tells you what kind of intervention might actually land, in any domain where feedback (performance reviews, safety incidents, financial audits) meets a defended self-image.