Exercise 3: Why the Root Cause Is Escalated Separately, Not Folded In — Possible Solution ==================================================================== WHAT THE TWO PIECES OF INFORMATION ACTUALLY ARE ------------------------------ The data-loss explanation answers "what happened to my specific data" - the folder's changes from the last three weeks are gone. The root-cause finding answers a different question entirely: "why did the organization's own backup process fail to protect that data in the first place." One is about the immediate impact on this user; the other is about a systemic process failure affecting far more than this one folder. WHY FOLDING THEM TOGETHER WOULD BLUR AN IMPORTANT DISTINCTION ------------------------------ If the root cause were quietly mentioned only as part of explaining this one user's own loss, it risks being received as an incidental detail about this ticket, rather than as a standalone finding requiring its own separate response. The dead alert inbox and the silently failed job aren't specific to this user's folder - they represent three weeks of exposure across everything that backup job was supposed to protect, which is a much bigger issue than any single person's individual loss. WHY THIS MIRRORS incident1's OWN DISTINCTION BETWEEN AUDIENCES AND PURPOSES ------------------------------ This chapter already established that data-loss communication borrows directly from `incident1`'s own material on cadence and audience. Part of that material is recognizing that different findings need to reach different audiences for different reasons - the affected user needs to know what happened to their data; whoever owns the backup process needs to know the process itself failed and requires fixing. Combining both into one message addressed to the user risks the process failure never reaching the audience actually positioned to fix it. WHY THIS ALSO PROTECTS AGAINST THE WARN-BOX'S OWN CONCERN ------------------------------ Escalating the root cause as its own explicit finding - rather than a buried aside - is what makes it possible to later say honestly "this has been identified and is being addressed," per this chapter's own warn-box, instead of it quietly disappearing into a single conversation with one affected user and never being acted on organization-wide. WHY THIS WORKS AS AN ANSWER ------------------------------ It distinguishes the two different questions being answered, explains why combining them risks the systemic finding being treated as incidental, and connects the separate escalation to both incident1's own audience-based communication principle and this chapter's own warning about not letting acknowledgment substitute for actual follow- through.