What is Production Readiness?

A readiness review checks several categories. Observability: does the service emit the signals needed to detect and diagnose problems. Alerting: do alerts exist for user affecting conditions, and do they page someone real.

Operability: is there a runbook, a tested rollback path, and a documented owner. Capacity: is expected load known and has the service been tested against it. Dependencies: what does the service require, and what happens when each of those fails.

Nearly every gap they catch is far cheaper to close before launch than after.

• Cheap fixes: adding instrumentation before launch costs hours, adding it mid incident costs an outage.
• Clear ownership: the service has a named owner before it needs one at 3am.
• Known capacity: load limits are measured rather than discovered under real traffic.
• Consistent baseline: every service meets the same operational floor.

Readiness checklists become theater when they are completed for approval rather than for correctness. A service can be marked ready with alerts that page a rotation nobody staffs and a runbook that describes an earlier architecture.

Readiness is also a snapshot. A service that met the criteria at launch drifts as dependencies change, traffic grows, and ownership moves. Without periodic re review, the checklist describes a state that stopped being true some time ago.

Launch approval is a decision about whether to proceed, typically involving product, business, and timing considerations. It answers whether the organization wants this live now.

Production readiness is a technical assessment of whether the service can be operated safely. The two are frequently conflated, and when readiness becomes a gate that business pressure can override, it loses its function. Keeping them separate lets a launch proceed with explicitly accepted operational risk, which is a legitimate decision, rather than pretending the risk was assessed away.