The Subjective Nature of Design: Why Good Work Gets Rejected

If you have worked in design for any length of time, you will know the moment. You present something you are genuinely proud of. The layout is clear, the hierarchy works, it is accessible, and it does exactly what the brief asked. Then someone in the room says they just don't like it. No reason, or a reason that seems to have nothing to do with the work. The colour reminds them of something. It feels too busy, or not busy enough. Could it be more like a website they saw last week?

It is tempting to file this under "people have no taste" and move on. But that explanation is both unkind and unhelpful. A more useful one is that design really is partly subjective, and partly not, and most of the friction in design work comes from people mixing the two up. Including us.

Everyone is looking at a slightly different design

Nobody sees a design with fresh eyes. Every person brings a lifetime of associations with them: the brands they trust, the products that let them down, the colours that carry meaning in their culture, the interfaces they learned on. A typeface that feels confident and modern to one person can feel cold and corporate to another. A shade of green can read as fresh, or as the logo of a company someone once had a terrible experience with.

Familiarity plays a large part too. Psychologists have long studied the mere-exposure effect: people tend to rate things more favourably simply because they have seen them before ^[1]. In design reviews this shows up constantly. The existing website feels "right" partly because everyone has looked at it every day for years. A new direction, however well reasoned, starts at a disadvantage because it is unfamiliar.

Then there is context. The same person can react differently to the same design depending on their mood, how rushed the meeting is, what they saw right before it, or whether they are viewing it on a large monitor or a phone in a taxi. None of this makes their reaction fake. It makes it personal, which is a different thing from being wrong.

Taste is real. It just isn't the whole story

Here is where the "design is subjective" argument usually goes too far. Taste genuinely varies, but a lot of what makes a design work can be checked, tested and measured. Treating everything as opinion is just as unhelpful as treating everything as fact.

A practical way to think about it is to separate the parts of a design that depend on preference from the parts that can be evaluated against something outside anyone's personal taste:

Then there is the part that genuinely is a matter of judgement: the mood of a brand, the choice between two equally usable layouts, whether a palette feels warm or restrained. These choices still matter, and they can still be argued for. They just cannot be proven in the same way.

Most design arguments get stuck because the conversation slides between these two territories without anyone noticing. A designer defends a contrast decision as if it were a matter of style. A stakeholder rejects an accessible layout because of a feeling. Both people are talking past each other.

Why good work gets rejected anyway

Even when a design is objectively sound, there are good reasons it might not get approved, and very few of them are about the work itself.

• The feedback has no criteria. If nobody agreed what success looks like before the design was made, every reviewer quietly uses their own definition. The loudest definition usually wins.
• Seniority stands in for evidence. Some teams call this the HiPPO problem: the Highest Paid Person's Opinion. It is not malicious. It is simply easier for a group to defer than to debate.
• Risk feels bigger than reward. A bold change is visible if it fails. Keeping things as they are rarely gets anyone in trouble, so unfamiliar work faces a higher bar.
• People arrive late. Someone who missed the research, the brief and the early rounds sees only the final design, without the reasoning behind it.
• Committees average things out. When everyone's preferences must be accommodated, distinctive decisions get sanded down until the work offends nobody and persuades nobody.

It is worth saying plainly: stakeholder approval and a good user experience are not the same thing. A design can be signed off enthusiastically and still confuse every customer who uses it. A design can also be rejected and still be the better option for the people it was meant to serve. Approval is a business process. Usefulness is measured somewhere else.

How to tell which kind of feedback you are getting

When feedback lands, the first job is not to respond. It is to work out what kind of feedback it is, because each kind needs a different answer. One useful way to sort it:

Much feedback arrives disguised. "Make the logo bigger" might be a preference, or it might be a genuine problem: the brand is not recognisable on mobile. "It feels cluttered" might be taste, or it might be a real hierarchy issue. Your job is to find out which, before you change anything.

Responding without defending or caving

There are two easy responses to subjective feedback, and both are traps. The first is to defend every pixel, which makes you look precious and teaches people to stop sharing honest reactions. The second is to change everything you are asked to change, which turns you into a pair of hands and quietly erodes the quality of the work.

