Exercise 2: Why the Technical and Management Escalations Differ So Much — Possible Solution ==================================================================== WHAT EACH VERSION CONTAINS ------------------------------ The technical (DBA) escalation includes the specific pg_stat_activity finding, a process ID, a query, and what's already been ruled out (version skew, network path) - concrete technical evidence. The management (Eng Director) escalation includes estimated revenue impact and a specific decision to authorize (failing over to the backup region, with its data-staleness tradeoff) - business impact and a decision, no technical evidence at all. WHY THE AUDIENCES NEED DIFFERENT INFORMATION ------------------------------ Per this chapter, "conflating the two wastes the escalation either way - a deeply technical stack trace doesn't help a manager who needs a business-impact summary and a decision to make; a vague 'this is bad' doesn't help an engineer who needs the actual evidence to act on." The DBA team's job is to act on the specific technical evidence directly - they need the pid and the query. The Eng Director's job is to weigh a business tradeoff and authorize an action - they need the impact and the decision, not database internals they aren't positioned to act on. WHY SWAPPING THE CONTENT WOULD FAIL ------------------------------ Sending the DBA team a revenue-impact figure with no technical detail would leave them unable to actually investigate the stuck query. Sending the Eng Director a process ID and query text would require them to either ignore it or ask someone to translate it into a decision they can actually act on - either way, wasting time that a correctly-tailored escalation wouldn't have cost. WHY THIS WORKS AS AN ANSWER ------------------------------ It identifies the specific content difference between the two escalations, and explains why each recipient's own role requires that specific kind of information to act, using the chapter's own reasoning about audience-appropriate content.