People often believe that an outcome was predictable or even inevitable, after they know what that outcome was. When we do this, sometimes we're right, but often our sense of predictability or inevitability is exaggerated. This perception is so common that psychologists have given it a name: hindsight bias. Because of hindsight bias, we tend to see causal connections between antecedent conditions and outcomes, even when those supposedly causal connections are false. We tend not to recall conditions that would introduce uncertainty in the outcome, or which would tend to produce dramatically different outcomes. And we do recall elements that didn't exist if they support explanations that predict what actually happened.
For example, in a written evaluation of a subordinate's performance, a supervisor might observe, "George's impulsiveness created toxic conflict, not only involving George, but also between other team members." Toxic conflict might well have occurred, but was George's impulsiveness really the cause? Or was it an effect? A more useful comment would have provided evidence for the supposed causal connection, and it would have addressed alternative explanations for the toxic conflict that did occur.
Here are three suggestions for managing the risk of hindsight bias in the workplace.
- Awareness is essential
- Ignorance of hindsight bias allows it to thrive. Educate all those responsible for interpreting past events. Give them the tools they need to detect hindsight bias in themselves and their own thinking.
- Accept that hindsight bias is a risk, and mitigate the risk
- Although awareness and sensitivity can reduce the incidence of hindsight bias, total elimination is almost certainly impossible. Cooperative action is required. For example, in the performance appraisal process, supervisor and subordinate can be encouraged to discuss the possible presence of hindsight bias in the appraisal, and then come to agreement that they have dealt with those possibilities. Introducing this idea into the appraisal process is an example of mitigating hindsight bias risk.
- Identify processes at risk of hindsight bias
- Some processes are especially vulnerable to hindsight bias. The two mentioned here — performanceIgnorance of hindsight bias
allows it to thrive appraisal and project retrospectives — are merely examples. Strategic decisions, including decisions such as reorganizations, acquisitions, relocations, downsizing, outsourcing, and more, are often subject to evaluation, and therefore hindsight bias risk. An inventory of all processes for hindsight bias vulnerability is a necessary element of any program to address the effects of hindsight bias.
After identifying those processes most susceptible to hindsight bias risk, mitigation is the next step. Mitigation approaches must suit the process, but effective measures include checks and balances along the lines of the approach indicated above for risk management in the performance appraisal process. Multiple viewpoints and healthy, vigorous dialog are essential. Top Next Issue
Are your projects always (or almost always) late and over budget? Are your project teams plagued by turnover, burnout, and high defect rates? Turn your culture around. Read 52 Tips for Leaders of Project-Oriented Organizations, filled with tips and techniques for organizational leaders. Order Now!
Your comments are welcomeWould you like to see your comments posted here? rbrenMyreSsaWRbrnILwener@ChacCNHZBddPvNcaUzHboCanyon.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 Emotions at Work:
- If You Weren't So Wrong So Often, I'd Agree with You
- Diversity of perspectives is one of the great strengths of teams. Ideas contend and through contending
they improve each other. In this process, criticism of ideas sometimes gets personal. How can we critique
ideas safely, without hurting each other, while keeping focused on the work?
- A Guide for the Humor-Impaired
- Humor can lift our spirits and defuse tense situations. If you're already skilled in humor, and you
want advice from an expert, I can't help you. But if you're humor-impaired and you just want to know
the basics, I probably can't help you either. Or maybe I can...
- The Restructuring-Fear Cycle: II
- When enterprises restructure, reorganize, downsize, outsource, lay off, or make other organizational
adjustments, they usually focus on financial health. Here's Part II of an exploration of how the fear
induced by these changes can lead to the need for further restructuring.
- Why Scope Expands: I
- Scope creep is depressingly familiar. Its anti-partner, spontaneous and stealthy scope contraction,
has no accepted name, and is rarely seen. Why?
- Preventing Toxic Conflict: II
- Establishing norms for respectful behavior is perhaps the most effective way to reduce the incidence
of toxic conflict at work. When we all understand and subscribe to a particular way of treating each
other, we can all help prevent trouble.
Forthcoming issues of Point Lookout
- Coming May 31: Unresponsive Suppliers: III
- When suppliers have a customer orientation, we can usually depend on them. But government suppliers are a special case. Available here and by RSS on May 31.
- And on June 7: The Knowledge One-Upmanship Game
- The Knowledge One-Upmanship Game is a pattern of group behavior in the form of a contest to determine which player knows the most arcane fact. It can seem like innocent fun, but it can disrupt a team's ability to collaborate. Available here and by RSS on June 7.
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenRfBTxWzxYhPGTzNNner@ChacZrzvOJADsvJaizRDoCanyon.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:
- Get 2001-2 in Geese Don't Land on Twigs (PDF, USD 11.95)
- Get 2003-4 in Why Dogs Wag (PDF, USD 11.95)
- Get 2005-6 in Loopy Things We Do (PDF, USD 11.95)
- Get 2007-8 in Things We Believe That Maybe Aren't So True (PDF, USD 11.95)
- Get 2009-10 in The Questions Not Asked (PDF, USD 11.95)
- Get all of the first twelve years (2001-2012) in The Collected Issues of Point Lookout (PDF, USD 28.99)
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
- Creating High Performance Virtual Teams
- Many people experience virtual teams as awkward, slow, and sometimes
frustrating. Even when most team members hail from the same nation or culture, and even when they all
speak the same language, geographic dispersion or the presence of employees from multiple enterprises
is often enough to exclude all possibility of high performance. The problem is that we lead, manage,
and support virtual teams in ways that are too much like the way we lead, manage, and support co-located
teams. In this program, Rick Brenner shows you how to change your approach to leading, managing, and
supporting virtual teams to achieve high performance using Simons' Four Spans model of high performance.
Read more about this program. Here's an upcoming date
for this program:
- Baci Grill, 134 Berlin
Road, Berlin, CT 06416: September 19,
Monthly Meeting, Southern New England Chapter of the Project Management Institute. Register now.
- Baci Grill, 134 Berlin Road, Berlin, CT 06416: September 19, Monthly Meeting, Southern New England Chapter of the Project Management Institute. Register now.
- 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 organizational leaders, business
analysts, project sponsors, and project managers, the story is fascinating. Lessons abound. Read
more about this program. Here's an upcoming date for this program:
- CTCPA, 716 Brook Street,
Rocky Hill, CT 06067: September 20,
Full-day Workshop, Southern New England Chapter of the Project Management Institute. Register now.
- CTCPA, 716 Brook Street, Rocky Hill, CT 06067: September 20, Full-day Workshop, Southern New England Chapter of the Project Management Institute. Register now.