Exercise 2: Why Embedded Branches Slow Down Readers Who Never Need Them — Possible Solution ==================================================================== WHAT EMBEDDING A BRANCH ACTUALLY DOES TO THE MAIN PATH ------------------------------ A conditional phrase like "if this doesn't work, you could try either A or B depending on..." inserted directly into a numbered step forces every reader following that step to read and mentally process the entire conditional - the "if," both alternatives, and the condition distinguishing them - even if their own situation never triggers it. The extra text has to be read and parsed regardless of whether it ends up being relevant. WHY THIS AFFECTS THE MAJORITY WHO DON'T NEED IT, NOT JUST THE MINORITY WHO DO ------------------------------ Per this chapter, "the vast majority who won't need the fallback at all" still pay the reading and comprehension cost of the branch being present, even though they'll never act on it. The cost isn't distributed only to the readers who hit the edge case - it's paid by every single reader who passes through that step, on every use of the document. WHY THIS IS ESPECIALLY COSTLY FOR THE 3AM READER SPECIFICALLY ------------------------------ A stressed, fatigued reader has to work harder to disentangle "this is the action I take" from "this is a conditional branch I can ignore right now" - exactly the kind of extra cognitive load this chapter argues degrades comprehension and increases the chance of skipped or misread steps. A branch embedded in the primary path adds friction at precisely the moment friction is least affordable. WHY SEPARATING FALLBACKS SOLVES THIS WITHOUT LOSING THEM ------------------------------ Per this chapter, "keep troubleshooting or fallback steps clearly separated out, not interleaved with the steps most readers will actually follow." The fallback information isn't deleted - it's moved to its own clearly marked section, so the main path stays a single, uninterrupted sequence of actions for the common case, while the information for the edge case remains fully available to whoever actually needs it. WHY THIS WORKS AS AN ANSWER ------------------------------ It explains what reading an embedded branch actually requires of every reader regardless of relevance, explains why this cost falls on the majority rather than just the minority who need the fallback, and explains why separating fallbacks into their own section removes that cost from the main path without discarding the information.