scientific-brand-naming-process
Scientific Brand Naming Process
A great brand name provides a "cumulative advantage" (it sticks in the mind longer) and an "asymmetric advantage" (it gives you a head start over competitors). To achieve this, move away from descriptive names that describe what you do and move toward distinctive names that create an experience.
The 3-Step Science of Naming
1. Identify (Behavioral Mapping)
Instead of starting with mission statements or positioning, focus on behavior and experience.
- Bi-directional Behavior: Analyze how the market behaves toward you and how you behave toward the marketplace.
- Landscape Analysis: Map the language used by competitors. Identify the "ocean" of similar names (e.g., "Cloud-something") specifically to avoid them. Imitation is a form of brand suicide.
- Creative Framework: Define the "window" the name should travel through. Focus on the rhythm of the experience (e.g., "calming" like Dasani vs. "noisy" like Azure).
2. Invent (The Disguised Brief Method)
Avoid large brainstorming sessions. Instead, use small teams of two and provide different contexts to force "synchronicity."
- Team A (Direct): Given the full, accurate brief.
- Team B (Competitor Shift): Given a brief disguised as a competitor (e.g., if building for Microsoft, pretend the client is Apple).
- Team C (Category Shift): Given a brief for a completely different product type (e.g., if naming an AI tool, pretend you are naming a bicycle or a high-end watch).
- Goal: Generate 1,000–1,500 ideas. Do not evaluate; speculate on what each word could become.
3. Implement (The Polarization Test)
The goal is not consensus; it is "signal."
- The Comfort Rule: If the team is immediately comfortable with a name, you haven't found the right one yet.
- Look for Tension: Polarization in a team is a sign of strength in the word. It indicates the name has enough energy to cause a reaction.
- Prototypes: Don't present a list of words. Put the names on T-shirts, mock-up ads, or a Wall Street Journal headline to show how the name "lifts" the brand's perceived value.
Linguistic Engineering (Sound Symbolism)
Every letter carries a specific "vibration" or cognitive signal. Use these to build the desired energy into a coined name:
- V (Alive/Vibrant): The most energetic sound. Use for innovation and speed (e.g., Vercel, Viagra, Corvette).
- B (Reliable/Solid): Use for stability and trust (e.g., BlackBerry).
- Z/S (Noisy/Distinctive): High signal strength in a busy marketplace (e.g., Sonos, Azure).
- X (Fast/Crisp): Associated with innovation and cutting-edge tech.
- Compounds (1+1=3): Combine two words to multiply associations (e.g., Windsurf, Powerbook).
The Startup "Diamond Exercise"
Use this 4-point framework to narrow down what a name must achieve when you have limited time.
- Top (Win): Define what "winning" looks like for the company.
- Right (Have): List the assets or "unfair advantages" you already possess.
- Bottom (Need): Identify what you still need to win (e.g., "We need to look bigger than we are").
- Left (Say): Determine what you must say to the market to trigger the desired behavior.
Examples
Example 1: Naming a high-performance developer tool
- Context: A startup building an AI-powered coding assistant currently named "CodeBot."
- Input: "We want to sound smart but professional."
- Application: Use the Category Shift brief. Tell one team to name a "Formula 1 Racing Team." They come up with "Vortex" or "Draft." Use the Sound Symbolism of V for vibrancy and X for crispness.
- Output: A name like Vectra or Apex—moving from a descriptive name (CodeBot) to an experience-led name.
Example 2: Testing a bold name for a consumer app
- Context: A team is split between a safe name ("HomePay") and a bold name ("Stash").
- Application: Apply the Competitor Launch Test. Ask 10 people: "Our new competitor just launched, they're called Stash. What do you imagine they do?"
- Result: If people say, "I bet they are faster/cooler than the other guys," the name has created a "predisposition to consider."
Common Pitfalls
- Seeking Comfort: Choosing a name because "everyone likes it" usually results in a descriptive, forgettable name that lacks market power.
- The .com Obsession: Don't discard the "right" name because the domain is taken. The URL is just an "area code"—prioritize the brand name's signal over the .com.
- Asking "Do you like this?": This is a low-value question. Instead ask, "What does this name make you imagine?" or "What kind of expectations does this name set?"
- Stopping Too Early: Most teams stop at 200 names. The "diamonds" usually appear after the first 1,000 ideas when the obvious options are exhausted.
More from samarv/shanon
agentic-workflow-automation
Transition from static LLM chats to autonomous agents that execute multi-step tasks. Use this when you need to automate cross-platform reports (e.g., Snowflake to Google Docs), build self-service tools for non-technical teams, or create "anticipatory" engineering workflows that draft PRs based on Slack discussions.
62b2b-value-negotiation
A framework for defending price and extracting maximum value in B2B sales. Use this skill when a prospect asks for a discount, when transitioning a POC to a commercial deal, or when presenting high-ticket pricing to budget-conscious stakeholders.
18niche-market-opportunity-mapping
A framework for identifying high-margin, low-competition business ideas ("fishing holes") by leveraging personal unfair advantages and avoiding overcrowded markets. Use this when vetting a new startup idea, choosing a niche for a service business, or seeking to pivot an existing product into a more profitable segment.
16b2b-saas-workflow-strategy
A framework to evaluate the market potential and strategic direction of B2B products based on workflow frequency and organizational breadth. Use it when validating a new startup idea, evaluating a product's "ceiling," or planning a pivot to increase market share.
14agentic-engineering-workflow
Transition from a hands-on "bricklayer" to a high-level "architect" by managing a fleet of autonomous AI agents. Use this when you need to scale engineering output with a small team, handle repetitive migrations/bug fixes, or onboard engineers to complex legacy codebases.
10b2b-category-creation-strategy
A framework for determining when to create a new software category versus winning an existing one, and the tactical steps to define and validate that category. Use this when your product is too disruptive for current labels, when existing categories have negative associations, or when you need to expand your TAM.
9