It's 8:50, the first meeting is at 10:00, and the inbox holds forty-some messages, several of which claim urgency in the subject line. The question "what do I answer first?" gets decided, for most people, by scroll position: top down, newest first, which hands the queue to whoever wrote most recently. Triage professionals (the medical kind) would recognize this as treating patients in arrival order, and they stopped doing that a century ago.
The sequence
1. Unblock first. Scan for replies where someone is waiting on you to proceed: the approval holding a launch, the answer your colleague needs to continue, the yes/no gating someone's afternoon. These multiply: thirty seconds from you releases hours of someone else's progress, and your delay compounds through their day into everyone's. Dependency outranks everything, including volume of exclamation marks.
2. Deadlines inside 48 hours. Anything dated and close: the RSVP, the filing, the offer expiring. Dated items are checkable facts, unlike urgency claims, which are free to type.
3. Your VIPs. The named shortlist (manager, key clients, the live deal) gets read even when nothing looks urgent, because their non-urgent is your important.
4. Two-minute closes. Quick confirmations and short answers, cleared in a batch: each one closes a loop cheaply, and the psychic weight drops faster than the message count. This is the two-minute rule in its natural habitat.
5. Everything else becomes scheduled work. Real tasks extract to the list with dates; the rest archives. Answering it all right now was never the goal; deciding it all was.
Why shouldn't the urgent-sounding ones go first?
Because stated urgency and actual stakes correlate weakly: the all-caps subject is often a newsletter tactic, while the quiet two-line email holds the resignation. Recency is an even worse signal, and it's the default. The sequence above substitutes checkable structure (dependency, dates, named senders) for volume and recency; the deeper version of that argument is in prioritising when everything is urgent.
Triage as a standing condition
The hour version of this exists because the inbox arrived unsorted. Pidgy's entire function is making that the machine's problem: on Gmail and Outlook it surfaces unblockers and dated items, holds the VIP layer, drafts the two-minute replies for one-click approval, and files the rest, so the 8:50 question isn't "what first?" but "approve these?". The hour becomes the ten minutes before the coffee's cold.
