Cognitive Bias

Rhiannon Gallagher • August 25, 2023

Notice and activate the team

There are a bunch of cognitive bias lists floating around.

I’m not sure what we’re supposed to do with them.

Recognize a bias in ourselves? Maybe.

Recognize a bias in others? Maybe.

But there are hundreds of cognitive biases. We’re never going to recognize them all. And we certainly aren’t going to eradicate them. We use them, as humans with big brains in a complicated world, to cope with (waves hands) everything.

We are, we are led by, we work with, and we must respond to people making decisions and taking actions based on those biases. Sometimes they have terrible consequences, and we need to prevent those consequences.

But we'll never recognize every bias, no matter how many lists we read.

What if, instead of memorizing lists of biases, we learn to recognize the situations where they are most likely to appear?

If we recognize when are we most vulnerable to these shorter and less accurate thought patterns, we can counteract them . . . even if we don’t know all their names.

Buster Benson has organized biases into 4 useful categories. I love his work so much that if you’re ever on a call with me, you’ll see the poster of his bias map on the wall.

You don’t need to memorize all the kinds of bias, you just need to recognize and calm the situations where they are likely to show up.

  1. When there is too much information. Our brains try to create Cliff’s Notes, shorthand to allow it to store information. These biases are about simplification and narrative. Confirmation Bias lives here, because it’s easier to cope with things that match what we already know. A branch of an existing belief is smaller than a whole new thing.
  2. When there isn’t enough meaning. At the other end of the spectrum are situations where we don’t have enough information, so our brains try to fill in the gaps, to make sense of the fraction of the pattern we know about. Murphy’s Law lives here, because it’s easier to assume a pattern than deal with the lack of one.
  3. When we need to act fast. Our brains sometimes need us to act confidently, even without enough information. Dunning-Kruger Effect lives here, because sometimes people overestimate their abilities in order to move into action.
  4. When we need to simplify memories. Our brains can’t possibly remember everything. So it reduces things, simplifies them. Primacy and Recency Effect live here, because it's easier to remember the first thing and the last thing instead of remembering everything.

Take a minute when things are feeling frantic or overwhelming or too much for your team. Analyze. Which kind of ‘too much’ is it? Which kinds of shortcuts are your brain or the brains of your team likely to make in this moment? The more diverse the team (neurologically, culturally, experientially), the more likely they are to bring different sets of biases and perspectives to the situation, and that is a strength. Use your team to overcome the moment.

What needs to be slowed down?

  • If it’s the volume of information: have people summarize for each other and notice the differences between their summaries
  • If it’s the meaning-making: bring people back to the basic facts, make sure they aren’t leaping to patterns that aren’t there
  • If it’s needed fast action: open up the discussion of actions to take - see how different people view the options before you act
  • If it’s memory overwhelm: document collaboratively, let everyone contribute to the agreed-on memory.

Humans create biases. But we also create teams, and our teams can be powerful counterbalances to our biases, if we let them.


By Rhiannon Gallagher August 12, 2023
Because it's respectful
By Rhiannon Gallagher July 18, 2023
A tribute to walkers
By Rhiannon Gallagher July 14, 2023
AKA Missing my mom
By Rhiannon Gallagher June 16, 2023
Murray wasn't happy. He was sure this new initiative would fail, just like all the others. 'I've been here for 31 years,' he'd say. 'They almost always fail.' But Murray was a planner, coordinating schedules and materials for teams across the entire organization. He talked to almost everyone, and he talked a lot. We had to get him on our side. Digital transformations succeed or fail for many reasons, big and small. Most of those reasons are people-related. But sometimes the reason is a person. One person. Or just a few people. People who, if you looked at them on a hierarchical chart, wouldn’t seem to have a bunch of power. But WOW, they have a lot of influence. We call these folks social nodes, and few actions will support your transformation success more than finding them, knowing them, honoring them, and getting them on the side of change. On factory floors, sometimes, they are social nodes because their role is so far-reaching. Planners, tooling designers, and in-process inspectors who talk to everyone and know everything are often social nodes. Union officers may be social nodes as well. But they could also be social nodes because they are simply people who connect well. The person who organized the chili cookoff or the person who always seems to be chatting in the breakroom. The person who reads all the company newsletters and emails and knows what’s happening outside the day-to-day. Social nodes often have strong opinions. They are loyal on multiple levels, but they’ve often been around for a few ‘transformations’ and can rattle off what went wrong in every one of them. Once we know who they are, we can build communication to support them. In various projects, I’ve given them special briefings, created a place in the project updates that comes from them, given them access to early information they could disseminate, or checked in with them regularly to learn how implementations are going. For Murray, we created a special column in the project newsletter called 'Murray's Musings' and recorded and transcribed a little interview every month. We asked about the problems with the old processes and checked in on new ones. We asked about his history with the company. We let him know that everyone, including the C-Level folks, was getting the newsletter and reading his words. Murray is retired now, but his stories are recorded as company history. And the initiative succeeded, partly because we recognized Murray as a social node and got him on board.