There is a meeting that happens in every naming project. The shortlist is on the screen. The CEO has an opinion. The marketing director has a different one. Someone from operations has been quiet for ten minutes and then says, almost apologetically, “I just don’t love any of them.”
The room stalls. Not because the names are bad. Because nobody has the words to assess them.
This is not a creativity problem. It is a judgement problem. Most teams have never been given the language to separate “this is interesting” from “this can carry a brand for ten years.” So the conversation defaults to the only currency on hand, which is preference. And preference is not a strategy. It is not even consistent over time. The name you love on Tuesday is the name you are tired of by Friday.
The shift that unlocks the decision is moving from like to judge.
Why “like” is the wrong question
Liking a name is a private feeling. Judging a name is a public act. The team needs to be able to say, out loud, in a room with stakeholders, why a name is the right one. “I like it” cannot survive that conversation. It does not bind. The next person can simply not like it back, and you are at a draw.
There is a more practical problem too. Liking is conditional on the moment. The name you instinctively prefer on the day of the shortlist is shaped by the order you saw the names in, what mood you were in, who was sitting next to you, and whether you had coffee that morning. A name chosen on this basis is not robust to the next week, let alone the next decade.
Names that endure are chosen on different grounds. They are chosen because they pass a structured test against criteria the team has agreed are important. This is what a senior naming practice actually does behind closed doors. It is not that experienced strategists have better instincts. It is that they have replaced the question “do I like this?” with the question “does this do the job?”
That question can be broken down.
Seven criteria for judging a name
We use seven lenses when assessing a shortlist. They do not produce a single score. They produce a more textured picture: where each name is strong, where it is weaker, and what trade-offs you are making. The team can then choose with their eyes open.
Strategic fit. Does this name belong to the business you actually are? A name pulled from the wrong territory will work against you every time someone hears it. If you are a precision engineering business, “Lumen” sounds nice but signals lighting. If you are a wellbeing service, “Forge” might be admired but it is fighting your category.
Distinctiveness. Does this name stand out from your direct competitors when written, spoken and remembered? Most categories have a default sound. Tech goes percussive. Finance goes Latin-rooted. Healthcare goes soft and humane. A name that lands inside the default sound is easy to write, hard to recall. Distinctiveness is not novelty for its own sake. It is the ability to be remembered as you, not as the one that sounded like the others.
Audience clarity. When the right buyer hears or reads this name for the first time, does anything register correctly? Or do they have to work to understand what you do, and then again to understand what you stand for? Some categories tolerate ambiguity. Most do not.
Memorability. This is where instinct often misleads people. We assume short names are memorable and long names are not. The truth is more specific. Memorable names tend to be either descriptive (so the brain has somewhere to file them) or evocative in a way that creates a small, clear image. “ChargeNet” is memorable because it is what they do. “Niko” is memorable because the sound is unusual in its category. Both work, for different reasons. “Synaptive” is memorable to nobody.
Defensibility. This is the criterion most teams skip and most boards ask about. Are there any obvious brand conflicts? Are the relevant domains available, or available at a sensible cost? Will a trademark application be straightforward in the territories that matter? Defensibility is not the same as legal clearance, which only a lawyer can give. But a name that fails the obvious checks now will keep failing them later.
Future-fit. Where is the business going in three to seven years? Will this name still describe it then? A name that perfectly fits today’s business can become a constraint when the business grows. “Auckland Trailers” worked in 1998. It works less well when the company is selling across Australia. “Absolute Wilderness” worked as a niche outdoor food brand. It limited the brand when it wanted to be on supermarket shelves. The renamed business, Real Meals, did not have that ceiling.
Operational fit. Can the team actually use this name? Can the receptionist say it on the phone without getting asked to spell it? Can a salesperson say it in a meeting without explanation? Does it fit on signage, in invoice headers, in email addresses, in legal documents? This sounds prosaic. It is often what kills names that scored well on every other lens.
How to use the seven lenses in a meeting
The point of the framework is not to give a name a score out of seven. It is to change the language of the conversation.
When somebody says “I’m not sure about that one,” the next question is no longer “why don’t you like it.” It is “which lens is it failing?” That single shift removes the defensiveness from the room. The person who flagged the concern is now contributing to the decision, not blocking it. Everyone else now has somewhere to point.
The conversation that used to be “we cannot agree” becomes “we agree it is strong on distinctiveness and audience clarity. We are less sure on operational fit. Let us test that.” That is a decision the team can move forward on.
We have seen the difference this makes in renaming projects across healthcare, social services, FMCG and engineering. The names that get to the finish line are not always the ones the team liked at first glance. They are the ones that hold up against the seven lenses, and the ones the team can explain to a board, a partner, a sceptical investor or a long-term staff member.
What this looks like in a real project
Niko is a useful example. The previous name was a working name the founders were attached to but it was creating confusion in market with a much larger competitor. The team came in liking several candidates, including some that scored well on distinctiveness but poorly on strategic fit.
Niko emerged not because anyone fell in love with it. It emerged because it scored well on six of the seven lenses. It was distinctive in the category, it had cultural and historical resonance to Nikola Tesla without infringing, it was short enough for operational use, the domain situation was workable, and it had headroom for the business to grow into new offers. The seventh lens, future-fit, was the deciding criterion. The team could see Niko as the brand in five years. They could not see the others.
The point is not that Niko is the best name. The point is that the framework let the team explain to themselves and others why it was the right name for that decision. That is a different conversation from “we liked it best.”
The decision you can defend
In ten years of naming work, the strongest pattern we have seen is this. Teams that choose names by preference revisit the decision more often. Teams that choose names by judgement build on the decision and move on. The first kind of project keeps coming back to the question of whether the name is working. The second kind stops asking.
This is not because the second team chose a better name. It is because they have an account of why they chose it. When a stakeholder asks the question, they have an answer that is not “we liked it.” They have an answer that is “we chose it because it was the strongest on the criteria that mattered.”
That is the difference a small change in language makes. It is also what makes naming feel less like a coin toss and more like a decision a board can sign off on.
If you are sitting at the start of a naming project, this is the question worth answering before anyone draws a single name. What criteria will you judge against? If you do not know yet, that is the first piece of work. The names come later, and they come much more easily.
Re:name productises this assessment framework inside Guided Strategic Naming. Your shortlist is scored against the seven lenses automatically, so the team can see where each name is strong, where it is weaker, and which trade-offs are being made. The decision report you receive is built around this framework and is designed to be presented to a board, a business partner or a leadership team without further translation.