Project Management

3 Common Biases - And Smartcuts for Mitigating Them

From the Voices on Project Management Blog
by , , , , , , , , , , , , , , , , , ,
Voices on Project Management offers insights, tips, advice and personal stories from project managers in different regions and industries. The goal is to get you thinking, and spark a discussion. So, if you read something that you agree with--or even disagree with--leave a comment.

About this Blog

RSS

View Posts By:

Cameron McGaughy
Lynda Bourne
Kevin Korterud
Conrado Morlan
Peter Tarhanidis
Mario Trentim
Jen Skrabak
David Wakeman
Wanda Curlee
Christian Bisson
Ramiro Rodrigues
Soma Bhattacharya
Emily Luijbregts
Sree Rao
Yasmina Khelifi
Marat Oyvetsky
Lenka Pincot
Jorge Martin Valdes Garciatorres
cyndee miller

Past Contributors:

Rex Holmlin
Vivek Prakash
Dan Goldfischer
Linda Agyapong
Jim De Piante
Siti Hajar Abdul Hamid
Bernadine Douglas
Michael Hatfield
Deanna Landers
Kelley Hunsberger
Taralyn Frasqueri-Molina
Alfonso Bucero Torres
Marian Haus
Shobhna Raghupathy
Peter Taylor
Joanna Newman
Saira Karim
Jess Tayel
Lung-Hung Chou
Rebecca Braglio
Roberto Toledo
Geoff Mattie

Recent Posts

Are Organization Charts Still Useful?

3 Ways to Challenge the Agile Norm

What’s In Your Return-To-Work Contract?

How To Foster Effective Group Decision Making

3 Tips for Avoiding the Single Point of Failure


Categories: Leadership


I’ve been trying to learn more about good decision-making and recently read Daniel Kahneman’s famous Thinking Fast and Slow. It’s very surprising to see the number of fallacies and biases that cloud our decision-making, with some impacting us more than others. Here are three of the most common fallacies that we encounter in project and program management, along with a few “smartcuts” (smarter way of doing things) to mitigate them. 

1. Planning fallacy: the tendency to underestimate the time, costs and risks of future actions, while overestimating the benefits of the same actions
Smartcuts:
•    Conduct a pre-mortem: Think of what could go wrong, work backwards and plan for those scenarios.
•    Use chunking: Break down the project into as small tasks as you and the team can.
•    Try consensus-based estimation: This method uses conversation and convergence to reduce individual cognitive biases—but it’s time-consuming. To strike a balance, I’d recommend using it only for complex features or projects in which there’s not much leeway in delivery time.
•    Add buffer: This decision depends on a lot of factors: type of project, whether there’s a need to have a definite deadline, complexity, dependencies etc. At a basic level, if you’ve been working with the team and have a history of how much the estimates are off by, you can plan to add that much buffer. If it’s a new team, and you don’t have any idea, look for similar projects use that data to gauge the buffer.

2. Sunk cost fallacy: an increased propensity to continue an endeavor once an investment in money, effort or time has been made 
Smartcuts:
•    Don’t just think about the time/money already spent. Instead, think of how much additional time/money is needed and if continuing the project will be a worthwhile investment.
•    Companies can help employees overcome loss aversion by putting greater values on gains and less penalties for losses. While this is something that happens at the enterprise level and might not be in our sphere of influence, you can influence it at a program and project level when framing wins and losses. For example, instead of saying, “We were over budget by 10 percent,” try framing it as, “We were within +10 percent of our initial estimates.”
•    Avoid perpetuating the stigma that stopping a project is a failure. Instead frame it as a lesson learned and incentivize people to make such decisions in the projects and programs they manage.
•    Consider opportunity costs. By sticking to the original plan, think of all the projects you’re giving up.

3. Status quo bias: sticking with the option you’re given even though the alternatives might be better
Smartcuts:
•    When you propose any change, be very clear and intentional about why you’re proposing it. Explain the problem statement you’re trying to solve and then detail the pros and cons of status quo versus the change.
•    Evaluate the opportunity cost of making the change versus sticking with the status quo.

While it’s not possible to eliminate all biases and fallacies, being cognizant of them and recognizing them will guide us in making better decisions.

What are some of the fallacies and biases you’ve held onto and how have you overcome them?


Here is a link to the unabridged version of this post.

Posted by Sree Rao on: March 12, 2021 01:59 PM | Permalink

Comments (3)

Please login or join to subscribe to this item
Dear Sree
Very interesting the theme that brought to our reflection and debate
Thanks for sharing
I consider the three of the most common fallacies that we encounter in project and program management to be very important to take into account

Good posting and thanks for sharing.

another fallacy: although the project is behind in time, it can be finished on time (instead of recognizing the delay and replanning). This puts lots of pressure on the project team and increase the posibility of suffering from health&safety&quality issues.

Please Login/Register to leave a comment.

ADVERTISEMENTS

"Military justice is to justice what military music is to music."

- Groucho Marx