As Walter studied the next slide, Ellen's position became clear. The slide showed her root cause diagram with colored bubbles indicating which department had contributed which causes, and Geoff owned the largest share. If she was playing the blame game, Geoff was her target.
To prevent a battle between Ellen and Geoff, Walter offered, "I can see there's plenty of blame to go around, though I'm sure we could debate the allocations."
Walter's tactic might be successful. Distributing blame across the entire team is one way to prevent scapegoating. It also has an unintended consequence — it validates the idea of assigning blame.
Blame is toxic to organizations. When blame is in the air, punishment follows. To avoid punishment, we deflect blame from ourselves, or allocate it to others. We'll even take action to insulate ourselves from blame — we dodge involvement, withhold contributions, and make protective "CYA" statements.
The ensuing confusion prevents the organization and its people from learning from failures. Organizations and people who cannot learn from failures inevitably repeat them.
When blame is in the air,
punishment followsBlame-oriented cultures (B cultures) seek causes so they can punish, while Responsibility-oriented cultures (R cultures) seek causes so they can learn. To identify the culture of your organization, look at how people use language, how they acknowledge failure, how they understand failure, and how they look at the past.
- Using language
- In B cultures, people "take the blame," "get tagged," "get dinged," or "take the fall." Generally, B cultures have "post mortems" while R cultures have "retrospectives."
- Acknowledging failure
- B cultures have difficulty acknowledging failure, because acknowledgment precedes blame, and blame precedes punishment. Failing projects live on, long past the time when they should have been cancelled. R cultures acknowledge failures more easily, because they see them as opportunities to learn. Projects that should be cancelled (or restarted) are.
- Understanding failure
- To limit the resulting punishment, B cultures think failure is caused by the actions of a single person or organization. R cultures see failure as the result of a complex network of causes. They do this, in part, to maximize the resulting learning.
- Looking at the past
- In B cultures, retrospectives — if they are held at all — are starved of resources. When retrospectives do occur, they're tense, painful, dangerous affairs in which people withhold comments that could otherwise lead to real progress. R cultures invest in retrospectives, enlisting professional assistance to ensure the safety of participants. The organization and its people both benefit.
Consistent with B culture thinking, those who live in B cultures often blame the CEO or upper management for their problems. Although changing the culture from B to R does indeed require change at the top, everyone must change. Change can start anywhere. It can start with you. Top Next Issue
Is your organization embroiled in Change? Are you managing a change effort that faces rampant cynicism, passive non-cooperation, or maybe even outright revolt? Read 101 Tips for Managing Change to learn how to survive, how to plan and how to execute change efforts to inspire real, passionate support. Order Now!
For indicators that an organizational culture is a blaming culture, see "Top Ten Signs of a Blaming Culture," Point Lookout for February 16, 2005. The words blame and accountability are often used interchangeably, but they have very different meanings. See "Is It Blame or Is It Accountability?," Point Lookout for December 21, 2005, for a discussion of blame and accountability. For the effects of blame on the investigations of unwanted outcomes, see "Obstacles to Finding the Reasons Why," Point Lookout for April 4, 2012. For more on blaming and blaming organizations, see "Organizational Coping Patterns."
Your comments are welcomeWould you like to see your comments posted here? rbrenHoWzUJVeioCfozEIner@ChacbnsTPttsdDaRAswloCanyon.comSend me your comments by email, or by Web form.
About Point Lookout
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.
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.
More articles on Organizational Change:
- He's No Longer Here
- Sometimes we adopt inappropriate technologies, or we deploy unworkable processes, largely because of
the political power of their advocates, and despite widespread doubts about the wisdom of the moves.
Strangely, though, the decisions often stick long after the advocates move on. Why? And what can we
do about it?
- On Beginnings
- A new year has begun, and I'm contemplating beginnings. Beginnings can inspire, and sometimes lead to
letdown when our hopes or expectations aren't met. How can we handle beginnings more powerfully?
- The Restructuring-Fear Cycle: I
- When enterprises restructure, reorganize, downsize, outsource, spin off, relocate, lay off, or make
other adjustments, they usually focus on financial health. Often ignored is the fear these changes create
in the minds of employees. Sadly, that fear can lead to the need for further restructuring.
- Deciding to Change: Choosing
- When organizations decide to change what they do, the change sometimes requires that they change how
they make decisions, too. That part of the change is sometimes overlooked, in part, because it affects
most the people who make decisions. What can we do about this?
- The Expectation-Disruption Connection
- In technology-dependent organizations, we usually invest in infrastructure as a means of providing new
capability. But mitigating the risk of disruption is a more powerful justification for infrastructure
investment, if we understand the Expectation-Disruption Connection.
See also Organizational Change for more related articles.
Forthcoming issues of Point Lookout
- Coming June 14: Pseudo-Collaborations
- Most workplace collaborations produce results of value. But some collaborations — pseudo-collaborations — are inherently incapable of producing value, due to performance management systems, or lack of authority, or lack of access to information. Available here and by RSS on June 14.
- And on June 21: Asking Burning Questions
- When we suddenly realize that an important question needs answering, directly asking that question in a meeting might not be an effective way to focus the attention of the group. There are risks. Fortunately, there are also ways to manage those risks. Available here and by RSS on June 21.
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenHoWzUJVeioCfozEIner@ChacbnsTPttsdDaRAswloCanyon.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:
- Get 2001-2 in Geese Don't Land on Twigs (PDF, )
- Get 2003-4 in Why Dogs Wag (PDF, )
- Get 2005-6 in Loopy Things We Do (PDF, )
- Get 2007-8 in Things We Believe That Maybe Aren't So True (PDF, )
- Get 2009-10 in The Questions Not Asked (PDF, )
- Get all of the first twelve years (2001-2012) in The Collected Issues of Point Lookout (PDF, )
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
- Your stuff is brilliant! Thank you!
- You and Scott Adams both secretly work here, right?
- I really enjoy my weekly newsletters. I appreciate the quick read.
- A sort of Dr. Phil for Management!
- …extremely accurate, inspiring and applicable to day-to-day … invaluable.