Following unwanted outcomes, we often commission "lessons learned" exercises to investigate the conditions that brought about the unwanted outcomes. We want to learn how to prevent recurrences of those outcomes or any other unwanted outcomes that might flow from similar conditions. In too many organizations, these exercises yield useless or misleading results.
What we seek is Truth: the reasons why the unwanted outcome occurred. But these investigations rely on reports from people who participated in or witnessed events leading to the outcome. To find the truth we must interpret the reports we receive, and those reports can contain a variety of misleading elements. Here's a short catalog of those elements.
- Confusions and mistakes
- Relying on memory and impressions, witnesses and participants sometimes get it wrong. They get confused about the order of events, or who did what. They confuse what they actually witnessed with what they heard about second-hand.
- An excuse is a fact, condition, or situation that provides protection for someone from blame for the unwanted outcome. Excuses are those offerings that, if true, most people would accept as relieving someone of being regarded as having caused or contributed to causing the unwanted outcome.
- An allegation is the opposite of an excuse — it's a fact, condition, or situation that, if true, affixes to someone blame for the unwanted outcome. While excuses tend to be offered by the person excused, allegations tend to be offered by someone other than the one blamed.
- Reports that omit relevant information can also mislead investigators. Omissions can be intentional, but they need not be. They can result from numerous factors including faulty memory, emotional trauma, and poor technique by the investigator.
- Concealment To find the truth we must
interpret reports that can
contain a variety of
misleading elementstranscends intentional omission. It includes deliberate actions to deflect the investigator from the information concealed, such as destruction or obfuscation of information, or propagating false accounts of events. It can also include actions that make the information difficult to retrieve. For example, important witnesses might be relocated, terminated, or transferred.
- Fabrications are fictions intended to mislead the investigator. When well crafted and when delivered by someone who is unaware that they are fabrications, they are difficult to detect, because the deliverer isn't actually lying. Detecting them often requires tracing them to their source.
In determining who acted (or did not act) so as to contribute to the genesis of the unwanted outcome, there's a high risk that some witnesses and participants might experience the investigation as a search for someone to blame. The investigators themselves might adopt this belief.
In organizational cultures that tend to affix blame, investigations are unlikely to uncover much Truth, because people fear blame. Over time, people who don't master these tools for misleading investigations tend to be discredited, ejected from the organization, or allocated to less central roles. Organizations that want to improve outcomes would do well to eliminate blame from their cultures. Next in this series Top Next Issue
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!
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 more on blaming and blaming organizations, see "Organizational Coping Patterns" and "Plenty of Blame to Go Around," Point Lookout for August 27, 2003.
Your comments are welcomeWould you like to see your comments posted here? rbrenZLkFdSHmlHvCaSsuner@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.
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:
- Workplace Taboos and Change
- In the workplace, some things can't be discussed — they are taboo. When we're aware of taboos,
we can choose when to obey them, and when to be more flexible. When we're unaware of them, they can
limit our ability to change.
- Comfortable Ignorance
- When we suddenly realize that what we've believed is wrong, or that what we've been doing won't work,
our fear and discomfort can cause us to persevere in our illusions. If we can get better at accepting
reality and dealing with it, we can make faster progress toward real achievement.
- Good Change, Bad Change: I
- Change is all around. Some changes are welcome and some not, but when we distinguish good change from
bad, we often get it wrong. Why?
- Patching Up the Cracks
- When things repeatedly "fall through the cracks," we're not doing the best we can. How can
we deal with the problem of repeatedly failing to do what we need to do? How can we patch up the cracks?
- 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.
Forthcoming issues of Point Lookout
- Coming November 30: Avoiding Speed Bumps: II
- Many of the difficulties we encounter when working together don't create long-term harm, but they do cause delays, confusion, and frustration. Here's Part II of a little catalog of tactics for avoiding speed bumps. Available here and by RSS on November 30.
- And on December 7: Reaching Agreements in Technological Contexts
- Reaching consensus in technological contexts presents special challenges. Problems can arise from interactions between the technological elements of the issue at hand, and the social dynamics of the group addressing that issue. Here are three examples. Available here and by RSS on December 7.
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenZLkFdSHmlHvCaSsuner@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