[Playbook] The 30-Minute Triage Framework for Surprise Documentation RequestsA practical decision framework for tech writers who just got pulled into something they didn’t plan for — and now can’t ignoreThe Situation You Didn’t Ask ForYou open Slack. Someone has “looped you in.” That phrase should come with a warning label. There’s a thread. It’s long. No one agrees on what’s happening, but everyone agrees it’s urgent. ‼️ You’ve been added because — you “know the docs.” But, no one’s told you what the outcome of this urgent matter should be probably because no one’s even sure what the problem actually is. But the clock started, and somehow you’re now responsible for making this make sense. Timing is key: the first 30 minutes matter more than anything you’ll do after. This is where you either stabilize the situation or quietly make it worse in ways that will come back to haunt you. What This Playbook Is (And Isn’t)This isn’t a method for solving the entire problem. If it were, it’d be 400 pages long and no one would read it. Instead, this is a stabilization protocol. It’s what you do before you know enough to be clever. The goal isn’t brilliance. The goal is to avoid doing something dumb that creates more work, more confusion, or — my personal favorite — more unnecessary meetings. You’re buying clarity and you’re buying time. You’re reducing the odds that someone says, “Wait, why did we do it that way?” two days from now. Step 1: Figure Out Why This Suddenly MattersEvery “urgent” request has a backstory. Something broke, something’s launching, someone important got nervous, or a deadline snuck up like a raccoon in the night. If you don’t know what triggered the request, you’re guessing. And guessing is how you end up writing a beautifully structured document no one actually needed. Ask yourself what just happened that made this urgent today. Not last week. Not next month. Today. If you can’t answer that in one sentence, you’re not ready to move forward. Step 2: Identify What Goes Wrong If You MissNot all urgency is created equal. Some things are “we’ll look silly.” Others are “we’ll lose customers,” or “legal will start using words like exposure.” You need to know which one you’re dealing with. Who gets hurt if this goes sideways? Is it customers? Revenue? Compliance? Or is it mostly internal confusion and a few bruised egos? This is where you separate the loud from the important. The person typing in all caps isn’t always the one holding the risk. Once you know what’s at stake, you can stop treating everything like a five-alarm fire—or worse, treating an actual fire like a mildly warm candle. |