Every platform team eventually faces the same fork: do you mandate standards or make the standard path the path of least resistance? We pick the second one almost every time, and the difference shows up in how much time we spend arguing.
Rules create exceptions
When you enforce a standard with a policy gate and a review board, you create a queue of people who want exceptions, and most of them have a fair point. You spend your week adjudicating instead of building. Rules also age badly: the moment one becomes wrong for a real case, people learn to route around the whole system, and your standardization quietly rots.
A golden path is the easy default
A golden path is the well lit, fully paved way to ship a service: a template that gives you a repo, a pipeline, sensible resource requests, logging, metrics and a deploy already wired up. Nobody is forced onto it. It is simply so much faster than rolling your own that most teams take it without being asked. Standardization becomes a byproduct of convenience.
- A scaffold that generates the repo, CI, Dockerfile and manifests in one command
- Sane defaults baked in: health checks, resource requests, logging and dashboards already present
- An escape hatch, so a team with a genuine special case can step off the path without a fight
The escape hatch is what makes the golden path credible. A paved road with no exits is just a mandate wearing nicer clothes.
When you still need a guardrail
Defaults cover the common case, but a few things genuinely must be enforced: no public S3 buckets, no privileged containers, no secrets in plain text. For those, a small set of admission policies makes sense. The skill is keeping that set small. Enforce the handful of things that are non negotiable for security, and make everything else a default people are happy to accept.
- Hard guardrails: security boundaries you will never grant an exception to
- Golden path defaults: the strong recommendation that is also the fastest option
- Free choice: everything that genuinely does not matter to the platform
The payoff
When the easy path is the right path, compliance stops being a fight. We have watched adoption of a logging standard go from a six month nag to a non event, simply because the scaffold shipped it on by default. People are not resisting your standards. They are resisting friction.