For all the insights below in an easy-to-read PDF, check out our Naming Feedback Guide
"I love it."
"I hate it."
Both are honest. Neither one is useful.
If you've ever sat in a naming review, you know the moment. A shortlist goes up on the screen, and within about ninety seconds the room has already split into camps. Someone's sold. Someone else has a look on their face that says absolutely not, and can't quite explain why. Nobody in the room knows what to do with either reaction.
Naming is subjective. There's no getting around that. Put ten smart people in a room, show them the same list of names, and you will not get ten identical reactions. One person's favorite is another person's pass.
The skill isn't having the right taste. It's learning to read your own reaction and turn it into something the process can actually use.
Good feedback doesn't ask "do I like this." It asks "why am I reacting this way."
Here's how to get there.
Don't Stop at "I Like It" or "I Don't Like It"
Your reaction carries information. You don't need to suppress your gut response, and you shouldn't. The real job is figuring out what's driving it.
"I don't like it" can mean a dozen different things, and each one leads to a completely different conversation:
- It feels too playful for the brand
- It doesn't convey enough authority
- It sounds too close to a competitor
- I'm not sure how people will pronounce it
- It creates the wrong association
Instead of stopping at the reaction, try naming what's underneath it: "This feels more consumer facing than the positioning we're building toward."
That sentence gives the naming team somewhere to go. "I don't like it" doesn't.
Ask: Do I Dislike This, or Is It Wrong for the Brand?
Naming feels personal, because it is. We all carry words we love, sounds we don't, and private ideas about what a company should sound like. You don't need to pretend those preferences don't exist. You do need to recognize them for what they are.
If a name makes you a little uncomfortable because it's bolder than you'd have picked yourself, that discomfort isn't proof the name is failing. It might be proof the name has power, and the strategy behind it is working.
Two questions, every time:
Personal: Would I have chosen this name? Strategic: Does this name do what we need it to do?
Let the second one carry more weight.
Remember: New Names Start at a Disadvantage
Apple doesn't sound strange to you anymore. Neither does Uber, Warby Parker, or Slack. But you're not meeting those names for the first time. You've encountered them thousands of times, wrapped in logos, products, and years of accumulated meaning.
A name on a slide has none of that. It's the least flattering setting a name will ever be judged in.
So separate two kinds of strange:
Bad strange: Confusing, hard to say, tonally off, carries an unwanted association. New strange: Unfamiliar. You just haven't built a relationship with it yet.
Don't ignore "that feels weird." Don't give it center stage either. Give it time.
Picture It in the World
Reviewing names in a deck is an artificial exercise. You're judging a string of letters before it's become a brand. No visual identity, no product experience, no customer familiarity, no history behind it yet.
Try saying it out loud in context: "I work at ______." "Have you tried ______?"
Then be honest with yourself: can you see this name's potential? If the answer is no, don't put lipstick on a pig. If the answer is maybe, picture it further. As a wordmark. On a building. On a package. In color. Mock it up if you can. A name in isolation and a name in the world are two different tests.
Know What You Know, and What You're Assuming
"Our customers won't understand it." "People won't know how to pronounce it." "Our audience will think it's too weird."
These come from a real concern. But stakeholders often turn their own reaction into a prediction about everyone else. "I don't get it immediately" quietly becomes "customers won't get it."
Before you let that kill a name, break it into three columns: what do we know, what do we suspect, and what could we test. Don't let an assumption you could check in a day decide something permanent.
Treat Associations as Data, Not Verdicts
Most names trigger something. A word might call up another company, a childhood friend, a song, or something that happened twenty years ago. The existence of an association doesn't automatically make it a problem.
When one comes up, ask:
- How strong is it?
- How widespread is it likely to be?
- Is it relevant to our audience?
- Is it actually negative?
An association is a data point. It's not necessarily a verdict.
Don't Start Renaming in the Feedback Meeting
You're reviewing the name Evergreen. Someone says, "I like the idea, but what about Evergrove?" Someone else offers Everfield. Then Fieldgreen. A few minutes later, nobody's talking about Evergreen anymore. You're running a chaotic brainstorm instead of a review.
Alternatives feel productive in the moment, but they distract from the actual insight. Maybe the real takeaway wasn't that Evergreen should become Evergrove. Maybe it's that the team responds to the sense of permanence and growth in the name, but wants something more distinctive.
Let feedback name the opportunity. Let the creative process solve it.
Look for Patterns, Not Unanimity
The goal was never a name everyone loves equally. Get enough stakeholders in a room and instant, universal love for one idea simply isn't going to happen. Names are subjective, and the more distinctive a name is, the less likely everyone reacts to it the same way.
Look for patterns instead:
- Which names keep rising to the top?
- Which qualities are people actually responding to?
- Which concerns keep resurfacing, unprompted?
- Is the disagreement about strategy, or just taste?
- Is there a "safe" name nobody objects to, but nobody's excited about either?
The outcome you're after isn't everyone loving the same thing. It's everyone saying "I understand why this is right for us."
It's Not a Beauty Contest
Before evaluating anything, go back to the criteria you set at the start. What does the name actually need to accomplish? Maybe it needs to signal credibility in a conservative industry while still suggesting change. Maybe it needs room to stretch across a growing portfolio.
A name can be beautiful and strategically wrong. It can also be a little challenging at first and strategically right. Keep returning to the brief: how well does this solve the problem we set out to solve?
Good Feedback Creates Clarity
It tells the team where the energy is, where the hesitation is, and which concerns are real obstacles versus things that just need more time. You don't have to solve the problem. You just have to help the team understand your reaction. That might sound like:
"I like how distinctive this is, but I'm struggling with the tone. It feels more irreverent than we want to be."
"This wasn't an instant favorite, but the more I think about the strategy behind it, the more it grows on me."
"I have a strong negative reaction to this one, and I'm not sure why yet. I'd like to sit with it before we rule it out."
All three give the process somewhere to go. Consensus doesn't require identical taste. It requires shared confidence in the decision.
A Five Question Framework for Any Naming Review
Next time you're evaluating a serious contender, run it through these:
- What's my immediate reaction, and why? Don't censor the instinct. Capture it, then dig underneath it.
- How well does this fit our strategy and criteria? Move past personal preference. Evaluate the job the name was built to do.
- What does the name make me think or feel? Consider tone, imagery, associations, and expectations.
- Is this a real problem, a personal preference, or unfamiliarity? Not every concern deserves equal weight.
- What do I want the naming team to understand? You don't have to solve it. You just have to articulate it clearly.
Ten Things Not to Say in a Naming Meeting
None of these are deal breakers on their own. They're just incomplete.
- "I just don't like it." Keep going. What don't you like about it?
- "I Googled it and something came up." Worth investigating. Not automatically a reason to cut it.
- "It doesn't knock my socks off." Do your socks need to be knocked off?
- "Can we combine these two?" Say what you like about each one first.
- "My spouse hates it." Focus on the people the name actually needs to work for.
- "What if we just change one letter?" Name the problem before you try to solve it.
- "Our customers won't get it." What specifically will they struggle with, and what's the evidence?
- "It doesn't sound like us." What does "us" sound like? Today, or where the brand is going?
- "It sounds like a pharmaceutical." What's creating that impression? Length? Construction? Sound?
- "I'll know it when I see it." Defining what you're looking for gives you a shot at recognizing it.
You Don't Have to Fall in Love at First Sight
There's real pressure around a naming decision. It's the name your company will live with for years, so of course you want to feel good about it right away.
But great names don't always arrive as a lightning bolt. Sometimes they do. Other times, the right name is the one that keeps getting more interesting. The one you're still thinking about the next morning. The one that makes more sense the longer you sit with it.
Give yourself permission to react. Then get curious about the reaction.