Backstage Adoption Deep Dive - Navigating the Pitfalls
summary
Backstage setup happens day one with a secure URL and sign‑in, week one builds a high‑impact automation to eliminate a common monthly ticket, month one adds ~5 plugins, first catalog entries and a scorecard; team makeup is one backend, one frontend (or two full‑stack), one devops and a part‑time PM; aim for ~25% active users in 0–3 months, 25–50% by 3–6 months and ~70–75% after 9 months; prioritize developer daily utility, seed adoption with automation first wins and measure catalog readiness.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 1:47What Backstage adoption means
- 3:37Mindset for adoption
- 8:56Phases of rollout
- 12:30Building the flywheel
- 17:06Golden path to adoption
- 25:13Q&A
related talks
32mIs Backstage for me?
49mA Front Row Seat to Backstage Adoption
36m4 Common Pitfalls when Adopting Backstage
25mHow to Adopt Backstage: Lessons from 20 Adopter Interviews
22mUnlocking Backstage’s Potential: Driving Adoption and Maturity With Your Develope...
22mGetting Started with Backstage in 2023
13mKeynote: 4 Common Pitfalls to Avoid When Onboarding Backstage
27mLessons from a Year with Backstage: What Worked, What Didn’t...