We are shopping for an AI-powered project management tool and our leadership team is highly enthusiastic about a shiny new platform, but I am worried we are falling victim to confirmation bias. How do we apply Gleb Tsipursky's debiasing framework from The Blindspots Between Us to make a rational, objective software decision?

Question

Tyler Smith · Accepted Answer

When a leadership team gets excited about a shiny new AI tool, confirmation bias can easily blind everyone to the actual implementation costs and operational disruptions. To make a clean, rational decision, you must intentionally apply debiasing techniques from Gleb Tsipursky's framework. Start by taking a mindful pause during your evaluation meetings. When the team is in a state of high enthusiasm, delay making any final decisions for at least twenty to thirty minutes, or even postpone the vote to the following week. This allows the emotional excitement of the sales pitch to subside.

Next, force the team to apply probabilistic thinking rather than binary thinking. Instead of asking if this tool will solve our problems, ask the team to estimate the probability of different outcomes. Assign numerical percentages to questions such as:
- What is the probability that this software will integrate seamlessly with our existing CRM without custom coding?
- What is the probability that our team will actually adopt this tool within ninety days?

Once you force people to write down these probability estimates, you will quickly see where the team is being overly optimistic. Finally, run a pre-mortem exercise. Have the entire team imagine a scenario one year from now where this AI project management tool has completely failed, costing the company thousands of dollars. Ask everyone to write down the exact reasons why it failed. This simple exercise forces the team to look at the real operational risks and hidden assumptions they are currently ignoring.