ProductIntermediate6 min read

Product Naming

Product naming is the discipline of deciding what to call a product, a feature, a SKU tier, and the relationships between them. Good names are pronounceable, ownable (trademark + .com), categoryally clear, and structurally consistent across the portfolio. Naming sits inside a 'naming architecture' — the system that decides whether a new capability becomes a Product (Atlassian Jira), a Sub-Product (Jira Service Management), a Feature (Jira Automation), or a Tier (Jira Premium). Apple's discipline — iPhone, iPad, MacBook Pro, iPad Pro — is naming architecture: a noun (the device), a modifier (the tier), no clever wordplay. Atlassian's discipline — Jira, Confluence, Trello, Bitbucket — uses memorable noun-products, then 'Jira X' for sub-products. Naming chaos compounds: every new SKU costs sales reps 30 seconds of confusion per call.

Also known asNaming StrategyBrand NamingProduct Name Architecture

Challenge a friend Browse library

The Trap

The trap is naming as a brainstorming exercise — generating clever portmanteaus in a Friday workshop without a naming architecture. The output is names that are unsearchable (generic dictionary words), unpronounceable in customer markets, already trademarked, or incompatible with the portfolio (e.g., one product is verb-based, another is metaphor-based, a third is an acronym). The deeper trap: founders rename existing products to be 'cooler,' destroying SEO, breaking documentation, and confusing existing customers. Renames cost 6-12 months of brand equity and should be reserved for category-redefining moments.

What to Do

Before naming, define the architecture: (1) Are you naming a Product, Sub-Product, Feature, or Tier? (2) Does the parent brand prefix it? (3) What's the 'naming pattern' (descriptive, evocative, abstract, founder-name, or acronym)? Pick ONE pattern per portfolio level. Then run every candidate through 5 filters: (a) Trademark search via USPTO + WIPO. (b) .com availability or strong .io/.app alternative. (c) 5-second pronunciation test with 10 strangers. (d) International scan — does it mean something embarrassing in Spanish, Mandarin, or German? (e) Search-volume test — can you rank for it on Google within 12 months? Kill any name that fails 2+ filters.

Formula

Name Quality Score = Pronounceability + Ownability + Category Clarity + Architecture Fit + Search Defensibility (each 0-2, max 10)

In Practice

Apple's naming discipline is the most studied case in product naming. The portfolio uses a 'noun-modifier' pattern: iPhone, iPad, MacBook, AirPods, Apple Watch. Tiers stack predictably: Pro, Air, mini, Max, Ultra. Numbering is generational and skips deliberately (no iPhone 9 — went 8 to X to align with the 10-year anniversary). The architecture is so rigid that customers can predict next year's name. By contrast, Microsoft's Surface line — Surface, Surface Pro, Surface Laptop, Surface Go, Surface Studio, Surface Duo, Surface Neo — created confusion because the modifier doesn't reliably indicate tier vs. form factor (is 'Pro' a tier or a form?). The result: Apple sustains higher per-device pricing partly because the name itself signals confidence and category leadership.

Pro Tips

01
Atlassian's rule: own the noun, then qualify it. 'Jira' is a noun (originally short for 'Gojira,' Godzilla in Japanese — an internal joke about competing with Bugzilla). Sub-products are 'Jira [Function]' — Service Management, Software, Work Management. This lets them ship a new sub-product without inventing a new brand.
02
Avoid generic dictionary words for products you want to defend. 'Slack' was defensible because in 2013 the word had no software meaning; today, 'Notion,' 'Linear,' and 'Loom' are increasingly hard to defend in trademark disputes. Made-up or repurposed words are stronger long-term assets.
03
When renaming, NEVER rename a product mid-growth-curve. If you must rename, do it within the first 18 months OR after a major strategic pivot. Mid-growth renames (Facebook → Meta, Twitter → X) cost billions in brand equity and search authority.

Myth vs Reality

Myth

“A great product name is the difference between success and failure”

Reality

Mediocre names backed by great products win all the time — Google was originally 'BackRub,' Twitter was 'twttr,' Pepsi was 'Brad's Drink.' Naming matters at the margin, not at the core. The downside risk is real (a bad name limits ceiling), but no name has ever saved a bad product.

Myth

“Descriptive names (e.g., 'BestEmailMarketing.com') beat abstract names because they signal category”

Reality

Descriptive names rank well in early-stage SEO but cap brand equity. They are commodified ('best,' 'pro,' 'fast' are claimed by 1000 competitors), un-trademarkable, and signal small thinking. The strongest brands are abstract (Stripe, Notion, Vercel, Linear) — they earn category meaning through usage, not by claiming it in the name.

Try it

Run the numbers.

Pressure-test the concept against your own knowledge — answer the challenge or try the live scenario.

🧪

Knowledge Check

You're launching a new sub-product inside an established platform brand 'Velar.' It handles AI-powered document drafting. Which naming approach is most strategically sound?

Industry benchmarks

Is your number good?

Calibrate against real-world tiers. Use these ranges as targets — not absolutes.

Distinct Naming Patterns Per Portfolio (Healthy)

B2B SaaS portfolios with 5-20 active SKUs

Disciplined (Apple, Atlassian)

1 pattern

Healthy

2 patterns (product + tier)

Drifting

3 patterns

Confused

4-5 patterns

Chaos (rename overdue)

6+ patterns

Source: Internal benchmarks across enterprise software portfolios

Real-world cases

Companies that lived this.

Verified narratives with the numbers that prove (or break) the concept.

🍎

Apple

2007-present

success

Apple's naming architecture is the most disciplined in consumer tech. The pattern is rigid: noun (iPhone, iPad, MacBook, AirPods, Apple Watch) + tier modifier (Pro, Air, mini, Max, Ultra) + generation number or year. The 'i' prefix was retired post-iPad as Apple matured the brand. Product names are intentionally not clever — they describe the device. This discipline lets Apple ship a new product (Vision Pro) and immediately signal: this is a Pro-tier device in a new category. Customers can predict naming a year out.

Naming Patterns Used

1 (noun + tier modifier)

Cross-Product Recall

~95% in surveyed buyers

Trademark Defenses Won (notable)

iPhone vs. Cisco (2007), settled

Outcome

Highest brand equity in tech ($500B+)

Naming discipline is a moat. When customers can predict your next product name, you've built mental shelf space that competitors can't take.

Source ↗

🔧

Atlassian

2002-present

success

Atlassian's architecture: own a memorable, slightly weird noun for each product (Jira, Confluence, Trello, Bitbucket, Loom), then sub-product as 'Jira [Function]' (Service Management, Software, Work Management). Jira itself was originally named 'Gojira,' Japanese for Godzilla, an internal joke about competing with Bugzilla. The names are abstract enough to defend in trademark, memorable enough to stick, and the sub-naming pattern lets them ship Jira Service Management, Jira Product Discovery, etc. without re-branding. Confluence keeps its own name because it pre-dated the architecture and has independent equity.

Top-Level Product Brands

5 (Jira, Confluence, Trello, Bitbucket, Loom)

Sub-Product Naming Pattern

Parent + Functional Modifier

Total Active SKUs

~15

Naming-Related Customer Confusion

Low — sub-products map clearly to parent

Hybrid architectures work IF each top-level brand stands alone AND sub-products inherit predictably. Don't try to make every product follow the same pattern — let mature brands keep their equity.

Source ↗

Related concepts