Open the spreadsheet. Enter the options down column A. Weight each criterion across the top row. Multiply, sum, compare. The highest score wins. Olusegun Adeyemi, a project manager at a mid-sized logistics firm, had done this dozens of times. He trusted the process. What the spreadsheet could not record was that he had already decided which vendor he wanted before opening the file, and had quietly adjusted the weights until the numbers confirmed it.
The mind didn't malfunction. It ran exactly the program it was built to run, in a situation that program wasn't designed for. Heuristics — the fast, pattern-matching shortcuts the brain uses to conserve energy — are genuinely useful most of the time. Bias is what happens when those shortcuts fire in contexts that need slower reasoning. The error is in the heuristic's application, not in the person using it. That distinction matters enormously, because shame sends you inward, and the fix is always outward.
Daniel Kahneman and Amos Tversky spent decades mapping exactly where these misfires happen. Work collected in the research underlying Thinking, Fast and Slow. One documented pattern: people anchor on an early number or preference, then interpret all subsequent information as evidence for it. Olusegun's spreadsheet is a near-perfect illustration. The tool looked rigorous. The bias dressed up in its clothes. Knowing that this specific error has a name and a mechanism is not an academic exercise. It is the first step toward designing around it.
Consider the moment you sit down to evaluate something you already have a gut feeling about. A hire, a plan, a purchase you have half-made in your head. The feeling arrived first, maybe in the first thirty seconds. Everything since has been a kind of prosecution, gathering evidence for the feeling rather than testing it. One structural move changes this: before you open the analysis, write one sentence predicting your conclusion and the reason you expect to reach it. The prediction goes in a drawer. You do the work. Then you compare. The gap between what you expected and what the process produced is not a verdict on you. It is data.
Your judgment is not broken. The conditions around it are just undesigned. Most people spend years feeling vaguely bad about decisions that a single constraint, written in advance, would have changed.