Why platforms need champions, not just features

Why do internal platforms with solid tooling and well-designed features still struggle to get adopted? The problem is rarely technical. Across many platform teams, the missing piece is not capability but ownership, trust, and advocacy.

This session explores how internal champions and community shape whether a platform becomes part of everyday engineering work or quietly gets bypassed. It examines how champions emerge, how platform teams can support them without forcing responsibility, and what breaks when platforms are built in isolation from the people meant to use them.

Key takeaways:
• Why features alone rarely lead to platform adoption
• How internal champions influence trust and usage
• Ways to grow platform community without mandates
• What worked, what failed, and lessons learned from experience