Workload triage: the four questions before you say yes

Workload triage is the four-question checklist you run before you say yes to another request. It is a deliberate pause that prevents the random ping from becoming your week. If the ask lands with no clue about urgency, impact, success criteria, or updates, then you are about to trade focus for a mystery project that might never count toward your goals.

The person handing you the work is trying to keep the program moving without going back to the same room three more times. They want the checkbox clicked, the blocker cleared, the deadline hit, and the stakeholder quieted. Your clarifying questions are not about being difficult; they make it possible for them to hand you something that actually lands.

Good looks like a 90-second exchange where everyone hears words like “deadline,” “who needs to approve,” “delivery format,” and “next sync” in the same breath. It looks like you walk away with a shared understanding of whether it is a sprint, a quick bug fix, or a side quest that can wait until next week. Good means you know what to deliver, when it is due, and whose inbox will light up if you miss it.

Bad looks like you nod and type “sure” while the requester keeps talking because they never pause to describe the deliverable. A bad interaction ends when you walk away with a vague “we need this soon” and a calendar full of meetings you now feel obligated to accept. The result is the usual overload: the inbox that should have been one helpful summary and is instead four follow-ups plus uncertainty.

Yeah, running this checklist every time an ask drops feels a little like a scripted corporate ritual, but I’ve seen it save weeks of wheel-spinning. I’ve run these questions in back-to-back standups at Stylitics, and we all walked out with actual plans instead of nods.

The four triage questions

Workload prioritization is not about being the busiest teammate. It is about choosing the fight that actually moves the work forward. Ask these questions in order, ideally before you acknowledge availability. They are not optional; they are the difference between work that is visible and work that vanishes into a dark corner.

Your manager’s Slack is already drowning in half-baked pings from five different teams, so punch back with these to reclaim your bandwidth.

1. What is the urgency? Ask for a deadline, the event it ties to, or what happens if it slips. Yes, this feels like a scripted onboarding line, but ask it anyway. Without it you are racing to unknown brakes. The urgency answer also reveals whether this is a “fires first” or “wait till next cycle” request.

2. What is the impact? The person on the other side of the table is trying to keep the stakeholder content, but that does not mean the work matters equally. Get a brief answer: what changes if this lands versus if you delay? A quick “keeps the partner from escalating” versus “nice to have for the research doc” tells you whether to reshuffle priorities or slot it into the background.

3. What does done actually look like? Most overload is just an unclear definition of done hiding in plain sight. When I was at Stylitics I watched a stakeholder ask for “some charts” and leave, and the team spiraled for a week trying to guess the format. Ask for wireframe examples, the format they will share, the data refresh, how they’ll know you are finished. If the answer is “just make it” you do not say yes. Instead, you say, “Can we sketch the format together so I know when I hit the mark?”

4. Who needs updates and how often? Someone thinks “copy me” is a mode of communication. You are not a notification service. Clarify the rhythm: Slack for blockers, weekly summary for project owners, no updates unless something deviates. This saves you from writing ten unnecessary emails and from the sudden expectation that you report in twice a day. We all end up as the default update machine if we don’t call this out early.

The ritual is simple enough to finish in two minutes. The real trick is saying no the first few times you discover the ask is vague. You do not have to decline the work forever. You just have to insist you cannot take it until outcome, urgency, and delivery are crystal.

Triage checklist

Use this mini form while you talk or as soon as you hang up. It is the checklist that saves you from giving into every unclear demand. Keep a note open, fill it in, and send a quick recap when you accept the work.

After the call, paste your answers into the shared doc or Slack thread so everyone is aligned. If you are still unsure, respond with a short script: “I can take this once we confirm [insert missing info]. Until then it sits on pause.” That script is not snark; it is triage. It makes the bureaucracy work for you instead of against you.

The deadpan observation: the “urgent” thread with six people bumping the same ticket and no decision owner is the only thing that grows faster than the backlog. If a new ask has no urgency, no impact, no definition of done, and no update plan, treat it like poorly labeled equipment in a storage closet. You can open the box later when someone realigns it.

I still forget question four about once a month, and the following Monday reminds me why that little detail mattered.