A Front...
summary
Large orgs report concrete wins and pitfalls: one portal reaches 60% daily adoption and 2.5k monthly users after starting with search, catalog and a simple MVP; another counts 36 internal plugins contributed by 120 people. Teams prioritize scaffolding, search, ownership metadata and metrics, avoid the “sugar‑rush” of flashy plugins, and start by solving one high‑impact workflow (e.g., rapid discovery or latest deployment visibility). Practical tips: prefer small, measurable wins, enable non‑TypeScript contributors via JSON/Go, and treat platform teams as partners.
AI-written summary · about
chapters (9)
- 0:00Backstage adoption panel intro
- 3:13Panelists’ motivations
- 7:44Rollout strategies at scale
- 12:18Evaluating Backstage plugins
- 18:41Data plugins and use cases
- 21:10Legacy IDPs to Backstage
- 24:45Enabling platform contributions
- 27:12Expert advice for adoption
- 30:01Closing remarks
related talks
49mA Front Row Seat to Backstage Adoption
24mBottom up org change and evolution
38mEmbracing Developer Portals in Software Development
22mUnlocking Backstage’s Potential: Driving Adoption and Maturity With Your Develope...
28mIDPs For The Rest of Us: Maximizing Impact When You Aren't a Tech Giant
31mBackstage Adoption Deep Dive - Navigating the Pitfalls
27mLessons from a Year with Backstage: What Worked, What Didn’t...
15mEstablishing Platform Teams to Utilize the Economy of Scale