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 welcome
Would you like to see your comments posted here? rbrendPtoGuFOkTSMQOzxner@ChacEgGqaylUnkmwIkkwoCanyon.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.
This article in its entirety was written by a human being. No machine intelligence was involved in any way.
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 Emotions at Work:
- When Naming Hurts
- One of our great strengths as Humans is our ability to name things. Naming empowers us by helping us
think about and communicate complex ideas. But naming has a dark side, too. We use naming to oversimplify,
to denigrate, to disempower, and even to dehumanize. When we abuse this tool, we hurt our companies,
our colleagues, and ourselves.
- Responding to Threats: I
- Threats are one form of communication common to many organizational cultures, especially as pressure
mounts. Understanding the varieties of threats can be helpful in determining a response that fits for you.
- Creating Trust
- What can you do when you discover that the environment at work is permeated with distrust? Your position
in the organization does affect your choices, but here are some suggestions that might be helpful to anyone.
- Coercion by Presupposition
- Coercion, physical or psychological, has no place in the workplace. Yet we see it and experience it
frequently. We can end the use of presupposition as a tool of coercion, but only if we take personal
responsibility for ending it.
- 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?
See also Emotions at Work, Personal, Team, and Organizational Effectiveness and Cognitive Biases at Work for more related articles.
Forthcoming issues of Point Lookout
- Coming May 1: Antipatterns for Time-Constrained Communication: 2
- Recognizing just a few patterns that can lead to miscommunication can reduce the incidence of miscommunications. Here's Part 2 of a collection of antipatterns that arise in communication under time pressure, emphasizing those that depend on content. Available here and by RSS on May 1.
- And on May 8: Antipatterns for Time-Constrained Communication: 3
- Recognizing just a few patterns that can lead to miscommunication can reduce the incidence of problems. Here is Part 3 of a collection of antipatterns that arise in technical communication under time pressure, emphasizing past experiences of participants. Available here and by RSS on May 8.
Coaching services
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrendPtoGuFOkTSMQOzxner@ChacEgGqaylUnkmwIkkwoCanyon.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
Follow Rick
Recommend this issue to a friend
Send an email message to a friend
rbrendPtoGuFOkTSMQOzxner@ChacEgGqaylUnkmwIkkwoCanyon.comSend a message to Rick
A Tip A Day feed
Point Lookout weekly feed