We have sat in on a lot of naming sessions. Some belonged to clients we were working with. Many were internal sessions teams had run before they came to us, often after realising that two days at a whiteboard had not produced a decision.
The mistakes are remarkably consistent. They are not failures of intelligence or creativity. The teams in question are usually capable, motivated and well-resourced. The mistakes are structural. They are baked into how internal naming sessions are usually set up.
If you understand the five patterns, you can change the structure. The session that used to end in fatigue and disagreement can end in a decision the team is ready to defend.
Pattern one: Generating before strategy
This is the most common failure. The session opens with the question “what could we call it?” and everyone reaches for their favourite ideas. Within twenty minutes there are forty names on the wall. Within an hour the team is arguing about half a dozen they cannot let go of.
The problem is that nobody has agreed what the name needs to do. Without that agreement, names are evaluated against private preferences. One person is looking for distinctive, another is looking for safe, another is looking for clever, another is looking for descriptive. They are all right, in isolation. They are all wrong together.
The fix is to push the generative work back by a stage. Before any names get drawn, the session needs to produce shared answers to three questions. What does this business actually do, in plain language. Who is it for, specifically. What does the name need to achieve for the business that the current name or the absence of a name cannot.
These three questions look small. They are not. We have seen leadership teams spend the first ninety minutes of a naming session realising they did not agree on the answers. That conversation, painful as it can be, is the most important work of the day. The names that come afterwards are quicker, sharper and easier to choose between, because the team is now judging them against the same criteria.
Pattern two: Treating opinion like data
In naming sessions without structure, the dominant currency is opinion. The CEO likes one name. The head of marketing prefers another. The designer is drawn to a third. The argument that follows is sometimes interesting and rarely conclusive, because no opinion outranks any other and there is no third party to settle the difference.
This pattern is not solved by adding more opinions. It is solved by changing what the opinions are about.
When the question becomes “which of these names is your personal favourite,” the team is locked into a popularity contest. When the question becomes “which of these names best meets the criteria we agreed at the start of the day,” the same people who were stuck can suddenly move. They are no longer defending taste. They are weighing the candidate names against shared standards.
The criteria do not have to be elaborate. Strategic fit, distinctiveness, audience clarity, memorability, defensibility, future-fit and operational use will get you most of the way. The point is that the team can point to one of those when they have a concern, and the conversation moves from “I don’t like it” to “I don’t think it fits the strategic territory we agreed.”
That single shift removes most of the friction from naming sessions. The criteria become the referee.
Pattern three: Defaulting to safety
A subtle but expensive mistake. When a team is uncertain, the names that survive the session tend to be the ones nobody objects to. The bold names get cut because they create discomfort. The boring names persist because they offend no one.
The problem is that boring names rarely lose, but they also rarely win. They do not generate enthusiasm in stakeholders. They do not stick in customers’ memories. They do not lift internal pride. They are tolerated, which is not the same as chosen.
The reason this pattern is so persistent is that the cost of a bold name failing is visible. Someone in the room has to be the person who supported it. The cost of a safe name underperforming is invisible. It happens slowly over years, and there is nobody to point to.
A useful corrective is to put a price on safety in the conversation. Ask the room what would happen if the brand chose this name and grew with it for ten years. Would it be the best name they could have chosen, or would they look back and wish they had been braver? The answers are often more honest than the in-the-moment evaluations.
This does not mean the most daring name always wins. It means the conversation about boldness becomes part of the decision, rather than something the team finds out about three years later when a competitor with a stronger name is winning the room.
Pattern four: The “domain check” derailer
There is a moment in almost every internal naming session when somebody opens a laptop and starts checking domain availability. The room follows along. A name everyone was warming to gets dropped because the .com is taken, even though .co or a country-specific TLD is available and arguably better. A name nobody loved gets a second look because the domain is clean. The strategic conversation is now being made by a registrar.
Domain availability matters. It is not the criterion that should decide the name.
The fix is to time-shift the domain check. Do not do it live in the strategic part of the session. Do it once a small set of candidate names has emerged. At that point, the check is informational, not directional. You are finding out what trade-offs each candidate involves, not letting domain availability pick the winner.
The same principle applies to the obvious-brand-conflict check and to the basic trademark scan. They are useful inputs at the right moment. They are saboteurs of strategic thinking when they happen too early.
Pattern five: Sunk-cost on the working name
When a project has been running under a working name for months, the working name has accumulated emotional value. The team has used it in meetings, written it in slides, said it to potential customers. Even when the team agrees in principle that a stronger name exists, the working name has a gravitational pull.
The result is that the new name has to be much better, not just better, to win. The team is unconsciously asking the new name to compensate for the social cost of moving on from the working name. This is rarely fair to the new name.
A small structural fix helps. Treat the working name as one of the candidates, with no special status. Score it against the same criteria as the others. Sometimes the working name turns out to be the right answer for the right reasons, and the team can move forward with confidence. More often, the working name shows clear weaknesses against the criteria, and the team has a reason to move on that is not “we got bored of it” or “the strategists pushed us off it.” The reason is structural and the team can defend it later.
What a better naming session looks like
If you want to run a naming session that produces a decision rather than a debate, structure it in three stages.
Stage one: Strategic alignment. No names. The first ninety minutes are spent agreeing what the business does, who it is for, and what the name needs to do. This is also the moment to agree the criteria you will judge against. End the stage with a written summary that everyone in the room signs off on. If you cannot get to that summary, do not move on. The session is not yet ready to generate names.
Stage two: Generation, without judgement. Once the strategy is locked, the team generates candidates against the agreed direction. The rule of this stage is that nobody criticises a candidate while names are still being generated. The point is breadth. Bad ideas often unlock good ones if they get to live long enough to inspire the next candidate. End the stage with a list of perhaps thirty to fifty candidate names, organised loosely by territory.
Stage three: Structured assessment. Now the criteria from stage one come back. Each candidate is scored against them. The names that fail multiple criteria are cut. The names that pass most are pressure-tested. The names that emerge from this stage have a reason to be there, and the reason is one the team can describe to their board, partners, customers or auditors.
This three-stage structure does not guarantee a brilliant name. It does guarantee that the team will not get stuck in any of the five patterns above. The session ends with a decision the team understands, can defend and will commit to.
The decision you can defend
The biggest lesson from a decade of naming sessions is also the simplest. Sessions fail because of structure, not because of talent. Even very capable teams produce poor outcomes when the structure of the session pushes them into preference contests, premature domain checks or boring compromises. Even small teams produce excellent outcomes when the structure aligns the strategic work before the creative work, and when the creative work is judged against shared criteria.
If you are about to run an internal naming session, the most useful thing you can do is design the structure carefully before booking the room. The names will come. The decision will only come if you have made room for it.
Re:name’s Guided Strategic Naming process automates this three-stage structure for teams that want to run their own naming work without the typical failure patterns. Strategy is captured before any names are generated. Candidates are produced against the agreed territories. Assessment happens against shared criteria. The decision report at the end summarises the thinking so the team can present it to whoever needs to sign off.