
REWORK (37signals)
Naming decisions affect brand perception, discoverability, and legal risk, so understanding a pragmatic approach helps founders avoid unnecessary delays. By focusing on simplicity and relevance, product teams can launch faster and create names that resonate with customers, a timely lesson for anyone building new digital tools.
In the Rework episode, Jason Fried and David Heinemeier-Hansen reveal that a product’s name often arrives before the idea fully forms, acting as a creative catalyst. The story of Fizzy—originally Splat, then briefly Boxcar—illustrates how visual metaphors (bug splats, carbonated bubbles, colorful train cars) guide naming, while also serving as an anchor that keeps teams aligned during development. This early‑stage naming ritual signals whether a concept is viable, turning abstract ideas into rallying banners that motivate teams and shape user perception.
The hosts stress that phonetics can outweigh literal relevance. They prefer names that sound fun and pleasant, such as Fizzy, over strictly descriptive terms. Domain availability matters, but they argue it shouldn’t dominate the decision; Basecamp launched without Basecamp.com and later secured the coveted domain. Legal friction also surfaces—David’s experience with the name MERSK (confusing Maersk) and the Haystack trademark dispute show that naming risks exist but are often manageable. Their pragmatic approach balances brand cohesion with flexibility, accepting occasional mismatches when the name feels right.
Overall, the conversation underscores a strategic naming framework for businesses: start with a resonant word, prioritize memorable sound, verify domain feasibility, and assess trademark risk without letting any single factor dominate. Consistent, evocative names like Basecamp, Campfire, Backpack, and Highrise create a harmonious brand symphony, while outliers like Fizzy demonstrate that a playful name can still succeed. For product leaders, the takeaway is clear—invest in naming as a foundational branding exercise, but remain open to evolution, ensuring the name supports both internal morale and external market positioning.
Coming up with a product name doesn’t have to be complicated. In this episode, Jason Fried and David Heinemeier Hansson share when in the development process a name is chosen, how several of their products got their names, and why keeping things simple usually wins. They talk about what's worth considering and what's not worth a second thought.
Key Takeaways
00:10 – How Fizzy got its name and what it was almost called
04:29 – No name ever checks every box
10:25 – When an available domain influences the choice
13:18 – The legal realities
17:26 – What’s behind the name Omarchy (and how do you actually say it?)
20:12 – Good names work by making an easy connection
Links and Resources
Fizzy is a modern spin on kanban. Try it for free at fizzy.do
Record a video question for the podcast
Sign up for a 30-day free trial at Basecamp.com
Books by 37signals
HEY World | HEY
The REWORK podcast
The Rework Podcast on YouTube
The 37signals Dev Blog
37signals on YouTube
@37signals on X
Coming up with a product name doesn’t have to be complicated. In this episode, Jason Fried and David Heinemeier Hansson share when in the development process a name is chosen, how several of their products got their names, and why keeping things simple usually wins. They talk about what's worth considering and what's not worth a second thought.
Key Takeaways
00:10 – How Fizzy got its name and what it was almost called
04:29 – No name ever checks every box
10:25 – When an available domain influences the choice
13:18 – The legal realities
17:26 – What’s behind the name Omarchy (and how do you actually say it?)
20:12 – Good names work by making an easy connection
Links and Resources
Fizzy is a modern spin on kanban. Try it for free at fizzy.do
Comments
Want to join the conversation?
Loading comments...