https://latini.dev/tags/runbooks/Recent content in Runbooks on F. Latini - IT EngineerHugoenThu, 24 Sep 2026 08:00:00 +0000https://latini.dev/posts/you-build-it-you-run-it-with-what/Thu, 24 Sep 2026 08:00:00 +0000https://latini.dev/posts/you-build-it-you-run-it-with-what/<p><strong>TL;DR</strong> - &ldquo;You build it, you run it&rdquo; is usually announced rather than equipped. Teams get a pager, a link to a wiki and a vague expectation, and the first time something hard breaks at 2am they call the platform team, because the platform team is the only group that understands the substrate. Help once and you are the escalation path forever. The fix is to treat operability the way you already treat deployment: as a paved-road default. Every service created on the road should arrive with a rota, alerts on the user journey, a dashboard, production access that works and a generated runbook that is true on day one. Split the runbook into the generic half the platform owns and generates, and a short specific half the team owns and drills. Offer enablement as a time-boxed engagement with an exit date, not as a standing rescue service. And make every rescue leave something behind in the kit, so the second call for the same problem never has to happen.</p>