1. Platform as a Product intermediate

    A platform team builds capabilities that teams do not adopt. What does treating the platform as a product actually require, and how is adoption measured without mandates?

    3 min answer platform-engineeringadoptionproduct-thinkingpaved-road
  2. Platform as a Product intermediate Multiple choice

    An internal deployment platform with six engineers serves 40 product teams. Three versions of its pipeline interface are live - v1 with 22 teams on it - v2 with 15 and v3 with 3. Supporting all three consumes roughly 40% of the platform team's capacity in compatibility work and support, and the team has shipped no new capability for two quarters. Which versioning policy should the platform adopt?

    3 min answer platform-engineeringversioningdeprecationadoption
  3. Platform as a Product intermediate

    An internal platform is used by 11 of 40 product teams. Leadership mandates it - every team must be migrated by the end of next quarter and the alternative paths are closed. The platform team has 6 engineers. What happens over the following two quarters?

    3 min answer platform-engineeringadoptionmandatesqueueing
  4. Platform as a Product intermediate

    An internal platform team's tools are avoided by product teams who build their own. What does treating the platform as a product change?

    2 min answer platform-as-productadoptionself-servicedeveloper-experience
  5. Platform as a Product intermediate

    Teams are avoiding the internal platform and building their own tooling. What do you conclude?

    2 min answer platformadoptionproduct-thinkingpaved-road