An Internal Developer Platform is not a wiki of best practices, it is the paved road that makes the right way the easy way. Treat it as a product whose users are your own engineers, and adoption becomes a pull, not a mandate.
Paved roads beat guardrails
Guardrails tell people what they cannot do. Paved roads make the good path so smooth that leaving it feels like extra work. Golden paths should cover the 80% cleanly and get out of the way for the rest.
Self-service: create a service, get a repo, pipeline, and prod path in minutes
Golden paths: opinionated templates that bake in security and observability
Sensible defaults: mTLS, SLOs, dashboards, and alerts on day one
An escape hatch: teams can step off the road when they truly need to
A golden path is a template plus a promise
A scaffolding template (Backstage, or your own) turns a new service from a week of setup into a form submission:
apiVersion: scaffolder.backstage.io/v1beta3
kind: Template
metadata:
name: go-service
title: Go microservice (paved road)
spec:
parameters:
- title: Service details
properties:
name: { type: string }
team: { type: string }
steps:
- id: scaffold
action: fetch:template
input: { url: ./skeleton } # Dockerfile, CI, Helm, SLOs, dashboards
- id: publish
action: publish:github
- id: register
action: catalog:registerMeasure it like a product
Time-to-first-deploy for a brand-new service
Adoption: what fraction of services are on the golden path
Change-failure rate and lead time (the DORA metrics)
Developer satisfaction, ask, do not assume
A platform succeeds when engineers choose it because it is faster, not because a policy forced them onto it.
Build the platform your engineers would pick on a good day. Paved roads, real self-service, and an honest escape hatch turn platform engineering from a gatekeeper into an accelerator.
