Lenny's PodcastDavid Placek: Why a name your team likes is the wrong name
Through Lexicon's polarization test and sound symbolism research; Sonos was rejected as not entertainment-like before becoming a billion-dollar asset.
CHAPTERS
- 0:00 – 5:28
Why brand names endure (and why clients resist bold choices)
David Placek opens with the core premise: a brand name outlives design, messaging, and even product iterations. He and Lenny frame the central tension in naming—teams seek comfort, but market-winning names often feel uncomfortable at first.
- •A name is the most-used, longest-lasting brand asset
- •Teams often expect they’ll “know it when they see it,” but rarely do
- •Comfort is the enemy of distinctiveness; bold names create advantage
- •Good naming requires helping teams tolerate initial discomfort
- 5:28 – 9:27
Case study: Fighting for—and winning—Sonos
David recounts how Sonos was initially rejected for not sounding “entertainment-like.” He explains the rationale (sound-first identity, palindrome qualities) and how reframing the decision around customers—not founders—helped the team commit.
- •Sonos was rejected because it didn’t match the founders’ initial category framing
- •Repositioning: not an entertainment company—an experience of sound
- •The palindrome/visual symmetry created additional appeal and memorability
- •Naming for the market (not internal preference) unlocked agreement
- 9:27 – 11:44
The psychology of naming: comfort, familiarity, and ‘creating the future’
David digs into why people reject great ideas: humans use past success as a comfort signal. He argues naming is less about reciting mission/values and more about designing future behavior and experience in a complex, digital world.
- •Humans default to what has worked before; novelty triggers skepticism
- •Great creative work is often rejected repeatedly (Harry Potter, Call of the Wild)
- •Lexicon starts with behavior and future experience, not traditional positioning language
- •A name should start a story, not merely make a statement
- 11:44 – 14:34
Case study: Microsoft Azure and the push beyond ‘cloud’ descriptors
Microsoft initially wanted a name that included “cloud,” which David argues would drown in sameness. Azure won by pairing a subtle semantic link (blue sky) with strong phonetic signaling—distinctive, balanced, and story-starting.
- •Descriptor naming (e.g., Cloud____) creates category blending and weak differentiation
- •Azure connects to sky/blue while avoiding generic “cloud” naming
- •Phonetic strategy: ‘noisy’ signal (Z) plus smoother ending for balance
- •Early reactions can be harsh; warming up takes discussion and time
- 14:34 – 18:12
How much a name matters: cumulative and asymmetric advantage
David explains the business value of naming in two layers: long-term compounding brand association and day-one differentiation. A great name won’t replace product quality, but it can meaningfully tilt market dynamics in your favor.
- •Cumulative advantage: repeated exposure strengthens brand-customer bond over time
- •Asymmetric advantage: start with differentiation before you even launch
- •Descriptive names struggle to stand out in crowded markets
- •Lexicon’s goal is the right name—not merely a good name
- 18:12 – 28:22
Lexicon’s three-step naming method: Identify → Invent → Implement
David outlines Lexicon’s end-to-end process: clarifying desired behavior/experience, generating and engineering candidate names, and then supporting internal selling and go-to-market execution. The method blends creativity with discipline and screening.
- •Identify: behavior + experience discovery, plus competitive language landscape
- •A ‘creative framework’ replaces rigid objectives to keep exploration broad
- •Invent: creative generation plus an ‘engineering layer’ of linguistic tools
- •Implement: help clients present, prototype, research, and gain approvals
- 28:22 – 31:39
Who creates great names: resilient writers, small teams, and productive constraints
Lenny probes the human side of Lexicon’s output. David describes the traits and backgrounds that work best—curiosity, low ego, tenacity—and why big brainstorms underperform compared to small, deliberately-briefed teams.
- •Best namers are curious, hardworking, resilient, and ego-light
- •Large brainstorms produce weaker outcomes; small teams outperform
- •Teams get different briefs (sometimes disguised contexts) to unlock creativity
- •Output volume matters: generating hundreds quickly, then continuing past rejection
- 31:39 – 32:54
Timelines and throughput: why naming is fast—but still rigorous
David sets expectations for how long professional naming typically takes and why. He also explains the reality of the funnel: thousands of ideas shrink through legal and linguistic screens into a handful of viable finalists.
- •Typical timeline: ~8 weeks; large corporations often 3–4 months
- •Early funnel can reach 2,000–3,000 ideas/directions (not all shippable)
- •Trademark clearance is increasingly difficult and shapes final options
- •Two presentation cycles help clients compare, learn, and refine judgment
- 32:54 – 36:11
Windsurf case study: making intangible AI tools feel tangible
Using Codium→Windsurf, David shows how metaphor and physical experience can make abstract tech feel graspable. He also argues compounds can be powerful “association multipliers,” despite common client bias toward shorter single words.
- •Rule: if the product is intangible, make the naming exploration tangible
- •Windsurf emerged from a ‘flow/dynamics’ metaphor direction
- •Compounds multiply associations (wind + surf → richer mental imagery)
- •Availability and executional ease (visual/story cues) supported adoption
- 36:11 – 39:23
Naming in the AI era: engineer preferences, speed of change, and consumer skepticism
David contrasts developer optimism with consumer ambivalence about AI, based on Lexicon’s international research. He warns against overly “sophisticated” coined names that please insiders but feel cold or abstract to broader markets.
- •AI is the fastest-moving category David has seen (faster than early internet era)
- •Engineers often request complex/technical names; market may need warmth/tangibility
- •Research split: developers positive; consumers more skeptical and job-anxious
- •Naming strategy shifts toward natural, vivid, experience-based signals
- 39:23 – 42:58
When to change your name: ‘we just needed something’ vs. real strategic need
Lenny asks about the surge in AI companies renaming products and companies. David outlines the main triggers for renaming and emphasizes the need for a clear argument that the change creates net advantage, especially as the company grows.
- •Renaming is harder as your customer base grows—requires strong justification
- •Startups often rename because the first name was a rushed placeholder
- •A pivot can outgrow the original name’s meaning and effectiveness
- •Mergers/acquisitions can require a fresh identity that signals new capability
- 42:58 – 50:13
The linguists’ role and sound symbolism: letters as signals (V, B, Z, X)
David explains Lexicon’s linguistic engine: in-house expertise plus a global network to detect meaning, cultural risks, and phonetic effects. He introduces sound symbolism—how specific sounds carry consistent emotional/semantic cues across audiences.
- •Lexicon has employed 250+ linguists and maintains a global evaluation network
- •Linguists screen for negative meanings, cultural/political implications, disasters, slang
- •Sound symbolism: letters/sounds evoke attributes (e.g., V = vibrant, B = reliable)
- •Examples: Azure’s Z as ‘noise,’ BlackBerry’s B as reliability, X as crisp/innovative
- 50:13 – 55:31
Implementation: prototypes, customer research, and selling bold names internally
David describes how implementation is often about internal adoption—helping teams justify bold choices up the chain. Prototypes and research should test imagination and expectations, not mere popularity or ‘fit to concept,’ which biases toward bland descriptiveness.
- •Implementation includes executive-ready rationales and internal presentation support
- •Prototypes (caps, ads, headlines) help leaders visualize market lift
- •Research should measure imagination/expectations, not comfort or popularity
- •Internal dynamics: stop optimizing for the boss’s taste; optimize for the marketplace
- 55:31 – 1:11:02
DIY naming playbook: the diamond exercise, generate 1,000+, and suspend judgment
For teams without Lexicon’s resources, David offers a structured approach: clarify what winning means, what you have/need, and what you must say—then use metaphors to generate many more options than you think you need. He stresses speculation over evaluation and looks for polarization as a strength signal.
- •Diamond exercise: define winning; what you have to win; what you need to win; what you need to say
- •Generate far more than 200 names—aim for 1,000–1,500+ ideas/directions
- •Don’t evaluate early; suspend judgment and speculate on potential
- •Use polarization as evidence of energy; ask ‘what could this name do for us?’
- 1:11:02 – 1:22:43
Domains don’t drive the decision anymore—and closing advice + lightning round
David argues dot-com availability has become secondary—more like an area code—especially as search and AI discovery evolve. He closes by reinforcing the mindset shift (word → experience) and shares personal picks and inspirations in a lightning round, including a favorite name he didn’t create.
- •Dot-com matters far less today; prioritize the right name, then find a workable URL
- •AI search may reduce the importance of traditional SEO and exact-match domains
- •Final tip: focus on behavior/experience and force ‘synchronicity’ via unrelated inputs
- •Lightning round: books, shows, motto, and admiration for the name ‘Dreamworks’
