Platform as a Product
Adoption earned rather than mandated, with an owner and a roadmap.
5 to work through
-
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 -
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 -
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 -
intermediate
Teams are avoiding the internal platform and building their own tooling. What do you conclude?
2 min answer -
advanced
An internal platform team's tooling is being bypassed by product teams building their own. What is the diagnosis, and what changes?
2 min answer
3 terms in this topic
Platform as a Product
Running an internal platform with users, a roadmap and adoption metrics — because a platform that must be mandated is one that has not earned its use.
practicePlatform as a Product
Running an internal platform with the disciplines of a product — voluntary adoption, user research, documentation and a roadmap — rather than as a ma…
conceptPlatform Bypass Signal
Teams routing around an internal platform read as a product signal about the platform's fitness, not as a compliance failure to be solved with a mandate.
Neighbouring topics
Business Architecture
General material on the business side of architecture.
Business Capabilities
What a business does, stated stably and independent of implementation.
Capability Mapping
Overlaying systems onto capabilities to expose duplication and gaps.
Business Processes
How work actually flows, including the handoffs nobody documented.
Value Streams
End-to-end delivery of an outcome, and where the waiting happens.
Domain Boundaries
Where the language of the business changes, and services should too.
Stakeholder Analysis
Who is affected, what they need, and who can block you late.
Product Thinking
Treating platforms and services as products with users and a lifecycle.
Business KPIs
The numbers a design is ultimately judged against.
Regulatory Constraints
Non-negotiable requirements that remove design options entirely.
Organisational Constraints
Team structure, skills and budget cycles as architectural inputs.
Time to Market
The constraint that dominates most products, and how to trade against it.
Build vs Buy
Differentiation versus table stakes, priced over five years.
Business Cases
Expressing an architecture proposal in the currency that gets funded.
Operating Models
How delivery, platform and governance functions fit together.
Team Topologies
Stream-aligned, platform, enabling and complicated-subsystem teams.
Outcome Measurement
Knowing whether the thing you built achieved what it promised.
Portfolio Prioritisation
Choosing between investments with incomparable benefits.
Business Continuity
What the business does while the system is unavailable.