liveBook · Manning

Scapegoating fallacy

As explained in Collaborative Software Design: How to facilitate domain modeling decisions

The scapegoating fallacy is a reasoning and communication error in which responsibility for a problem is shifted onto other people.

The scapegoating fallacy shifts responsibility for a problem onto other people. In a tense group discussion, a participant may defend their own contribution by claiming others are disengaged, turning a specific conflict into blame against the wider group. section 8.3.2

A climate report can surface the pattern, but it cannot resolve it alone. Reopen dialogue by making space, listening actively, acknowledging emotions, reflecting back what was heard, and asking unbiased questions rather than arguing over blame. section 8.3.2

When blame is redirected toward others:

  • Ask a neutral question such as, “Why do you think the group is not engaging?” section 8.3.2
  • Notice defensive reactions, “Yeah, buts,” denial, attacks, sarcasm, topic changes, silence, or isolation. section 8.3.2
  • Reflect feelings and demonstrate empathy before seeking shared understanding. section 8.3.2

How Collaborative Software Design: How to facilitate domain modeling decisions covers it

How deep it goes
Defines the fallacy through a group-conflict scenario and pairs it with active-listening responses, without formal reasoning analysis.
Examples
Illustrates a defensive participant blaming disengaged developers after receiving a climate report.
What you can do after
Practice/perform unbiased questioning, active listening, and empathy to reopen dialogue after blame shifting.
How it connects
Connects scapegoating to climate reports, active listening, empathy, resistance, bias, and conflict resolution.

This explainer was generated by Manning's knowledge graph from the text of Collaborative Software Design: How to facilitate domain modeling decisions. The section links point to the parts of the book it draws on.