Plenty of Blame to Go Around
by Rick Brenner
You may have heard the phrase "plenty of blame to go around," or maybe you've even used it yourself. Although it sometimes does bring an end to immediate finger pointing, it also validates blame as a general approach. Here's how to end the blaming by looking ahead.
s 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
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 more on blaming and blaming organizations, see "Organizational Coping Patterns."
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!
Your comments are welcome
Would you like to see your comments posted here?
Send 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.
Related articles
More articles on
Organizational Change:
Look Before You Leap
- When we execute complex organizational change, we sometimes create disasters. It's ironic that even in companies that test their products thoroughly, we rarely test organizational changes before we "roll them out." We need systematic methods for discovering problems before we execute change efforts. One approach that works well is the simulation.
Don't Rebuild the Chrysler Building
- When we undertake change, we're usually surprised at the effort and cost required. Much of this effort and cost is necessary because of the nature of the processes we're changing. What can we do differently to make change easier in the future?
Conventional Foolishness
- Every specialization has a set of beliefs, often called "conventional wisdom." When these beliefs are so obvious that they're unquestioned and even unnoticed, there's an opportunity to leap ahead of the pack — by questioning the conventional wisdom.
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?
Outsourcing Each Other's Kids
- Outsourcing is now so widespread that it has achieved status as a full-fledged management fad. But many outsourcing decisions lack the justification that a full financial model provides. Here are some of the factors that such a model should include.
See also Organizational Change for more related articles.
Coaching services
I offer email and telephone coaching at both corporate and individual rates.
Contact me for details at
rbrenner@ChacoCanyon.com
or (617) 491-6289, or toll-free in the continental US at (866) 378-5470.
Get the e-book!
Past issues of
Point Lookout are available in five e-books:
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 words in your inbox in one hour. License any article from this Web site.
More info
Public seminars
- Person-to-Person Communication for Project Managers
- When
we talk, listen, send or read emails, read or write memos, or when we leave or listen to voice mail messages, we're communicating person-to-person. And whenever we communicate person-to-person, we risk being misunderstood, offending others, feeling hurt, and being confused. There are so many ways for things to go wrong that we could never learn how to fix all the problems. A more effective approach avoids problems altogether, or at least minimizes their occurrence. In this very interactive program you'll learn a model of inter-personal communications that can help you stay out of the ditch. In those moments of intense involvement, when we're most likely to slip, you'll have a new tool to use to keep things constructive. Read more about this program. Here are some upcoming dates for this program:
Download to
your calendarDes Moines, IA: February 16, Breakfast Meeting, Central Iowa Chapter of The Project Management Institute. Register now.
Download to
your calendarDes Moines, IA: February 16, Lunch Meeting, Central Iowa Chapter of The Project Management Institute. Register now.
- Houston, Texas: May 8, Monthly Meeting, Houston Chapter of the Project Management Institute.
- Houston, Texas: May 9, Monthly Meeting, Houston Chapter of the Project Management Institute.
- The Race to the South Pole: The Power of Agile Development
- On 14
December 1911, four men led by Roald Amundsen reached the South Pole. Thirty-five days later, Robert F. Scott and four others followed. Amundsen had won the race to the pole. Amundsen's party returned to base on 26 January 1912. Scott's party perished. As historical drama, why this happened is interesting enough. Lessons abound. Among the more important lessons are those that demonstrate the power of the agile approach to project management and product development. Read more about this program. Here's an upcoming date for this program:
- Human-Centered Risk Management
- Most
of us can assess technological risks, but risks related to human behavior tend to resist our best efforts. This session provides a framework for evaluating risks related to the behavior of individuals, teams, organizations and people generally. Human-centered risk differs from technological or market risk, because objective evaluation requires acknowledging personal and organizational limitations and failures. Since some of those limitations and failures might apply to the people assessing the risks, or to their superiors, there's a tendency to deny them or to explain them away. Our approach examines capability, organization, context, risk mitigation, and workplace politics. It has tools for guiding the assessment and management of human-centered risk, and we show how to extend these tools to suit your situation. You'll learn how to identify sources of risk in human behavior; recognize systemic and individual barriers to acknowledging risk; assess the effects of organizational turbulence; determine the risk associated with inappropriate internal risk transfer; estimate the effects of team dysfunction, toxic conflict and turnover; and measure the impact of workplace politics. Read more about this program. Here's an upcoming date for this program:
- The Race to the South Pole: Ten Lessons for Project Managers
- On 14
December 1911, four men led by Roald Amundsen reached the South Pole. Thirty-five days later, Robert F. Scott and four others followed. Amundsen had won the race to the pole. Amundsen's party returned to base on 26 January 1912. Scott's party perished. As historical drama, why this happened is interesting enough, but to project managers, the story is fascinating. Lessons abound. Read more about this program. Here's an upcoming date for this program:
- Project Management in Fluid Environments
- Most
people now work in environments that can best be characterized as fluid, because they're subject to continual change. We never know what's coming next. In such environments, managing — teams, projects, groups, departments, or the enterprise — often entails moving from surprise to surprise while somehow staying almost on track. It's a nerve-wracking existence. This program provides numerous tools that help project managers who work in fluid environments. Read more about this program. Here's an upcoming date for this program:
- The Politics of Meetings for People Who Hate Politics
- There
's a lot more to running an effective meeting than having the right room, the right equipment, and the right people. With meetings, the whole really is more than the sum of its parts. How the parts interact with each other and with external elements is as important as the parts themselves. And those interactions are the essence of politics for meetings. This program explores techniques for leading meetings that are based on understanding political interactions, and using that knowledge effectively to meet organizational goals. Read more about this program. Here's an upcoming date for this program: