Culture and shared ownership
You build it, you run it — blameless learning, on-call, and product ownership of production.
DevOps culture is shared responsibility for user outcomes in production, not heroics by a separate firefighting caste.
You build it, you run it
Teams that ship features own alerts, dashboards, and runbooks for those services — with platform support, not abandonment. Ownership without paved roads burns people out; paved roads without ownership recreate the wall.
Blameless, not consequence-free
Incidents produce learning: timelines, contributing factors, follow-ups with owners and dates. Blameless means we fix systems and processes. It does not mean ignoring negligence or skipping follow-through.
On-call as design feedback
Painful on-call is a product signal. Reduce noise, invest in SLIs, improve rollouts. Paying people to endure bad alert hygiene is not “strong ownership.”
Collaboration habits
Joint design for operability (probes, metrics, migration plans), shared definitions of done (includes observability and rollback), and respectful handoffs when platform and product boundaries are real.
Anti-patterns
- “DevOps team” as a ticket sink for every YAML change
- Devs with prod access and no training or guardrails
- Ops measured only on uptime, devs only on feature count
Culture shows up in who gets paged and who gets to change the system afterward.