Chapter 2. Platform as a Product
The terms platform and internal developer platform (IDP) can describe either a single off-the-shelf platform as a service (PaaS) product or a bespoke collection of tools curated by an organization for its internal use. These definitions can reinforce the idea that platforms are infrastructure projects with a beginning, a delivery milestone, and a vague hope that developers will use what is built or bought. However, this approach rarely delivers sustained value.
More Than Just a Stack of Tools
A platform is not just a collection of tools, templates, or workflows. It is an evolving system that must continuously respond to user needs. To achieve this, it must be treated not as a project but as a product.
Adopting a product mindset starts with continually evaluating the business context to manage “build versus buy” decisions. Contextual factors such as scale, compliance requirements, or the diversity of the workforce skill base and technology stacks often require organizations to opt out of an off-the-shelf solution and instead invest in a set of integrated capabilities designed for its specific needs. The resulting platform has users, and it requires design, iteration, feedback, and a clear value proposition. Without a mindset that takes all this into account, platform teams risk becoming internal service providers chasing feature requests rather than strategic enablers focused on outcomes.
This chapter explores the foundational shift toward product ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access