A shared language for drop disputes
Drop disputes stall when each function brings a different clock and a different success definition. One side counts HTTP 500s; another counts ticket volume; another counts circuit alarms.
Write a one-page incident vocabulary before the next outage: what counts as a session end, what counts as a recoverable pause, and which clocks are authoritative. That page does more than another dashboard tile.
External attribution briefs work best when that vocabulary already exists. Without it, even careful analysis becomes another opinion in the room.