Point Lookout: a free weekly publication of Chaco Canyon Consulting
Volume 24, Issue 30;   July 24, 2024: When Retrospectives Turn into Blamefests: I

When Retrospectives Turn into Blamefests: I

by

An interactive group exercise known as a retrospective is widely recognized as a reliable tool for fostering organizational learning. But it can degenerate into blaming and retaliation if not conducted so as to manage the risk of toxic conflict.
The mushroom cloud of an atomic bomb test

The mushroom cloud of an atomic bomb test. The image serves as a metaphor for conflict that has gone out of control. This test was designated Hood, which was part of Operation Plumbob in 1957. According to The Nuclear Weapon Archive, Hood was the largest atmospheric test ever conducted at the Nevada Test Site. The image is from a FEMA (U.S. Federal Emergency Management Agency) publicity poster, courtesy WikiMedia.

I once suggested to a client that his team might benefit from conducting retrospectives from time to time, because retrospectives help teams identify what works and what doesn't. His response was: "We tried retrospectives and they just turn into blamefests, so let's find a better way." Thing is, there is no better way. [Kerth 2001] If retrospectives turn into blamefests, the thing to do is to fix them, not ban them.

To make retrospectives worthwhile for groups that have histories of retrospectives turning into blamefests, we must address the ongoing causes of the trouble by taking steps in three domains: before retrospectives, during retrospectives, and after retrospectives. In this Part I, I focus on measures to be taken during retrospectives. See Part II for suggested measures before conducting a retrospective, and Part III for suggested measures for the period after a retrospective.

About blaming and accountability

The word accountability is widely misused. To be accountable for an activity means to be responsible for and answerable for that activity. If something goes wrong, those accountable are expected to answer for their part in the goings-on, because we need their knowledge when we try to perfect our flawed systems. Blame is something more. To be blamed is to be accountable in a way deserving of censure, discipline, or other penalty, either explicit or tacit. [Brenner 2005]

A "blamefest" is an uncontrolled exchange of blaming assertions, counter-assertions, and other retaliations, offered without evidence or effect, other than harm to relationships between blamers and blamed.

Blame-control measures that we can deploy during retrospectives

These measures address the effects of organizational culture, past unpleasant experiences, participant behavior, and patterns of conducting the work itself.

A "blamefest" is an uncontrolled exchange
of blaming assertions, counter-assertions,
and other retaliations, offered without
evidence or effect, other than harm to
relationships between blamers and blamed
Enlist the assistance of an expert facilitator
Facilitating retrospectives is an art in its own right. The benefits of experience are clear, but an expert facilitator brings two advantages even more important to the exercise: neutrality and its close partner, fairness. These advantages are especially important for groups that have histories of retrospectives turning into blamefests.
Be explicit about expectations of behavior
Have the group develop and adopt a list of behavioral norms that apply for the duration of the retrospective. For example, "We treat each other with respect." Another: "We don't interrupt each other." (Expressing them in the present tense does tend to give them more force) Do this as the first order of business. And if trouble breaks out later on, review the list of norms for possible expansion or clarification.
Use anonymity-based tactics
In environments where blamefests are likely, deficits of psychological safety are also likely. [Brenner 2023] When people don't feel psychologically safe, they're often concerned that their comments might invite some form of retaliation. Making it possible for people to contribute to the retrospective anonymously can mitigate these fears.
Don't attribute actions (or inactions) to others by name
It's difficult to blame Person P for Event E without using P's name. You can try to blame P indirectly, but the blaming then becomes more obvious. It goes like this: "E happened, and someone told me P did it." Of course, that's a lie unless someone actually said that P did it. To avoid lying, the formulation can only be the equivalent of, "E happened." And that form is free of blame.

Last words

Certainly we can devise more guidelines that could reduce the likelihood of an outbreak of blaming in a retrospective. But these are a good start. Next time I'll suggest guidelines for measures we can take that occur before a coming retrospective.  When Retrospectives Turn into Blamefests: II Next issue in this series  Go to top Top  Next issue: When Retrospectives Turn into Blamefests: II  Next Issue

101 Tips for Managing Conflict Are you fed up with tense, explosive meetings? Are you or a colleague the target of a bully? Destructive conflict can ruin organizations. But if we believe that all conflict is destructive, and that we can somehow eliminate conflict, or that conflict is an enemy of productivity, then we're in conflict with Conflict itself. Read 101 Tips for Managing Conflict to learn how to make peace with conflict and make it an organizational asset. Order Now!

Footnotes

Comprehensive list of all citations from all editions of Point Lookout
[Kerth 2001]
Norman L. Kerth. Project Retrospectives: A Handbook for Team Reviews. New York: Dorset House, 2001. Order from Amazon.com. Back
[Brenner 2005]
Richard Brenner. "Is It Blame or Is It Accountability?," Point Lookout blog, December 21, 2005. Available here. Back
[Brenner 2023]
Richard Brenner. "Contrary Indicators of Psychological Safety: I," Point Lookout blog, December 13, 2023. Available here. Back

