Recap. Exceptions are managed — mostly. Operationally, the platform is working. Politically, nobody has noticed in months.
Series In Production · 5
Part of In Production. Browse the series overview for every part.
Outline
- Hook: The platform team’s budget review lands with a note: “justify headcount — no major incidents this year”
- Context: Leadership metrics vs. engineering metrics; benign neglect as success condition (callback to series two finale)
- Paradox: Stay operationally invisible while remaining politically visible
- NZ field note: The restructure where the platform team survived because one slide existed — and what was on it
Sections to Draft
- Two metric sets: what leadership needs vs. what engineers need
- Quarterly narrative reporting (four minutes, three numbers, one risk)
- Anti-patterns: manufacturing drama to stay visible
- Steal-this checklist
Next in the Series
Part 6 — “The Platform Drifts From the Cloud Provider.” Two years of provider change — new services, deprecations, pricing — and foundations that need refresh under live tenants.
One Block · build from here
Draft the one slide your platform would need in a restructure — three metrics, one risk, one tenant quote — before anyone asks for it.