Platform as a Product • William Rizzo • GOTO 2024

Platform engineering should focus on accelerating business value delivery rather than just developer productivity

Build platforms with a product mindset - have a roadmap, be accountable, negotiate outcomes with business stakeholders, and treat it as a socio-technical exercise

Don’t try to build a platform for 100% of use cases - aim to satisfy around 20% of critical organizational needs effectively

Include users (developers, data analysts, etc.) in platform development from the start rather than trying to drive adoption afterwards

Design for multiple users/teams from the beginning - like building a multiplayer game, it’s harder to add collaboration later

Focus on self-service capabilities while maintaining appropriate guardrails through golden paths

Every component should be replaceable - avoid vendor/technology lock-in including with Kubernetes

Platforms need strong documentation, clear interfaces (APIs, CLIs, portals), and well-defined ways for users to contribute

Start small and deliver incremental value - avoid “innovation-induced paralysis” by seeking perfection

Measure success through user outcomes and business value rather than just technical metrics

Build trust by following through on commitments and sticking to communicated timelines and roadmaps

Platform capabilities should be optional and composable rather than forcing specific workflows or tools