Building Thriving Communities in Platform Engineering: Collaboration, Innovation, and Growth
Panelat Platform Engineering Day 2025 - Europe · on Tuesday, 2025-04-01· at 16:55· Level 1 | Hall Entrance N10 | Room F·
summary
Panelists report concrete practices: start by interviewing everyone and running hackathons, office hours and inner-source to involve real developers (aim for one developer per department contributing regularly); treat documentation as part of your platform and track PRs, DORA metrics, uptime and feature velocity for trends; avoid top‑down mandates that exclude legacy teams (one healthcare rollout slips from 18 to 24 months when ops aren’t included); assign ownership of feedback and translate metrics into C‑level cost/value conversations.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:46Panelist introductions
- 2:27Why community matters
- 3:34Build versus buy
- 5:21Roles for success
- 9:18Organizational structures
- 12:13Starting platform team
- 14:19Feedback to improvements
- 17:07Measuring engagement
- 18:55Team Topologies distinctions
- 21:44Reducing friction
- 23:51Actionable steps
- 27:46Closing remarks
related talks
59mLessons from Running Developer Platforms & Communities
45mPanel on Building Communities
40mBuilding Developer Platforms, Birds of Feather
49mCommunities Over Code: How to Build a Successful Project
15mBuilding Tech Communities: Lessons from a Decade of Experience
30mBuilding an Enterprise DevOps Community
39mCreating an Inclusive Community
30mBuilding Developer Documentation with a Fully Remote Team and Community