You Design for Your Ego

TL;DR:
The more you've invested in a design, the harder it is to see what's wrong with it. Critical feedback triggers identity defense, not design thinking. You're not protecting the work. You're protecting yourself.

The test came back bad. Users got confused. The flow that felt obvious to you made no sense to them. Three places where people gave up and stopped. The facilitator presented the findings and you sat there listening, and somewhere in your chest something tightened.

And then you said: “But I think they just didn’t understand the concept.” Or maybe: “That user was kind of an outlier.” Or you said nothing and just decided the test wasn’t very well run.

You didn’t lie. You believed it. That’s the problem.

There’s a version of being a designer where you hold your work at arm’s length, take feedback at face value, and update when the evidence tells you to. Most designers think that’s the version they are. The research says otherwise. The more hours you’ve put in, the more you’ve shaped and named and defended a design in meetings, the worse you get at seeing what’s actually wrong with it. Not because you’re lazy. Because your brain won’t let you.

The brain rewrites the story

Leon Festinger described cognitive dissonance in 1957 as the discomfort that comes from holding two conflicting ideas at the same time. You think your design is good. Evidence shows it isn’t. Both can’t be true. That gap creates psychological pressure, and the brain resolves it the only way it knows how: by changing how you interpret one of them.

It almost never changes the belief you’re most invested in. It changes the threatening evidence. The user who struggled wasn’t a representative user. The test conditions weren’t quite right. The finding is true in a narrow sense but doesn’t reflect real usage. These aren’t conscious choices. The brain runs this process without asking you, below any level you’d notice, and hands you back a version of events that feels like honest evaluation but isn’t.

Carol Tavris and Elliot Aronson mapped this in Mistakes Were Made (But Not by Me): the deeper someone has invested in a belief, the more elaborate and convincing the justifications become when someone challenges it. They write about it across politics and personal relationships and medicine. It holds in design too. The greater the investment, the more sophisticated the defense. You’re not just protecting a file. You’re protecting a version of yourself.

Dan Kahan’s research on what he calls identity-protective cognition, the way people defend beliefs tied to their sense of self, adds something uncomfortable to this. His studies found that the smarter and more experienced someone is, the better they get at constructing justifications for their existing positions. Intelligence doesn’t neutralize this bias. It arms it. A senior designer with years of pattern recognition doesn’t just feel attached to their work. They can build a persuasive, detailed argument for why the critical feedback is wrong. They’ve done it enough times. They’re good at it now.

Nielsen Norman Group put it straight in their research on confirmation bias in UX work:

The more invested you are in your assumptions about the design or the users, the stronger the confirmation bias.

Nielsen Norman Group

This isn’t a warning for beginners. It’s a warning for the people who’ve been doing this long enough to be dangerous.

The investment came first. The blindness followed. That’s the sequence.

Forty-eight days

In 2010, Microsoft launched the Kin, a social phone aimed at teenagers. The company had spent about $1 billion and two years building it. The phones were stylish. The team had a clear vision of what the product was and who it was for.

The Kin launched on May 14, 2010. Microsoft pulled it on June 30, 2010. Forty-eight days.

The product launched without an app store. Without a calendar. The social feed updated on a fifteen-minute delay. On a phone marketed to teenagers who lived on social media. These weren’t unknowable problems. They were visible to anyone who didn’t already have a very specific idea of what the product needed to be.

The team had one. The people building the Kin had shaped and refined and defended that idea across two years and hundreds of decisions and a billion dollars. By the time anyone might have said “but does this actually work for the person buying it,” the investment was so deep that the question would have sounded like a personal attack. Not on purpose. Just the way brains work when they’ve gone that far in.

The Kin wasn’t the product of stupid people or careless people. It was the product of invested people. And investment, past a certain point, becomes the thing that stops you from seeing what you’re building.

The question you least want to ask

There’s a technique called the pre-mortem. Before you ship, you imagine the thing has already failed. Not might fail. Has failed. Then you work backwards. Why did it fail? What went wrong?

This works because it changes the frame. Instead of asking “is there anything wrong with this?” (which your brain will answer with “no” if you’re invested enough), it asks “what was wrong with this?” Past tense, assumed outcome. You’re no longer defending. You’re explaining.

The most useful version is to do it when you feel least like you need it. Not when the project is rocky and doubts are already surfacing. When the design is finished and you’re proud of it and everyone in the room seems aligned. That’s when the blindness is at its worst. That’s the moment to sit down and write the three things that would most threaten this design’s success in the real world. Not vague worries. Specific. Named. Real. The exercise works because it gives your brain permission to be honest without it feeling like an attack on the work you just built.

If you can’t name them, someone else will. Users will. The market will. The difference is just timing, and whether you find out while there’s still time to do something about it.

The second version is simpler. Before any major design decision ships, ask one person to argue against it. Not to be constructive. To be hard. Their job is to find what’s wrong. Give them the brief, give them ten minutes, and tell them they’re doing you a favour. If they can’t find anything, the problem isn’t that the design is perfect. The problem is that nobody wants to be the one who says it.

The best designers aren’t the ones who never fall in love with their work. They’re the ones who learned to break up with it.