Spot anchoring and confirmation bias in negotiations, estimates and reviews.
Before you read on, think of a piece of work you will need to estimate soon and write down how long you think it will take. Do it now, before anyone else's figure reaches you. The reason to do it in that order is a bias called anchoring, and it affects estimates, negotiations and reviews more than most people expect.
Anchoring is the tendency for a number heard early to pull later estimates towards it, even when it has nothing to do with the question. Amos Tversky and Daniel Kahneman demonstrated it in an experiment Kahneman describes in his book Thinking, Fast and Slow. People spun a wheel of fortune that was rigged to stop on either a low or a high number, then estimated an unrelated quantity. Those who saw the high number gave clearly higher estimates than those who saw the low number. The wheel number was obviously meaningless, and it still moved their answers.
Workplace anchors are rarely that random, but they are often just as unhelpful. A previous vendor's price, a colleague's guess, last year's budget and the first salary figure mentioned in a negotiation all work this way. A client's hoped-for timeline tells you what the client wants. It does not tell you how long the work takes.
Take Mei, whose team is estimating how long it will take to migrate a client's records to a new system. Before anyone else speaks, the account director says the client hopes for six weeks and asks what the team thinks. The engineers say seven weeks, eight weeks, maybe seven if the data is clean. The final plan says eight weeks. Three months later the project is still running. Nobody in the room thought the six weeks had influenced them, and each person believed they had estimated from their own experience. That is typical of an anchored room: the first number spoken set the range everyone else worked within.
The wheel experiment shows that an anchor pulls your judgement even when you can see the number is meaningless. Deciding to ignore it is not enough, because anchoring happens in the fast, automatic thinking described in Lesson 5.1, Fast and slow thinking. What helps is changing the order, so you form your own view before you see anyone else's.
The defence is to write your own number privately before any anchor reaches you. In a meeting, everyone writes an estimate on paper or in a private message, and all the estimates are revealed together. Software teams do this with planning poker, where everyone shows an estimate card at the same time so no one hears another estimate first.
At the next estimating session, Mei asks everyone to write a number before the director speaks. The estimates range from eight to fourteen weeks. A spread that wide shows genuine uncertainty about the job, and it gives the team something to discuss. The conversation turns to why the high estimates are high. One engineer has seen this client's data before and knows it is messy, which nobody would have heard if the six weeks had been said first.
The same order applies in negotiations. Decide your own figure from your own research before you hear theirs, and write it down. For a pay discussion, research first using MOM's Occupational Wage Tables, MyCareersFuture listings and recruiter salary guides, so the first number in your mind is one you chose. Keep in mind that it works both ways: when you name a figure first, you set the anchor for the other side.
Confirmation bias is looking for, noticing and remembering evidence that supports what you already believe, while overlooking evidence against it. From the inside it rarely feels like bias. It feels like being right.
Mei has also decided that Ravi, a new member of her team, is a weak performer after a rocky first month. Over the next quarter she notices every missed deadline and every typo. His good work on a difficult client call barely registers, or she puts it down to luck. By review time she has a full page of evidence against him, all of it real and all of it pointing one way. Her attention did the filtering. People caught by confirmation bias usually never set out to be unfair, and Mei did not either.
The bias also shapes how you search. Someone who thinks a stock, product or policy is good searches for its strengths and clicks the articles that agree. You can also end up asking questions whose answers can only confirm your view, such as "Did the new process help?" A more useful question is "What would we see if it had not helped?"
The defence is to make the opposite case your job. Before a decision or review, ask yourself what evidence would change your mind, write it down, then look for that evidence as seriously as you looked for the evidence that supports you.
Mei asks herself what she would expect to see if Ravi were a solid performer having a hard start. She writes down three things: good client feedback, improving turnaround over the quarter, and strong work on tasks suited to his experience. She checks and finds two of the three. Her review changes from "not meeting expectations" to a more specific conversation about the tasks where he struggles and why.
Teams can build the same habit into how they work:
Give someone the job of making the case against the leading option. Rotate that role so it is not always the same person. Ask for evidence that the plan will not work, as well as evidence that it will. When a report supports what everyone hoped, apply the checks from Module 3 with extra care, because that is when nobody wants to look hard.
None of these habits ask you to abandon your view. They ask you to hold it in a way that lets new evidence reach it.
The easiest place to start is your next estimate at work. Write your own figure down before you hear anyone else's, note what would make you change it, and bring that estimate to the activity below.
Write your number privately before your next work estimate, then compare it with the group's and note whether yours moved. Then, for one review or negotiation you are preparing, write down what evidence would change your view and look for it.
Junxiong-WFG Organisation is an authorised representative of AIA Financial Advisers Private Limited (Reg. No. 201715016G).