Internal platforms in practice
summary
Concrete playbook for building an internal engineering platform: start with a thin‑slice, thinnest‑viable platform and validate with value‑stream mapping and developer surveys; measure onboarding time and onboarding rate as leading indicators, and model cost/benefit in a spreadsheet to show payback; use tools like Backstage for a portal but remember Backstage portal ≠ platform, and use DX or AgilityHealth for developer experience dashboards; prefer top‑level funding/sponsorship and white‑glove onboarding / seed‑and‑split team growth to avoid big‑bang failures.
AI-written summary · about
chapters (13)
- 0:00Intro
- 1:52Top Strategic Technology Trends 2023
- 4:58Thoughtworks Technology Radar
- 8:17Critical Success Factors
- 9:09Understand are the real problems teams face on the ground
- 12:19Value Stream Mapping
- 15:06Support and buy-in require a clear articulation of value
- 17:50Inception workshops
- 21:36Build trust through early developer engagement
- 26:06Measuring Success
- 26:28Real-time dashboards
- 29:13Get the funding (and sponsorship) model right
- 32:17Value-based prioritisation
related talks
43mEngineering Platforms Evolved
26mBuilding Internal Platforms to Enhance Developer Experience
32mLessons Learned from 7 Years of Running Developer Platforms
54mInternal Developer Platform and Developers: What Does the Business Pay For?
33mWhy You Should Treat Your Platform as a Product
28mDesigning for Success: UX Principles for Internal Developer Platforms
27mWhy Developer Platforms and a curated Dev Experience are a must have when scaling
44mPlatform Engineering 101: Building Internal Developer Platforms