Golden Path Adoption
The proportion of teams voluntarily using the supported path, which is the honest measure of whether a platform is solving real problems.
A paved road is a supported, opinionated way of building and running software that is genuinely easier than the alternatives. Its defining property is that adoption is voluntary, and adoption rate is therefore a signal rather than a compliance statistic.
What that signal tells you: low adoption means the road does not fit the problems teams have, not that teams are being difficult. Investigating why is more productive than mandating use, and mandating use destroys the signal permanently.
What a road must contain to be adopted: service templates or generators, deployment pipeline, observability wired in by default, authentication and secrets handling, standard libraries for resilience and messaging, and documentation with a working example. Anything missing is work each team must do itself, which is the reason they go elsewhere.
The complements that make the model coherent: an exception process for teams whose needs genuinely differ, who then accept the operational ownership that comes with leaving the road; and automated policy for the small set of controls that are non-negotiable regardless of path.
The measures worth tracking alongside adoption: time from a new team starting to first production deployment, and satisfaction — because a road adopted under pressure and resented is heading back toward being routed around.