Exercise 1: Why the Crashing Service Needed All Three Document Types — Possible Solution ==================================================================== WHAT EACH DOCUMENT ACTUALLY DID FOR THIS PROBLEM ------------------------------ Per this chapter's worked example, the ticket recorded "what happened and how it was resolved" the first time - a historical record of one specific instance. The runbook, created once the pattern recurred a third time, captured "the exact steps to mitigate and restart the service safely" - a reusable procedure for the next person facing the same symptom. The KB article separately explained "why the service crashes under load in the first place - the underlying architectural cause." WHY NO SINGLE ONE OF THESE COULD HAVE DONE ALL THREE JOBS ------------------------------ The ticket only makes sense as a record of one occurrence - trying to make it double as a general procedure would mean generalizing from a single case, which may not hold up the second or third time the problem shows different symptoms. The runbook is deliberately procedural and lean, per this chapter's own reasoning about the "3am reader" - stuffing in the full architectural explanation would slow down exactly the person trying to follow the steps quickly during a live incident. The KB article is deliberately not a step-by-step guide - someone just wanting to fix the crash right now doesn't want to wade through architectural background first. WHY ONE "THOROUGH" DOCUMENT WOULD HAVE SERVED WORSE, NOT BETTER ------------------------------ Per this chapter's own warn-box, "cramming explanation, procedure, and incident-specific detail into a single document usually means it serves none of the three purposes well." A single combined document would force every reader - whoever just wants the quick fix, whoever wants to understand the root cause, whoever's auditing what happened in a specific past incident - to wade through the two-thirds of the content that isn't relevant to their actual need. WHY THIS DEMONSTRATES CHAPTER 2's OWN CENTRAL DISTINCTION ------------------------------ The worked example isn't just illustrating that three documents can exist for one problem - it's showing that each document answers a genuinely different question (what happened this time? what do I do? why does this happen?) that a single audience, at a single moment, actually needs answered separately. WHY THIS WORKS AS AN ANSWER ------------------------------ It states what each of the three documents specifically accomplished for this one recurring problem, explains why no single document could have served all three purposes without compromising each one, and connects this back to the chapter's own warning against combining them.