Recap. The platform refreshed without a headline incident. Then the person who held half the tribal knowledge gives notice — ties back to series two’s fractional team and bus-factor themes.
Series In Production · 7
Part of In Production. Browse the series overview for every part.
Outline
- Hook: Two weeks’ notice from the one human who understands the identity integration
- Context: Documentation vs. archaeology — what platform docs must actually contain
- Handover: The two-week handover that wasn’t
- NZ field note: What you find when you map every “ask Dave” path in the organisation
Sections to Draft
- Runbook inventory vs. exception register vs. decision document
- Minimum documentation for a 2–4 FTE platform (practical, not aspirational)
- Pairing and rotation before you need them
- Steal-this checklist
Next in the Series
Part 8 — “Platform vs. the Hyperscaler’s Native Answer.” The provider ships a managed service that does 70% of what your team built — and tenants ask why they cannot use it.
One Block · build from here
Ask your team: what breaks if the most knowledgeable person is unavailable for a fortnight — and write down the first three answers as tickets, not assumptions.