Your comments are welcome

Would you like to see your comments posted here? rbrenDJpmhgyaDTwBQXkhner@ChacmGoYuzfZpOvDQdRkoCanyon.comSend me your comments by email, or by Web form.

About Point Lookout

This article in its entirety was written by a 
          human being. No machine intelligence was involved in any way.Thank you for reading this article. I hope you enjoyed it and found it useful, and that you'll consider recommending it to a friend.

This article in its entirety was written by a human being. No machine intelligence was involved in any way.

Point Lookout is a free weekly email newsletter. Browse the archive of past issues. Subscribe for free.

Support Point Lookout by joining the Friends of Point Lookout, as an individual or as an organization.

Do you face a complex interpersonal situation? Send it in, anonymously if you like, and I'll give you my two cents.

Related articles

More articles on Conflict Management:

A schematic representation of the Milgram ExperimentToxic Conflict in Virtual Teams: Minimizing Authority
Toxic conflict in virtual teams is especially difficult to address, because we bring to it assumptions about causes and remedies that we've acquired in our experience in co-located teams. In this Part II of our exploration we examine how minimizing authority tends to convert ordinary creative conflict into a toxic form.
The business end of a spark plugCreating Toxic Conflict: II
Some supervisors seem to behave as if part of their job description is creating toxic conflict among their subordinates. It isn't really, of course, but here's a collection of methods bad managers use that make trouble.
BoredCompulsive Talkers at Work: Peers I
Our exploration of approaches for dealing with compulsive talkers now continues, with Part I of a set of suggestions for what to do when a peer interferes with your work by talking compulsively.
A flock of starlings acting as a swarmFear/Anxiety Bias: I
When people don't feel safe enough to report the true status of the work underway in an organization, managers receive an inaccurate impression of the state of the organization. To understand this dynamic, we must understand psychological safety.
The standard conception of delegationOn Delegating Accountability: II
What happens to accountability when we delegate responsibility for a mission? As a result of delegation, the distribution of responsibility, authority, and accountability can assume any of eight possible forms. Here's a catalog.

See also Conflict Management and Conflict Management for more related articles.

Forthcoming issues of Point Lookout

Grissom, White, and Chaffee in front of the launch pad containing their AS-204 space vehicleComing May 14: Working with the Overconfident
A cognitive bias known as the Overconfidence Effect causes us to overestimate the reliability of our judgments. Decisions we make based on those judgments are therefore suspect. But there are steps we can take to make our confidence levels more realistic, and thus make our decisions more reliable. Available here and by RSS on May 14.
A Strangler Fig in AustraliaAnd on May 21: Mismanaging Project Managers
Most organizations hold project managers accountable for project performance. But they don't grant those project managers control of needed resources. Nor do they hold project sponsors or other senior managers accountable for the consequences of their actions when they interfere with project work. Here's a catalog of behaviors worth looking at. Available here and by RSS on May 21.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenDJpmhgyaDTwBQXkhner@ChacmGoYuzfZpOvDQdRkoCanyon.com or (650) 787-6475, or toll-free in the continental US at (866) 378-5470.

Get the ebook!

Past issues of Point Lookout are available in six ebooks:

Reprinting this article

Are you a writer, editor or publisher on deadline? Are you looking for an article that will get people talking and get compliments flying your way? You can have 500-1000 words in your inbox in one hour. License any article from this Web site. More info

Follow Rick

Send email or subscribe to one of my newsletters Follow me at LinkedIn Follow me at Bluesky, or share a post Subscribe to RSS feeds Subscribe to RSS feeds
The message of Point Lookout is unique. Help get the message out. Please donate to help keep Point Lookout available for free to everyone.
Technical Debt for Policymakers BlogMy blog, Technical Debt for Policymakers, offers resources, insights, and conversations of interest to policymakers who are concerned with managing technical debt within their organizations. Get the millstone of technical debt off the neck of your organization!
Go For It: Sometimes It's Easier If You RunBad boss, long commute, troubling ethical questions, hateful colleague? Learn what we can do when we love the work but not the job.
303 Tips for Virtual and Global TeamsLearn how to make your virtual global team sing.
101 Tips for Managing ChangeAre you managing a change effort that faces rampant cynicism, passive non-cooperation, or maybe even outright revolt?
101 Tips for Effective MeetingsLearn how to make meetings more productive — and more rare.
Exchange your "personal trade secrets" — the tips, tricks and techniques that make you an ace — with other aces, anonymously. Visit the Library of Personal Trade Secrets.
If your teams don't yet consistently achieve state-of-the-art teamwork, check out this catalog. Help is just a few clicks/taps away!
Ebooks, booklets and tip books on project management, conflict, writing email, effective meetings and more.