Run a Product Naming Workshop with Clear Criteria

Write the naming brief before generating ideas

Describe the product’s role, audience, and intended associations. Identify terms to avoid because they are misleading, too narrow, or inconsistent with the product’s direction. Decide whether the name needs to communicate the category directly or can rely on accompanying explanation. This choice changes the evaluation, so make it explicit before discussing candidates.

Consider a hypothetical product for coordinating shared equipment. A highly descriptive name may explain the task quickly but become restrictive if the product later supports spaces as well. An abstract name offers flexibility but requires more explanation. The brief should record the tradeoff rather than expecting one candidate to be perfectly descriptive, distinctive, short, and universally expressive.

Generate across different naming approaches

Explore descriptive, suggestive, metaphorical, and invented directions as separate routes. Give each route enough attention to produce meaningful alternatives. Avoid making a list of slight variations on the first attractive word. Invite contributors to explain the association or story behind a candidate, while postponing judgment during the initial generation stage.

For equipment coordination, one route might emphasize shared availability, another reliable handovers, and another the sense of a central place. Keep these themes tied to the product. A clever pun can be enjoyable without helping recognition or pronunciation. Capture the rationale so the shortlist can be evaluated on more than whether a name sounded appealing during the workshop.

Evaluate candidates in realistic use

Use a small set of criteria such as clarity, intended associations, pronunciation, spelling, flexibility, and fit in required formats. Put each candidate into a spoken introduction, a product header, and a support sentence. Ask relevant people what they infer without first explaining the intended story. Their initial associations can reveal confusion that internal enthusiasm misses.

In the hypothetical equipment product, test whether someone can repeat the name after hearing it and distinguish it from an ordinary task label. Include audiences with relevant language differences where the product requires them. Avoid treating feedback as a popularity vote. A candidate may be liked but still imply a service the product does not provide.

Separate selection from factual checks and rollout

Create a shortlist with reasons, concerns, and required follow-up. Verify relevant practical availability through the responsible owners and appropriate processes before final adoption. Domain strings, account handles, and existing uses are separate facts that the creative workshop cannot establish. Keep alternatives available while checks are completed rather than prematurely building every asset around one favorite.

Once a candidate is selected, define spelling, capitalization, pronunciation guidance, and how it appears beside a product descriptor. Test the final form in small and content-heavy applications. Record why the name was chosen and which interpretations should be avoided in messaging. This context helps future writers preserve the intended meaning without repeating the whole naming exercise.

• Define category clarity and future scope needs.
• Explore genuinely different naming routes.
• Test spoken and written use with relevant people.
• Complete practical checks before final adoption.

Once the name and descriptor have passed the relevant checks, define the identity’s recognition needs, applications, and practical constraints before exploring visual directions.Write a Visual Identity Brief for a Product