Design for Your Ego

TL;DR: Cognitive dissonance makes criticism feel personal. Once your identity gets tied up in the work, feedback stops being useful input and starts feeling like something you need to defend against.

The feedback came in and it landed harder than it should have. The screen was confusing. People got stuck. The evidence was not subtle. And still some part of you wanted to defend it, because by then the work was no longer just work. It had started to feel like proof of whether you were good at your job.

I know that move because I have done it.

The work stops feeling separate from you

Leon Festinger described cognitive dissonance as the strain that shows up when two things you want to keep both turn out to conflict. In design the clash is ugly and familiar. You think the work is good. Then the test says otherwise. At that point, something has to give.

Most of the time the first thing your brain protects is not the evidence but you. Carol Tavris and Elliot Aronson wrote about how people justify bad choices once identity gets tied up in them. That is the part that matters here. When your design starts standing in for your judgment, hard feedback stops feeling like useful signal and starts feeling like exposure.

Dan Kahan adds something worse. Smart people are often better at protecting the idea they are attached to because they can generate better reasons for keeping it intact. Experience does not save you there. Sometimes it just makes the defense cleaner.

That is what makes this one hard to catch in yourself. Bad defense does not always sound defensive. It can sound thoughtful. It can sound nuanced. “The participant was rushed.” “The prompt was unclear.” “They would understand it after one use.” Sometimes those things are true. But once the work has become personal, your brain reaches for those lines faster than it reaches for the simpler possibility that the design missed.

Kin had too much of Microsoft in it

In 2010, Microsoft launched the Kin , a social phone built for teenagers. It had been in development for two years and reportedly cost around $1 billion. Then it launched without an app store, without a calendar, and with a social feed that refreshed every fifteen minutes on a phone aimed at people living on social platforms all day.

Microsoft killed it forty-eight days later.

The reason this example works is not that the flaws were subtle or hard to find. They were visible. But by that point the product had too much commitment, identity, and internal belief wrapped around it. Asking whether it really worked for the buyer no longer felt like a neutral product question. It felt like attacking a thing people had already spent years defending.

That is usually how it looks in product work too. It is not one big lie or some dramatic refusal to see the obvious. It is more like a slow change in tone. A problem gets raised and the room starts talking about how to protect the work from the problem instead of how to learn from it.

Why this feels reasonable from the inside

This is what matters here. Confirmation bias is about how you filter evidence. This problem starts earlier and feels more personal. It is the moment feedback turns into threat because the work got fused with your sense of self.

Nielsen Norman Group has a line that fits the overlap between the two well: “The more invested you are in your assumptions about the design or the users, the stronger the confirmation bias.” I want the first half of that line here. Invested. That is the condition. Once the attachment is there, clean thinking gets harder fast.

I have seen designers protect bad work because cutting it felt too close to admitting they were not as smart as they wanted to be. I have felt that in my own chest in reviews. The threat feels personal before the defense starts sounding intellectual.

What to do before the ego takes over

Run a pre-mortem before the work ships. Don’t ask, “what might go wrong?” Say the thing already failed, then ask why. It sounds like a small wording change, but it matters because it takes you out of defense mode. You’re not trying to protect a live idea anymore. You’re looking back at something that already fell over, which makes it easier to be honest about where it was weak.

If you want the shorter version, get one person to attack the work properly for ten minutes. No softening it. No “overall this is strong.” Just tell them to look for the cracks and say where it breaks.

Then write down the first defensive thought that popped into your head when they said it. Not the cleaner version you came up with a few minutes later. The first one. That’s usually where the ego is hiding.

Good designers get attached too. Everybody does. The difference is they build in little moments where the work can stop being an extension of them and go back to being a thing on the table. That’s not a personality trait. You have to practice it, because if the feedback feels like a threat, your ego is already in the room.