Faster, Better, More! How to start and scale a Digital Platform for your organisation's teams
summary
Defines a digital platform as a product of people, processes and tooling that accelerates other service teams and gives five glass‑tested criteria to decide whether to start one: multi‑year funding, homogeneous workload, a service team as first user, empowered platform team, and support five or more service teams. Recommends discovery + inception, lightweight managed services, pairing with the first user, and tracking deployment lead time and frequency, MTTR and availability while warning against per‑team platform forks and separate support squads.
AI-written summary · about
chapters (21)
- 0:00Intro
- 0:354 fundamental topologies Stream-aligned team Enabling team Complicated Subsystem team Platform team
- 6:26Will the Digital Platform have multi- year funding?
- 7:00Will the Digital Platform serve a homogeneous workload?
- 7:29Will the Digital Platform have a service team to be the first user ?
- 7:41Will the Digital Platform team be empowered to make choices?
- 13:14Choose user journeys Strategy to handle other journeys Tooling choices
- 13:29Maximise using lightweight managed services build your user journeys
- 15:53Failure to collaborate with users
- 16:34Onboard a service team as soon as possible
- 18:16Failure to enable Continuous Delivery & Operability
- 18:38Technology isn't supporting the processes
- 19:08Process isn't supporting the technology
- 21:20Failure to help users adapt to change
- 22:50Pitfalls when scaling a Digital Platform
- 24:10each service team
- 26:11Failure to sustainably scale team structures
- 28:06Split Platform Teams based on user features and capabilities
- 29:56Failure to do one thing well
- 30:41Create a Data Platform team
- 31:20What can you do when you go back to your organisation?
related talks
24mSignificance of Platforms in Product Development
40mInternal platforms in practice
33mWhy You Should Treat Your Platform as a Product
43mEngineering Platforms Evolved
37mPlatform as a Product for modern IT needs
32mLessons Learned from 7 Years of Running Developer Platforms
26mLessons Learned from 7 years of Running Developer Platforms
30mTeam Topologies Applied to Platform Engineering
