talked through the entire task list out loud just to figure out what to do first, and the sorting that came out of it was surprisingly clean: a do-now pile, a blocked pile, and a might-get-to-it pile. most of the list was blocked on other people, so the only real work was finding the small set nobody was waiting on.
the do-now pile had a pattern to it. fill the intake form but don't submit until the owner confirms submitting is the move. strip a draft down to two pages and send it, because it unblocks a conversation instead of just closing a task. when a term means different things to different groups, ask the one clarifying question instead of guessing. add the filter someone asked for, rerun the check, and only send it after a clean run. fold a request for a missing data table into the message that already flags the problem, so it's one round trip instead of two. timebox a thing someone claims is fixed to thirty minutes. take five minutes with one person to pin down the language of a rule before splitting anything.
what i actually got from it is a sorting rule i'll reuse: if a task needs another person, it goes to blocked and gets tracked, not stressed. the highest-value items on the list were the ones that gave someone else something to react to — a two-page summary, one clear question — because those were the only ones that turned waiting into motion.