Paved Roads
also called Golden Path
A supported, opinionated default path that is the easiest way to do the right thing — governance by convenience rather than by mandate.
Definition
A paved road is a fully supported way to build, deploy and operate a service: templates, pipelines, libraries, infrastructure modules, and observability wired in. Teams may leave the road, at their own cost.
Why it beats mandates
A mandate creates an adversarial relationship, produces waivers and shadow infrastructure, and destroys the signal about whether the standard is any good.
A paved road is chosen because it is genuinely easier. Compliance, security and operational best practice arrive as side effects of the convenient option, which is the only form of governance that survives deadline pressure.
It also keeps the platform honest: if teams are leaving the road, that is a product finding about the road, not a discipline problem with the teams.
What belongs on it
- A service template producing a deployable, observable service in minutes.
- A pipeline with build, test, security scanning, deployment and rollback.
- Infrastructure modules that are correctly sized, tagged, encrypted and networked by default.
- Observability wired in — structured logging with correlation IDs, metrics, tracing, dashboards and default alerts, with no per-team work.
- Standard libraries for authentication, resilience and configuration.
- Documentation and a support path.
The rule that makes it work
Leaving the road must be allowed, and must cost something. Teams that go off-road own the consequences: their own pipeline, their own monitoring, their own on-call tooling, their own compliance evidence.
That is not a punishment; it is the honest cost, and stating it converts an argument about standards into a straightforward trade the team can make for themselves.
Track the exceptions. A pattern of teams leaving the road for the same reason is the road's roadmap.
What makes it fail
- A road that constrains more than it enables, which teams correctly abandon.
- No support behind it, so users are stuck on their own.
- Never updated, so it encodes decisions from three years ago.
- Mandated, which destroys the adoption signal and the incentive to improve it.
- Too narrow, covering only the simplest case, so anything real requires leaving it.
The measure
Voluntary adoption, plus the outcomes of teams on the road versus off it — lead time, incident rate, time to first deploy. If those are not better on the road, the road is not doing its job.
Interview question
"How does a paved road achieve governance outcomes without a mandate, and what makes it fail?"