Chapter 4

Your Mind Lies to You

How fluency and confirmation bias distort your judgment

Your Mind Lies to You illustration

TL;DR: Your brain can make bad work feel solid in several ways at once. Processing fluency makes it feel right, confirmation bias protects it, and the illusion of depth makes you think you understand it. That is how nonsense ships with confidence.

You’ve been working on this design for weeks. You know every screen. You know why each decision was made. So when you open the file, it looks right. Clean. Clear. Obvious. But that feeling is not proof that the design is good. It is a sign that your brain has gotten used to it. Those are not the same thing, and designers confuse them all the time.

The brain uses ease as a shortcut for quality. When something feels familiar, it also feels right. Researchers Rolf Reber, Norbert Schwarz, and Piotr Winkielman studied this and put it simply:

The more fluently perceivers can process an object, the more positive their aesthetic response.

That does not mean the design is better. It means it is easier for you to process because you have seen it so many times. And that is the trap: the longer you stare at your own work, the harder it becomes to judge it clearly.

The brain doesn’t stop at one lie

Processing fluency is the first problem. But it is not the only one.

Once you commit to a design direction, confirmation bias starts to shape what you see. This is not a personal flaw. It is how the brain works after it has chosen a position. Raymond Nickerson, who reviewed years of research on confirmation bias, said it is “sufficiently strong and pervasive” that it may explain why people can disagree so strongly while each believes they are thinking clearly.

In design, it looks like this: a user struggles with your navigation in a usability test. Instead of seeing that as evidence the design may be weak, your brain looks for another explanation. Maybe the user did not understand the concept. Maybe the task was unclear. You are not lying to yourself on purpose. Your brain is doing what confirmation bias does. It is defending the idea, not testing it.

Then there is a third problem, and it is a strange one. Leonid Rozenblit and Frank Keil at Yale asked people to explain how ordinary things work, like zippers, toilets, and bicycles. People felt sure they understood them. But when they had to explain them step by step, their confidence dropped fast. Many people who thought they understood a zipper could not actually explain how it worked. Rozenblit and Keil described this as the illusion that you understand something better than you really do.

What happened to Google Wave

In May 2009, Google announced Google Wave at its developer conference and the crowd went wild. The product combined email, chat, live document editing, and social updates in one place. Technically, it was impressive. The team behind it, led by Lars and Jens Rasmussen, had also built Google Maps. They knew what they were doing.

But when Google opened Wave to 100,000 users in September 2009, the response was very different. Regular users did not understand what it was for. The interface asked them to learn a completely new way of thinking, with no familiar starting point. People opened it, looked around, and gave up. Tech writers said using it felt exhausting. The problem was not just one confusing feature. The whole product was confusing at once.

Google stopped active development in August 2010, less than a year after the public launch. The problem was not the engineering. The problem was that the team understood the product too well. They had spent so long building it that they could no longer see how confusing it was to everyone else.

Their own familiarity made the product feel obvious. Their shared belief in the idea made it easier to dismiss signs that users were lost. And they believed they understood the user problem, when really they mostly understood the technical solution. Those are not the same thing.

The question you’re probably not asking

There is one question worth asking, and most people avoid it: when did feedback actually make you change your mind? Not tweak the details. Really change direction. If you can name one example from the last month, good. If not, that does not mean nothing happened. It may mean confirmation bias was in charge. Your brain was gathering support for what you already believed, not testing whether you were wrong.

You do not fix that by collecting more feedback. You fix it by paying attention to what you do with feedback that challenges your decision.

Confidence is just familiarity in a better coat

Your instincts are not neutral. They’ve been shaped by exposure, by weeks of looking at the same designs. What feels like confidence is often just familiarity pretending to be judgment. From the inside, they feel the same. That is the problem.

You have been looking at it too long to judge it clearly. That is not a feeling. It is just what happens.

Wouter de Bres

I am a psychologist turned product designer & founder. With 20yrs experience designing digital products, I am convinced that when you understand psychology, it makes your designs more effective and your products more human. Let's Connect

If this book saved you from one bad design decision

References