12 Names for the Same Thing: Why Developer Experience Can't Grow Without a Common Language

Developer Experience, Developer Productivity, Platform Engineering, Engineering Thrive, Enablement, Developer Tools, Engineering Solutions, Productivity & Happiness - 12 different names across 17 top tech companies for what is essentially the same discipline. This fragmentation isn't just confusing - it's actively slowing down DX as a field. When Google calls it "Engineering Productivity," Microsoft calls it "Engineering Thrive," and LinkedIn calls it "Productivity & Happiness," developers can't find each other's work, share practices, or even recognize they're solving the same problems. In this lightning talk, I'll show: - The naming landscape: 12 titles for one function (data from GetDX research across Google, Microsoft, Spotify, Uber, Stripe, and others) - Why this matters: fragmentation prevents knowledge sharing and makes DX invisible as a career path - The DX vs Productivity divide: "experience" is the developer's word, "productivity" is the manager's word - and this difference shapes what gets measured and what gets fixed - A case for convergence: DX needs a brand as recognizable as DevOps or UX