liveBook · Manning

Platform-as-a-product

As explained in Architecture Modernization: Socio-technical alignment of software, strategy, and structure

Platform-as-a-product is an approach that treats an internal platform as a product with employees as customers and emphasizes usability and customer value.

Platform as a product applies modern product-management practices to internal developer platforms. It treats employees as customers and prioritizes customer value, usability, lower cognitive load, and improved productivity over building a complete platform upfront. section 13.4.1 section 6.1.4

A product-oriented platform approach:

  • Starts with a clear strategy and business case rather than fashion or imitation. section 13.4.1
  • Connects platform investment to productivity, innovation, collaboration, scalability, and reduced cognitive load—not cost reduction alone. section 13.4.1
  • Develops iteratively through feedback, proofs of concept, and minimum viable products, scaling investment as value is validated. section 13.4.1
  • Avoids treating the platform as a large, fully specified, multiyear project whose users are expected to appear after delivery. section 13.4.1 section 6.1.4

NAV’s internal platform

NAV developed its platform on an as-needed basis rather than specifying and delivering it as a three-year project. Treating employees as customers, it sought to make the platform attractive by reducing cognitive load and helping people work more effectively. section 6.1.4

Figure 6.8 NAV’s internal technology platform

Use the internal technology platform figure to inspect the platform context behind the employee-as-customer approach. section 6.1.4

How Architecture Modernization: Socio-technical alignment of software, strategy, and structure covers it

How deep it goes
Explains product-versus-project framing, strategy, business case, feedback, MVPs, and scaling investment after value validation.
Examples
Uses NAV’s as-needed platform development and platform reuse across multiple products as concrete illustrations.
What you can do after
Apply it via iterative platform development: establish value, test proofs of concept and MVPs, gather feedback, and scale validated investment.
How it connects
Connects internal developer platforms with product management, cognitive load, productivity, scalability, and fast flow.

This explainer was generated by Manning's knowledge graph from the text of Architecture Modernization: Socio-technical alignment of software, strategy, and structure. The section links point to the parts of the book it draws on.