Tales from the Platform Adoption Mines
summary
Platform teams focus on building but miss adoption: start with shiny pebbles (discoverable docs, examples and onboarding that set norms), formalise decisions as stone tablets (ADR/policy and owners), then enforce a make phase where wrong choices break or get intercepted — e.g., blocking Helm charts stored in LaunchDarkly flags and replacing them with a “don’t do that” remediation link. Measure success with concrete outcomes (SLOs, tightened public SLAs, audit posture, cost), not percent adoption, and plan for stragglers and advance disappointment.
AI-written summary · about
chapters (10)
- 0:00SRE to platform adoption
- 3:05When not to build yet
- 6:12Cultural norms before platforms
- 9:59Policy and tooling spectrum
- 13:10Guardrails for developers
- 16:06Defining platform success
- 20:21Handling stragglers
- 22:29Selling platforms like SaaS
- 24:17Myths derailing adoption
- 27:47Key takeaways
related talks
32mAre You Ready for Platform Adoption, or Are You Setting Yourself up for Failure?
22mThe challenges of Platform teams
25mCommon platform team mistakes and how to avoid them
44mGetting out of the Starting Blocks
15mKeynote Engineering Success The Blueprint for Effective Platform Adoption
27mPlatform Adoption Strategies: Critical Roles When Investing...
43mPlatform as a Product: Mindset, milestones, metrics
32mHow Might You Platform: Avoiding Traps Before It's Too Late