The inbox treats a five-minute favor and a three-day analysis as the same kind of yes. Right now you have 12 unread messages stacked with unlabeled requests, each marked urgent by the sender, and you’re staring at the first one that says “can you pull last quarter’s metrics before EOD?” with no context on who needs it or why. Your pen hovers over the open notebook page beside your laptop, and you already know half of these asks don’t actually require your input at all.
The two immediate choices you have for every incoming ask
You don’t get to say yes to every request that lands in your inbox, no matter how polite the sender is, and ignoring requests until they blow up only creates more work for you later. The two real options in front of you right now are: triage each incoming ask in 30 seconds or less right now, or leave every unprocessed ask in your inbox to pile up and crowd out the work you already planned to complete today. There is no third option that lets you “get to it later” without costing you mental energy every time you scroll past the unread notification. You pick the first option, because you don’t want to spend half your day refreshing your inbox wondering what you missed. You don’t need extra tools or complicated steps to do this, just the open notebook or blank note you already have pulled up beside your inbox.
Sort criteria that only uses information you already have right now
You don’t need to follow up with anyone or dig through old threads to assign each ask to the correct box, because all the information you need is in the initial request itself. The four boxes you use are do, schedule, ask, drop. You assign an ask to do only if it takes less than two minutes to complete, you already have all the information you need to finish it, and no further follow up will be required from you after you send the response. You assign an ask to schedule if it takes longer than two minutes, it explicitly falls under your documented job responsibilities, and you have all the context you need to complete it when you carve out time for it later. You assign an ask to ask if you are missing critical context to complete it, you don’t know if it’s actually your responsibility, or the request was sent to a large group thread with no named owner so you don’t know if someone else is already handling it. You assign an ask to drop if it falls outside of your job responsibilities, it’s irrelevant spam, or the request is for work you would never agree to prioritize even if you had extra free time. You don’t overcomplicate the sort: if you’re unsure which box an ask fits into, you default to ask first, no extra deliberation allowed.
Fill this table with the next 10 asks in your inbox
You go one by one through the next 10 unread asks in your inbox, no skipping, no switching tabs, no responding to unrelated texts while you work. For each ask, you write a 10 word or less snippet of the request, assign it to the correct box, and write the single next immediate action you need to take for that ask, if any. You spend 30 seconds max per ask, no overthinking. You can write directly in your notebook or a new note on your laptop, using this structure:
| Ask snippet | Box assigned | Next immediate action |
|---|---|---|
| Illustrative example: “Can you send Q3 onboarding deck EOW?” | Schedule | Block 90 minutes Wednesday afternoon to update and send the deck |
| Illustrative example: “Can you review this 1-page project pitch?” | Do | Open attachment, add 2 line comments, hit reply now |
| Illustrative example: “Need someone to run point on office potluck next month” | Ask | Reply to thread asking if operations lead is handling this before committing |
Once you fill the table for all 10 asks, you complete all the do box items immediately, before you do anything else. You add all the schedule box items to your calendar right now, blocking the exact time you will complete them so no other meetings get scheduled over that slot. You send all the ask box responses immediately, so you get the information you need as fast as possible. You delete all the drop box asks immediately, no archiving, no saving for later, just remove them from your inbox entirely. If you run into an ask that you can’t assign in 30 seconds, you put it in the ask box and write the specific question you need answered to clarify it, no exceptions.
Adjust misassigned asks when you hit a clear roadblock
You will assign some asks to the wrong box at first, and that’s fine, there are no penalties for small mis-sorts as long as you fix them as soon as you notice a clear roadblock. If you assigned an ask to do but when you start working on it you realize it will take longer than 10 minutes or you’re missing critical information, that’s the sign you picked the wrong box. The small fix is to move it immediately to the ask box, send the single specific question you need answered to move forward, and delete the task from your immediate to-do list until you get a response. If you assigned an ask to schedule but when you sit down to work on it you realize it doesn’t actually fall under your job responsibilities, that’s the sign you picked the wrong box. The small fix is to forward the ask to the correct person with a one line note that you’re passing it along, remove the time block from your calendar, and drop the ask from your list entirely. If you assigned an ask to drop but someone follows up a few days later asking why you didn’t complete it, that’s the sign you picked the wrong box. The small fix is to reply once with a one line note that this falls outside of your current responsibilities, point them to the person who can help, and drop the ask again, no long explanations or apologies required. This process also eliminates asks that bounce around group threads with no named owner, because you never take ownership of an ask unless someone explicitly names you as the responsible party in the thread.
Triage the next batch of incoming asks using the same list at the start of your workday tomorrow
Right now, you tape the filled table to the edge of your laptop, so when you open your laptop tomorrow morning, you can see the box definitions and your last 10 assignments to reference immediately. You don’t have to rewrite the sort criteria or start from zero, because you already have the structure in place right in front of you. At the start of your workday tomorrow, before you open any other tabs or join any meetings, you pull up all unread asks that came in overnight, sort each into the same four boxes, add the next immediate action to your list, and complete all do box items right away. You can reference the four box definitions on Find Core Insight if you forget the sort criteria, but you’ll likely have them memorized after you sort 20 asks total. You repeat this process every morning, and whenever you have 10 unread asks stacked in your inbox during the workday, so you never end up with a pile of unprocessed requests hanging over your head. Right now, you close this tab, click on the first unread ask in your inbox, and assign it to the correct box before you do anything else.