How Ericsson Scaled Developer Experience With Backstage
summary
Ericsson describes standing up a Backstage-based Internal Developer Portal for ~1,260 engineers and scaling to over 4,000 visits per week by automating cataloging, building plugins and measuring usage. Key moves: build a small DX team, prioritize developer feedback (NPS from -22 to -2), pivot to fix surprise pain points, and stop old tools/bookmarks to drive migration. The booking-environments plugin launches as the highest-used plugin on day one, and usage metrics plus observation sessions steer the roadmap.
AI-written summary · about
chapters (8)
- 0:00Project introduction
- 3:08Initiating the DX journey
- 6:16Addressing feedback
- 9:42Removing legacy processes
- 12:46Integrating golden paths
- 15:54Measuring success
- 18:36Engaging developers
- 20:31Sentiment and future outlook
related talks
06mScaling Enterprise Platform Engineering with Backstage
35mImproving Developer Experience with Backstage
28mIDPs For The Rest of Us: Maximizing Impact When You Aren't a Tech Giant
23mOur Journey To a Unified Developer Experience With Backstage
25mLet’s Go Backstage: End to End IDP Tips & Tricks for Platform Engineers
42mNavigating Backstage: A Year in Developer Life
29mHow We Made Backstage Improve Developer Efficiency of 1000+ En...
28mHow Did Backstage Make 500+ Developers Happy in a Highly Regulated Enterprise