Your Mind Lies to You

The feeling of knowing

You have been working on this design for three weeks. You know every screen. You know why every decision got made. You open the file in the morning and it looks right to you. Clean, sensible, obvious. That feeling is not a sign the design is good. It is a sign your brain has learned to process it without effort. Those are not the same thing, and confusing them is one of the most consistent mistakes designers make.

The brain uses processing ease as a proxy for quality. When something feels familiar, the cognitive system flags it as safe, correct, pleasant. Researchers Rolf Reber, Norbert Schwarz, and Piotr Winkielman spent years studying this and put it plainly: “The more fluently perceivers can process an object, the more positive their aesthetic response.” Not the better the object is. The easier it is to process. You have been looking at your own work long enough that your brain processes it on autopilot, which means you have lost the ability to evaluate it. Every hour you spend inside your own file makes you a worse judge of it.

Three ways your brain covers its tracks

Processing fluency is the first problem. But it does not work alone.

Once you have committed to a design direction, a second mechanism kicks in. Confirmation bias is not a character flaw. It is what the brain does by default once it has taken a position. Raymond Nickerson, who spent a career reviewing the research on this, concluded that it appears to be “sufficiently strong and pervasive” that it may account for a significant share of disputes and misunderstandings among people who are each convinced they are thinking clearly. In design terms: you run a usability test and a user struggles with your navigation. Your brain does not log that as “evidence against the current approach.” It logs it as “that user didn’t understand the concept” or “the task we gave them was off.” You are not being dishonest. You are doing exactly what a brain in confirmation mode does. It builds a case, not a test.

The third layer is the strangest one. Leonid Rozenblit and Frank Keil at Yale ran a series of studies asking people to explain how everyday things work: zippers, toilets, bicycles. People felt confident they understood them. Then the researchers asked them to write out step-by-step explanations. Confidence collapsed. People who were certain they understood how a zipper worked could not explain the mechanism when pressed. Rozenblit and Keil called this the illusion of explanatory depth: people feel they understand complex things with far greater precision and depth than they actually do. For designers, this illusion is everywhere. You believe you understand your users, your own product logic, the reasoning behind the decisions you shipped three months ago. Some of that understanding is real. More of it is the feeling of understanding, which the brain generates on demand and mistakes for the genuine article.

These three mechanisms run together. Fluency makes the design feel right. Confirmation bias filters out the signals that it isn’t. The illusion of depth prevents you from asking the questions that would reveal the gap. By the time a bad design makes it to shipping, the person who built it has typically convinced themselves, through no conscious deception, that it is solid.

What happened to Google Wave

In May 2009, Google announced Wave at its developer conference and the crowd went loud. The product merged email, instant messaging, real-time document editing, and social updates into one interface. It was technically extraordinary. The team that built it, led by Lars and Jens Rasmussen, had already built Google Maps. They were not amateurs. They understood what they had made with complete clarity, because they had made it.

Google opened Wave to 100,000 users in September 2009. The reaction from regular people was not what the team expected. Users could not figure out what Wave was for. The interface required a new mental model with no bridge to anything familiar. People opened it, looked around, and closed it. Tech writers described the experience of trying to learn Wave as exhausting. Not one thing was unclear. Everything was unclear, simultaneously, which is a different problem and a harder one to fix.

Google shut down active development in August 2010, less than a year after the public launch. The product was not bad engineering. It was a team that understood their own creation so completely, had spent so long inside it, that the gap between their comprehension and everyone else’s had become invisible to them. They could not see it. The fluency they had built up over years of development made the product feel obvious. The confirmation bias of a close-knit team with a shared vision filtered out every signal that ordinary people were lost. And the illusion of depth meant they believed they understood the user problem when they understood the engineering solution, which is a different thing entirely.

Wave is not an unusual story. It is a common one with an unusually well-documented ending.

The question you are not asking

The fix is not a new process. It is one question, asked honestly: when did a piece of user feedback change a decision you had already made? Not adjusted. Not refined at the edges. Changed. As in, you were going one way and the evidence turned you around.

If you can name one from the last month, good. If you are sitting there running through your memory and coming up empty, that is not bad luck or a quiet period. That is confirmation bias running the show. Your brain has been collecting evidence like a lawyer building a case, not a scientist testing a hypothesis. Everything that confirmed your direction got logged. Everything that did not got filtered, reframed, or quietly forgotten.

You do not fix this by collecting more feedback. You fix it by noticing what you do with feedback that says you are wrong.

The lie that feels like confidence

Your instincts are not neutral. They have been shaped by exposure, by investment, by weeks of staring at the same screens. What registers in your body as confidence is often just familiarity in a different coat. The two feel identical from the inside, which is precisely the problem.

You have been looking at this too long to see it. That is not a feeling. It is a cognitive fact.