Exercise 2: Why Accurate Background Still Makes a Runbook Harder to Follow — Possible Solution ==================================================================== WHAT THE ADDED INFORMATION ACTUALLY IS ------------------------------ The background explanation being added to the runbook is genuinely accurate and genuinely relevant to the underlying problem - it isn't wrong or irrelevant information. Per this chapter, "the 'why' belongs in a linked KB article, not woven into the steps themselves" - the issue isn't the content's own correctness, it's where that content sits relative to the steps someone is trying to execute. WHY CORRECTNESS DOESN'T PREVENT HARM TO USABILITY ------------------------------ A runbook's entire value, per this chapter's own definitions, is answering "what do I do, step by step" as directly as possible. Interspersing accurate but non-actionable background between numbered steps forces the reader to constantly distinguish "is this line something I need to do, or something explaining why I'm doing it" - extra cognitive work that has nothing to do with actually executing the procedure. WHY THIS MATTERS MORE UNDER PRESSURE SPECIFICALLY ------------------------------ This connects directly to the "3am reader" principle Chapter 3 covers next: a stressed, tired reader trying to resolve a live problem quickly needs to move through numbered actions as fast and reliably as possible. Extra prose - even correct, well-intentioned prose - adds friction and increases the chance of skipping or misreading an actual step while scanning past explanatory text. WHY SEPARATING THE TWO SOLVES THE PROBLEM WITHOUT LOSING THE INFORMATION ------------------------------ Per this chapter, the fix isn't deleting the background - it's linking out to a separate KB article that covers the "why" in full, for anyone who wants it, while keeping the runbook itself lean and purely procedural. The information isn't lost; it's just relocated to where a reader who actually wants it can find it, without forcing it on a reader who's mid-incident and just needs to act. WHY THIS WORKS AS AN ANSWER ------------------------------ It acknowledges the added information's own genuine accuracy and relevance, explains why correctness doesn't prevent it from harming a document's usability as a procedure, connects this to the upcoming 3am-reader principle, and explains why linking to a separate KB article resolves the tension without discarding the information.