Back to Library
Library rep  ·  Friday, May 15

David Placek on naming: descriptive is not safe, it's how you lose.

Kettlebell Coach
Read first. Then rep it.
Ready to apply this idea?
Five application reps based on what David Placek discussed.
Practice this insight
Based on Lenny’s
Newsletter · David Placek · Sep 2, 2025

How to find the perfect name

Start from the original episode or newsletter, then use the ideas below in the reps.

Key ideas to remember

  1. 01 Descriptive feels safe; it's actually the riskiest move. 'Microsoft Cloud Services' was rejected as 'a dumb idea' before Azure shipped — the original name won.
  2. 02 If a stakeholder defends a name with 'people will know what it does', that's a warning sign, not validation. A thousand competitors will sound the same.
  3. 03 Sound matters. Read your candidate names out loud. The phonetics of Azure aren't accidental.
  4. 04 Stop running group naming brainstorms hoping a winner emerges. The right name is a strategic call, not a vote.
3-minute summary

David Placek has spent 40+ years naming products at Lexicon Branding — Swiffer, Sonos, BlackBerry, Azure, Pentium, Vercel, Windsurf, Impossible Foods. His central argument is that most teams treat naming as a low-stakes administrative task — delegated to junior staff or tackled in group brainstorming sessions — and the cost is enormous. The right name is a competitive advantage no one can take away from you; the safe-feeling descriptive name leaves you indistinguishable in a crowded market.

His three-pillar framework: (1) Build for trust — the marketplace moves so fast now that a name must generate momentum early or fail. (2) Communicate an original idea — never describe. Anyone can describe what a company does; that name will have a thousand similar names swirling around it. Google, Pentium, and Navan beat Infoseek-style naming because they signal a new idea. (3) Be accessible — the brain doesn't remember complexity, so familiar components and clean sound patterns matter (Azure's 'z' creates a strong signal; '-zure' lands like 'sure').

For PMs naming features and surfaces, the trap is the same as for founders naming companies: descriptive names feel responsible because they're easy to defend in a stakeholder meeting. Placek's argument is that the responsibility is misallocated — descriptive names underperform precisely because they're indistinguishable, and indistinguishable products lose the discovery battle. The PM-level translation: when you name your next launch, treat the name as a strategic decision, not a documentation decision.

Kettlebell Coach
This is where the reps count.
Practice the insight now
Turn the operator summary into five product decisions.
Practice this insight