“Platform as a Product” is a term that has been around for nearly a decade, and teams have been trying to build effective internal platforms for even longer. Platform Engineering is also getting some buzz - Gartner predicts that by 2026, 80% of large software engineering organizations will establish platform engineering teams as internal providers of reusable services. But with this buzz, comes the reality - this is a costly investment if you aren’t getting the promised results. Accelerate’s State of DevOps report shows limited gains from organisations using an internal developer platform and an 8% decrease in throughput among those using a platform compared to those who do not. My 5+ years in Platform Engineering have taught me that one big reason why is not treating your Platform as a Product

But platform engineering and product thinking aren't always been the happy bedfellows that I hope for.

Moving from engineering-led delivery to treating your Platform as a Product is hard. It can feel like you’re crawling through the trenches. But the rewards are also awesome. In this talk, I’ll share more than just what the Platform Engineering and Platform as a Product buzzwords mean, but also how you can get out of the trenches and onto the green fields of happy developers without making the same mistakes I have.