Loading
Self-service infrastructure fails when it means 'anything goes.' It succeeds when it means 'here's the shape we've already approved — go build.'
Platform teams tend to arrive at self-service infrastructure from one of two directions: either they're drowning in provisioning tickets and need relief, or a security incident revealed that infrastructure decisions were being made ad hoc, with no consistent review. Both paths lead to the same conclusion — application teams need a way to provision infrastructure without waiting on a human, and platform teams need a way to guarantee what gets provisioned meets their standards.
The mistake is treating self-service as an all-or-nothing proposition: either developers file a ticket for everything, or they get unrestricted access to provision whatever they want. Neither extreme works. The middle path — the one that actually scales — is the golden path: a curated, pre-approved set of templates that represent the shapes of infrastructure your platform team is willing to support.
The uncomfortable part of building golden paths is admitting that not every request should be self-service. Some infrastructure shapes are genuinely novel, or genuinely risky, and deserve a human in the loop. A good self-service system doesn't pretend otherwise — it routes the 80% of requests that match an approved pattern through instant provisioning, and routes the remaining 20% to a real review, without making either path feel like a punishment.
Done well, this changes the platform team's job description. Instead of being a queue that processes tickets, the team becomes the author of the patterns everyone else builds on — which is a far better use of a platform engineer's time than clicking through a cloud console for the fortieth time this month.