Platform Adoption
Migrating existing teams onto a platform without a mandate, and reading the adoption curve.
5 to work through
-
intermediate
A platform capability is objectively better than what teams are doing, and adoption is low. How should the gap be diagnosed?
1 min answer -
intermediate
A platform team reports 90% of services are on the platform, and delivery has not improved. What is being measured wrongly?
2 min answer -
advanced
You built an internal developer platform. Eighteen months in, adoption is 30% and the rest of the estate has built its own tooling. What went wrong and what do you do?
2 min answer -
advanced
You introduce service maturity scorecards. Within a month every service scores green and nothing has improved. Why, and what now?
2 min answer -
advanced
Your internal platform has been live for a year. Six of twenty teams use it; the rest built their own pipelines. The CTO proposes mandating it. What is your advice?
2 min answer
5 terms in this topic
Adoption Curve
The proportion of teams actually using a platform capability over time, which is the only honest measure of whether the platform is working.
metricPlatform Adoption
The proportion of eligible teams and workloads actually using the platform, treated as the platform's primary product metric.
practiceService Maturity Scorecard
An automated per-service assessment against the organisation's operational standards, visible to the owning team.
practiceTime to First Success
How long it takes a new team to get something working on the platform - the single best proxy for developer experience and the strongest predictor of…
conceptVoluntary Adoption
Usage of a platform by teams that could have chosen otherwise - which is the only measurement that indicates whether the platform is actually useful,…
Neighbouring topics
Platform Engineering
General material on internal platforms as products with users, adoption and lifecycles.
Internal Developer Platform
The assembled surface teams actually touch, and what belongs behind it.
Paved Road & Golden Path
A supported default route that is easier than the alternatives rather than mandatory.
Self-Service Provisioning
Teams getting infrastructure without a ticket, and the guardrails that make that safe.
Service Templates
Scaffolding new services with observability, CI and security already wired in.
Platform APIs
Treating the platform's own interfaces as contracts with consumers and compatibility rules.
Platform Tenancy
Isolating teams sharing a cluster, account or pipeline fleet, and where isolation must be hard.
Cluster Architecture
How many clusters, split by what, and the blast radius each split buys.
Service Mesh Operations
What a mesh genuinely solves, its failure modes, and the cost of running one.
Container Image Strategy
Base images, layer hygiene, rebuild cadence, and patching a fleet of images.
Developer Environments
Local, remote and ephemeral environments, and the fidelity each can honestly claim.
Inner Loop & Outer Loop
Where an engineer's time actually goes, and which loop a platform investment shortens.
Abstraction Level Choice
How much to hide, and the leak that turns a helpful abstraction into a trap.
Platform SLOs
Committing to reliability for internal consumers who cannot choose another provider.
Platform Funding
Central cost, showback, chargeback, and justifying a team that ships no customer feature.
Platform API Deprecation
Removing something dozens of internal teams depend on, on a timeline that holds.
Guardrails vs Gates
Preventing a class of mistake automatically versus stopping to ask a human.
Platform Telemetry
Instrumenting the platform itself: usage, friction, and where teams leave the paved road.
Platform Team Topologies
Stream-aligned, enabling, complicated-subsystem and platform teams, and their interactions.