War-game a product naming system before SKUs, tiers, and codenames quietly collide in market, support tickets, and partner decks.
Naming systems fail when tiers reuse words customers already use for something else, when legal clears a name that sales cannot pronounce on a call, when codenames leak into public docs, and when support still invents nicknames because the official set is unusable. A clean naming memo is not evidence that the company can hold a coherent story under pressure.
Freeze one system
Write the naming rules, the inventory of current names you will retire or keep, the trademark and domain checks you will defend, and the first quarter outcomes that still must hold if a collision appears. Then write the owner for each name family and the kill criteria if customers or partners confuse the set. If you cannot name the owner or the kill criteria, the system is decoration.
Freeze product names, tier labels, feature names, and the migration path from old to new. Attach search collision notes, ticket themes, and residual risk you will accept. Split any secondary brand repositioning into a separate decision. One naming system under fire at a time.
Hostile seats
- Brand seat: confusion with category language and competitor names.
- Legal seat: trademark, domain, and international clearance gaps.
- Sales seat: names that stall demos or invite discount theater.
- Customer or support seat: nicknames, ticket tags, and renewal language that still use old names.
- Skeptic seat: the claim that looks cleanest and has the least evidence.
Ask each seat for material objections, missing exhibits, and the smallest change that keeps the intent without the theater. Optional partner seat if channel kits already ship conflicting labels.
Private pass
Run that package in Pingpong. Sequential review helps because an early pass can defend the clarity upside while later passes try to kill soft clearances and dual-counted brand equity. Keep a change log of names cut, sequenced, or clarified. If survival requires silence about a single hero name or a heroic trademark guess, stop. Rewrite the system or delay the "ready" label.
Publish the activation calendar inside the package: when docs flip, when managers are briefed, and when support locks ticket tags. A product naming system without dated owners is a rumor with a spreadsheet. Ask brand and support seats to break that calendar before anyone posts the first public rename.
Related: war-game a naming decision, war-game a brand repositioning, war-game a packaging change, war-game a pricing page rewrite, and AI for high-stakes decisions. Mechanics: how it works.