Point Lookout: a free weekly publication of Chaco Canyon Consulting
Volume 5, Issue 7;   February 16, 2005: Top Ten Signs of a Blaming Culture

Top Ten Signs of a Blaming Culture

by

The quality of an organization's culture is the key to high performance. An organization with a blaming culture can't perform at a high level, because its people can't take reasonable risks. How can you tell whether you work in a blaming culture?
Beatty Pennsylvania broad ax

Beatty Pennsylvania broad ax. The broad axe (also called hewing axe or side axe) was the preferred tool for squaring timber or flattening the sides of logs. This was an essential step in preparing material for log buildings and timber framing for houses or barns. Later applications were for railroad ties and trestle bridges. The blade is as broad as a headsman's axe, though the handle is shorter. Photo courtesy U.S. Federal Highway Administration.

Lenore and Brad stepped through the revolving door and out into the sunshine of the plaza. Lenore had intended to wait until they got to the car, but nobody was around, so she took a risk. "Here's a tip, since you're new," she began. "It's just not safe to talk that way in these meetings."

Brad was listening. "I figured," he said. "Warner's reaching for his double-bladed axe was the tip-off."

"Uh-huh," Lenore agreed, "and you haven't even seen real trouble yet."

Lenore is educating Brad in survival strategies for the organization he has just joined. Hopefully, it isn't too late, but if he had known what to look for, he might have been a little more cautious. Here are ten attributes that suggest that your work culture might be a blaming culture.

Blame runs downhill in public, and uphill at the water-cooler
Lessons-learned panels rarely assign any responsibility to the owner of the panel or to any superiors. Blame almost always runs downhill. But water-cooler talk is the opposite — people grumble about management.
We rarely blame processes
In a blaming culture,
if something goes wrong,
it's always the fault
of some one person
Blame is rarely assigned to equipment, to a process, or to a situation. If something went wrong, human error is the cause.
We usually blame an individual
Rarely do we assign blame to a group or to several people. One is enough to satisfy the beast.
We kill messengers
Bearers of bad news are especially at risk, because we have a pattern of killing the messenger.
CYA is a standard business procedure
Since you can't be sure when you might need cover, it's only prudent to take every opportunity to cover your behind.
In response to catastrophe, we apply revised policy retroactively
When something bad happens, we convene a panel to write or revise policies and procedures. Then we apply them retroactively, and we blame violators.
We never revise policy in response to success
When something good happens, we feel that our policies and procedures are validated, so there's nothing to do.
We have designated winners
When good things happen, we usually assign credit to someone who's already an anointed winner. Heroes are rarely found in the trenches.
We blame people for breaking unwritten rules
Some policies and rules are written down only in obscure documents, if they're written at all. No matter. You can still be blamed for violating them.
People get sandbagged
Some people find out about a failure or policy violation for the very first time in their annual reviews. This is especially maddening when having withheld the information prevented the employee from righting a wrong, or from avoiding repetitions.

If you find yourself being blamed, remember that blame is almost always inappropriate. Blaming yourself then only adds to your trouble. Learning is a far better choice. Go to top Top  Next issue: Recovering Time: Part I  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 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" and "Plenty of Blame to Go Around," Point Lookout for August 27, 2003.

303 Secrets of Workplace PoliticsIs every other day a tense, anxious, angry misery as you watch people around you, who couldn't even think their way through a game of Jacks, win at workplace politics and steal the credit and glory for just about everyone's best work including yours? Read 303 Secrets of Workplace Politics, filled with tips and techniques for succeeding in workplace politics. Order Now!

Your comments are welcome

Would you like to see your comments posted here? rbrenrWzRrBnLiMtKFfXZner@ChacZKCoYfBIEyGeYgfsoCanyon.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.

Related articles

More articles on Workplace Politics:

