When incidents hit, the true cost isn’t the bug — it’s that only one person knows how to fix it. That hidden single‑point-of-knowledge forces all‑hands nights, slows decisions, and taxes customers and leadership. This episode introduces the 30‑Minute Runbook Test: a strict, safety-first protocol that verifies whether any critical recovery can be executed by a competent stand‑in within thirty minutes using only the runbook and minimal, pre‑approved access. Mirko opens with a compact vignette where a single expert enabled a weekend of firefighting, then walks business and IT perspectives on bus‑factor risk. You’ll get a copy‑paste test script, exact phrasing to recruit a stand‑in and a sponsor, three conservative safety rules (non‑prod or scrubbed data, read‑aloud acceptance, one‑step rollback), and a 7‑day pilot: pick three critical runbooks, run the test, record time‑to‑complete and missed assumptions, then prioritize fixable gaps. Practical, low‑friction, and immediately adoptable: make recoveries transferable before they become crises. CTA: run the 7‑day pilot this week and leave a review if it reduced night pages.

Become a supporter of this podcast: https://www.spreaker.com/podcast/business-it-it-business--6867401/support.

To continue the conversation, follow Mirko Peters on LinkedIn, where more insights and real-world examples are shared from both business and IT perspectives.