Six chat pings arrive while a draft is half done, and each ping sounds equally urgent. You hover your cursor over the chat tab, thumb hovering over the phone’s do not disturb toggle, and realize you’ve already spent 12 minutes switching between the two without moving either forward. The half-finished draft sits with a blinking cursor mid-sentence about client onboarding tweaks, and the unread chat previews tease requests from three different teammates, a vendor follow-up, and a question from an intern. You don’t have to guess which one to tackle first right now.
Map the 55-minute window you have before your next scheduled call
That hard stop is non-negotiable, so you work within that exact boundary instead of stretching decisions to vague “free time later” that never materializes. You immediately rule out any request that would take longer than 45 minutes to wrap fully, because you need 10 minutes at the end of the block to prep call notes and pull up relevant agendas, no exceptions. You don’t add extra time by assuming you can “squeeze in” a long task between now and the call, because that always leads to rushing the call prep or leaving the task half-finished and hanging over you through the meeting. Any task that falls outside the 45-minute max for this block gets flagged to revisit later, no guilt, no debate.
Write the two decision criteria at the top of your open notes tab
These are the only two factors you use to rank tasks today, no extra layers, no overcomplicating with arbitrary “urgency” labels people add to their messages to get faster replies. The first criterion is effort, measured on a 1 to 3 scale, where 1 means you can wrap the task in less than 15 minutes with zero extra follow-up required, 2 means 15 to 45 minutes of focused work with one quick follow-up check-in at most, 3 means it would require more than 45 minutes or input from at least two other people to move forward right now. The second criterion is alignment, measured on a 1 to 3 scale, where 1 means the task moves a goal you committed to this week forward directly, 2 means the task supports a teammate’s committed weekly goal, 3 means the task is unplanned and not tied to any agreed-upon priority for you or your team this week. You don’t spend time refining these definitions right now; if they don’t fit a specific edge case later, you can adjust them, but they work for every task vying for your attention in this current block. The scoring doesn’t pretend to be perfect science — it’s just a quick way to eliminate the back-and-forth in your head about what matters most.
Fill the decision grid with your current pending tasks
You list every single uncompleted task pulling at your focus right now: the half-finished draft, each chat ping request, and the call prep you already know you need to complete at the end of the block. You score each one quickly, spending no more than 10 seconds on each score; if you hesitate longer than that, you default to the higher number for both criteria to avoid decision paralysis. Once all tasks are scored, you sort them first by lowest alignment score (so tasks tied to core priorities come first) then by lowest effort score (so fast, high-impact tasks get done before longer ones). The table you build looks like this, with your own tasks swapped in for the example measurements:
| Task description | Effort score (1-3) | Alignment score (1-3) | Next action |
|---|---|---|---|
| Example measurement: Reply to intern’s question about expense report submission rules | 1 | 2 | Complete first, before opening any other task tabs |
| Example measurement: Follow up with software vendor about delayed license shipment for the new hire starting next week | 2 | 1 | Complete second, right after the intern request |
| Example measurement: Finish the two remaining sections of the client onboarding draft for the account launching next Monday | 2 | 1 | Complete third, for the rest of the block before call prep |
| Example measurement: Review marketing teammate’s draft social media graphic for the upcoming product launch | 3 | 2 | Defer to tomorrow’s first 15-minute block |
You don’t add extra columns or categories to the grid; the two criteria are enough to give you a clear order of operations for this block. Any new request that comes in while you work gets added to the bottom of the grid and scored before you agree to take it on, no quick “sure” replies in chat before you confirm where it falls relative to the work you already committed to for this window.
Tackle the highest-priority task on your sorted list immediately
You close all tabs except the one you need for that first task, turn on do not disturb for 15 minutes, and wrap it fully before moving to the next. You don’t check chat or email mid-task, even if you hear a ping, because that would add unnecessary context switching time and push you closer to missing your call prep window. When you finish the first task, you take 10 seconds to cross it off the grid, then move to the next highest-priority item. If a new request comes in that requires an immediate response, you score it on the grid first to see if it bumps any of your current tasks; you only drop what you’re working on if the request is a literal emergency that impacts customer safety or payroll, which almost none of these midday pings are. This rule keeps you from getting derailed by last-minute asks that don’t move core work forward.
Save the updated grid to your desktop for your first work block tomorrow
When you finish the last task you have time for before your call, you save the grid as a plain text file on your desktop so it’s the first thing you see when you log on tomorrow. You add a one-line note to the top of the grid with any new requests that came in while you were working, so you don’t have to dig through chat history first thing. You don’t spend more than 2 minutes updating the grid for tomorrow — you just drop in the pending tasks, you’ll score them when you sit down to work your first block, no extra prep needed. Before you answer, put this ask on /desk-tools/decision-grid/ and read the box. Then send the reply yourself. You don’t have to build a new grid every time you sit down to work; you can add to this one for the rest of the week, adjusting the criteria if needed to fit your upcoming scheduled blocks.