dragoon0x Naming Strategy
Product Naming Approaches
| Type | Example | Pros | Cons |
|---|---|---|---|
| Descriptive | Microsoft Teams | Clear function | Generic |
| Invented | Spotify | Unique, ownable | Needs marketing |
| Metaphor | Slack | Memorable | Can confuse |
| Founder | Bloomberg | Personal, trustworthy | Limited scalability |
| Acronym | IBM | Short | Meaningless initially |
Feature Naming Rules
- Descriptive over clever (users need to find it, not enjoy the pun)
- Consistent vocabulary (don't call it 'workspace' in one place and 'project' in another)
- Verb-first for actions ('Create project' not 'Project creation')
- Avoid internal jargon (what engineers call it isn't what users should see)
- Test with users: 'What would you expect this to do?'
Linguistic Testing
- Does it translate well? (no accidental meanings in other languages)
- Is it easy to pronounce? (for word-of-mouth growth)
- Is it searchable? (unique enough to rank in Google)
- Is the domain available? (.com or relevant TLD)
- Is the social handle available?