Damage to the Interstate 10 Twin Bridge across Lake PontchartrainManaging Risk Revision
Prudent risk management begins by accepting the possibility that unpleasant events might actually happen. But when organizations try to achieve goals that are a bit out of reach, they're often tempted to stretch resources by revising or denying risks. Here's a tactic for managing risk revision.
Three Card Monte, Jaffa, IsraelFooling Ourselves
Humans have impressive abilities to convince themselves of things that are false. One explanation for this behavior is the theory of cognitive dissonance.
Ross Marshall and Don Pugh at the kickoff meeting for the Expeditionary Combat Support System (ECSS) at Tinker Air Force BaseDeep Trouble and Getting Deeper
Here's a catalog of actions people take when the projects they're leading are in deep trouble, and they're pretty sure there's no way out.
A schematic representation of a MOSFETBottlenecks: Part II
When some people take on so much work that they become "bottlenecks," they expose the organization to risks. Managing those risks is a first step to ending the bottlenecking pattern.
Langston Hughes, poet and leader of the Harlem RenaissanceThat Was a Yes-or-No Question: Part II
When, in the presence of others, someone asks you "a simple yes or no" question, beware. Chances are that you're confronting a trap. Here's Part II of a set of suggestions for dealing with the yes-or-no trap.

See also Workplace Politics, Conflict Management and Managing Your Boss for more related articles.

Forthcoming issues of Point Lookout

An outstanding example of the Utility Pole anti-patternComing June 1: Workplace Anti-Patterns
We find patterns of counter-effective behavior — anti-patterns — in every part of life, including the workplace. Why? What are their features? Available here and by RSS on June 1.
An outstanding example of the Utility Pole anti-patternAnd on June 8: The Utility Pole Anti-Pattern: Part I
Organizational processes can get so complicated that nobody actually knows how they work. If getting something done takes too long, the organization can't lead its markets, or even catch up to the leaders. Why does this happen? Available here and by RSS on June 8.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenZGTwiYoXuUzzsLOfner@ChacEtIabcZXADxNLQZSoCanyon.com or (617) 491-6289, 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 words in your inbox in one hour. License any article from this Web site. More info

Public seminars

The Race to the South Pole: The Power of Agile Development
On 14The Race to the Pole: An Application of Agile Development 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:

Managing in Fluid Environments
Most Managing in Fluid Environmentspeople now work in environments that can best be characterized as fluid, because they're subject to continual change. We never know whats 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 managers who work in fluid environments. Read more about this program. Here's an upcoming date for this program:

Sudoku Solutions, INK: A Simulation of a Project-Oriented Organization
In thCross-Functional Teams: How Organizations Actually Workis workshop, we simulate a company that solves Sudoku puzzles for its customers. Each puzzle is a project, solved by a project team led by a project manager. Team members hail from different parts of the organization, such as QA or the Department of Threes. Puzzles have different values, and the company must strive to meet revenue goals. The metaphor is uncanny. Lessons abound. Read more about this program. Here's an upcoming date for this program:

Follow Rick

Send email or subscribe to one of my newsletters Follow me at LinkedIn Follow me at Twitter, or share a tweet Follow me at Google+ or share a post Subscribe to RSS feeds Subscribe to RSS feeds
Please donate!The message of Point Lookout is unique. Help get the message out. Please donate to help keep Point Lookout available for free to everyone.
How to Spot a Troubled Project Before the Trouble StartsLearn how to spot troubled projects before they get out of control.
303 Secrets of Workplace PoliticsIs every other day a tense, anxious, angry misery as you watch people around you, who couldn't even think their way through a game of Jacks, win at workplace politics and steal the credit and glory for just about everyone's best work including yours? Read 303 Secrets of Workplace Politics!
303 Tips for Virtual and Global TeamsLearn how to make your virtual global team sing.
My free weekly email newsletter gives concrete tips and suggestions for dealing with the challenging but everyday situations we all face.
A Tip A DayA Tip a Day arrives by email, or by RSS Feed, each business day. It's 20 to 30 words at most, and gives you a new perspective on the hassles and rewards of work life. Most tips also contain links to related articles. Free!
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.