# Scientific Brand Naming Process

> A framework for creating distinctive, high-value brand names using linguistic engineering, disguised briefs, and the polarization test. Use this when naming a new product, rebranding a startup, or when internal teams are stuck on "safe" but forgettable descriptive names.

- Skill: `samarv/scientific-brand-naming-process` (Agent Skill)
- Install (CLI): `npx skillmds@latest add samarv/scientific-brand-naming-process`
- Raw SKILL.md: https://api.skillmd.com/api/skills/samarv/scientific-brand-naming-process/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: samarv (https://skillmd.com/u/samarv)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/samarv/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.

1.  **Top (Win):** Define what "winning" looks like for the company.
2.  **Right (Have):** List the assets or "unfair advantages" you already possess.
3.  **Bottom (Need):** Identify what you still need to win (e.g., "We need to look bigger than we are").
4.  **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.