The useful middle ground starts with questions rather than answers:

• "What are you reacting to, specifically?" This moves the conversation from a feeling to something you can look at together.
• "Who do you think will struggle with this, and how?" This connects a preference to a user, or reveals that there isn't one.
• "Which of our goals does this get in the way of?" This brings the agreed success criteria back into the room.
• "If we changed it, what would better look like?" Sometimes the answer reveals a real problem. Sometimes it reveals that nobody knows.

Asking these questions is not a tactic for winning. Sometimes the answers show that the feedback is right and you missed something. That is a good outcome. The point is to make decisions for reasons both sides can see.

And when a preference is the only thing at stake, and the change does no harm to usability or the business goal, it is often fine to simply make it. Not every hill is worth defending. Save your energy for the decisions that affect the people who will use the work.

Presenting design decisions with evidence

The best time to deal with subjective feedback is before it arrives. A design presented with its reasoning gets a very different reception from one presented as a finished picture.

1. Start with the goal, not the design. Remind everyone what the work is meant to achieve and for whom, before anyone sees a screen.
2. Show the decisions, not just the result. Explain why the main action sits where it does, why the navigation is structured this way, why this contrast level was chosen.
3. Show what you considered and rejected. It demonstrates rigour and answers "what if we tried..." before it is asked.
4. Bring evidence where you have it. Usability test observations, accessibility checks, analytics from the current site and research findings carry more weight than conviction.
5. Separate the testable from the taste. Be clear which decisions are grounded in evidence and which are judgement calls. People trust the second kind more when you are honest about it.

If a disagreement cannot be settled in the room, suggest a way to settle it outside the room. Put both versions in front of a handful of real users. Run a simple test. Agree to measure after launch. Evidence ends arguments that opinions can only prolong.

When the criticism gets into your head

None of the above makes rejection painless. Design is personal work. You put judgement and care into it, and when it is dismissed, it is hard not to hear "you are not good at this" instead of "this did not land".

If repeated criticism has you quietly convinced that everyone else knows what they are doing and you are about to be found out, you are in large company. The imposter phenomenon was described by psychologists Pauline Clance and Suzanne Imes in 1978 ^[4], and it has been widely discussed in creative and professional fields since. It tends to affect capable people, which is part of what makes it so persistent.

A few things genuinely help:

• Separate the work from the worker. A rejected design is a decision about one piece of work in one context, not a verdict on your ability.
• Keep a record of your reasoning. When you write down why you made each decision, criticism becomes something to examine rather than something to absorb.
• Track outcomes, not just approvals. Notice when your work made something clearer, faster or easier for real people. That evidence is easy to forget and worth remembering.
• Talk to peers. Other designers have had the same meeting. Hearing that is often more useful than any framework.
• Get a second opinion on the feedback itself. Sometimes the feedback is fair. Sometimes it is not. Someone outside the situation can usually tell the difference faster than you can.

If self-doubt is affecting your wellbeing beyond the occasional bad week, it is worth talking to a qualified professional. There is no prize for carrying it alone.

If you are the one giving the feedback

Many of the people reading this are not designers at all. They are business owners and founders reviewing work for their own website or product, unsure whether their reaction is useful. It is. You know your customers and your business better than anyone. A few habits make your feedback far more valuable:

• Agree what success looks like before the design begins, and judge the work against that.
• Describe the problem you see, not the solution you want. "Customers won't know what to do next" is more useful than "make the button red".
• Say when something is just your preference. It is completely fine to have one; labelling it helps the designer weigh it properly.
• Ask the designer to explain their reasoning before you ask for changes.
• Where you disagree and the stakes are real, test it with customers rather than settling it by rank.

The takeaway

Design is subjective in the way it is felt, and far less subjective in the way it works. The skill is knowing which part of a conversation you are in. Treat taste with respect, treat evidence as decisive, and make your reasoning visible. Do that consistently and fewer good ideas get rejected for bad reasons, and the ones that do will not shake your confidence quite so much.