You Ruin Your Own Designs

TL;DR: Impostor syndrome does not stay in your head. It leaks into the work. You play safe, shrink the idea, and the user gets the timid version instead of the bold one.

You had a design direction that felt right, the kind that got you excited, until doubt crept in. Then you found a reason it would not work. A technical constraint. A stakeholder concern. A story you told yourself about the user. So you moved toward something safer, more boring, something no one would push back on. You called it pragmatism.

It wasn’t. It was fear.

Most designers know the feeling, but few name it for what it is. You sit in a room with people who seem to know exactly what they are doing, and you wonder when someone will notice that you are mostly guessing. You got the job, shipped products, earned praise, but none of it quite feels like proof that you belong. Each new project feels like the one that might finally expose you as a fraud. So you protect yourself. You make the choice that is hardest to criticize instead of the one most likely to be right. And you call that being professional.

That pattern has a name, and it costs more than you think.

Why you play it safe

In 1978, psychologists Pauline Clance and Suzanne Imes described what they called the impostor phenomenon. They observed that even high-achieving people with clear signs of success could still believe they were not actually competent. Instead, they explained their accomplishments as luck, charm, timing, or someone else’s mistake. At the core was a simple belief: they had fooled anyone who thought otherwise.

An internal experience of intellectual phonies

Clance & Imes

Since then the research has stretched well beyond its original sample. A systematic review of 62 studies covering more than 14,000 people found prevalence rates ranging from 9 to 82 percent, depending on how it was measured, across genders, age groups, and professions (Bravata et al., 2020). It gets worse during transitions. New job, new team, new kind of work. The more you care, the harder it hits.

What Clance and Imes named as a feeling, Albert Bandura showed us as a behavior. Bandura spent decades studying your belief in your ability to do it. His finding was not subtle. When that belief is low, people don’t just feel worse. They do less. They avoid challenging tasks before they even start. They give up earlier. They read setbacks as confirmation of what they already suspected about themselves, rather than as normal friction on the way to something (Bandura, 1977). When you do not trust your own ability, it does not stay in your head. It shows up in your work. In the choices you make at your desk, in meetings, and in the moment you choose between the idea you believe in and the one that feels safer.

That is where the real problem starts. Deep down, you think your past success was mostly luck. So when a hard decision shows up, you stop trusting your own judgment. You wait. You add more options instead of choosing. You do another round of research instead of picking a direction. You call it being thorough. But often it is just avoiding a decision you do not feel ready to own.

And the work is what suffers.

What it looks like in the room

Jason Fried wrote about this in Rework. The early 37signals team, building what would become Basecamp, made conservative call after conservative call out of fear, fear of being exposed as amateurs playing at a level above their ability. They played safe. They hedged. When they finally shipped Basecamp despite those doubts, the market responded. The product worked. The fear had been costing them the whole time, not in how they felt, but in what they built.

When designers do not trust their own judgment, they stop making clear calls. They add more, explain more, and choose the safer option over the better one.

None of those choices feel like fear in the moment. They feel like professionalism.

One question before you make the call

Valerie Young, who spent decades studying the impostor phenomenon across professional fields, found that people experiencing it tend to set up situations where they can never fully trust their own success. When things go well, they attribute it to external factors. When a risky call works out, they assume they got lucky again. The evidence piles up and nothing changes. Failures feel like proof. Successes feel like luck.

You can’t fix that in one chapter.

But you can interrupt it before it kicks in. Before you kill a bold idea or reach for the safe option, ask yourself one question: am I making this call because the evidence says it won’t work, or because I’m afraid of being the one who pushed it? That’s it. Not workshops neccesary. One question. Evidence or fear. You will know the answer and you will not always like what you find.

Superfried, a Manchester design studio, made a similar point from the practitioner side: when you’re struggling with impostor feelings, the most useful thing is to look for concrete facts that can’t be argued away. Not reassurances. Facts. The client hired you. The team shipped the product. The thing you built worked. Those things happened. They are evidence. The fear that showed up alongside them is not.

The work is the record

The impostor feeling does not disappear just because things go well. The problem is not the evidence. The problem is how you read it. If you keep reading success as luck, the pattern stays. And over time, that shapes every design decision you make.

The people using your design do not care how confident you felt. They care whether what you made works.