The inbox treats a five-minute favor and a three-day analysis as the same kind of yes. There is no built-in filter to flag asks that pull you off prioritized work, or requests that belong to someone else entirely, before you spend 10 minutes reading the full thread and weighing how to respond. This four-box card cuts down decision time for every incoming request without forcing you to write long custom replies or ignore messages that actually need your input.
Find Core Insight editors
Incoming asks that all feel like today’s job
When you are balancing competing deadlines, every new ping from email, Slack, or team chat can feel equally urgent. A new hire asking for access to a shared folder, a manager forwarding a client question, a teammate asking you to review a 20-slide deck, and a cross-department lead asking if you can lead a 30-minute sync next week all land in your feed with the same visual weight, no context of your existing commitments. Most people default to one of two unproductive triage habits: either replying immediately to every ask as it lands, derailing their current deep work and extending the time it takes to finish core tasks by double or more, or leaving requests unread until the requester follows up with an urgent ping, turning a small ask into a last-minute crisis that takes even more time to resolve. Many teams also have unspoken norms that pressure people to reply to every message within minutes, even if the request is not relevant to their role, which drains collective productivity across the entire organization. Illustrative example: A senior marketing specialist juggling a product launch deadline spent 2 hours a day fielding unfiltered incoming asks, 40% of which did not require their specific expertise.
Four boxes: do, schedule, ask, drop
This printable or digital four-box card sits at the top of your task list or pinned to your Slack/email drafts folder, so you can triage any incoming ask in 10 seconds or less. The card includes clear eligibility rules for each category, so you don’t second-guess your call, and pre-written response snippets to cut down on reply time.
| Box | Eligibility rules | Action to take | Pre-written response snippet |
|---|---|---|---|
| Do | Takes 2 minutes or less to complete, requires your specific access/expertise, and does not pull you off a time-sensitive deadline that is due within the next 2 hours | Complete the task immediately | [1-sentence confirmation of completion, no extra context] |
| Schedule | Takes longer than 2 minutes, requires your specific work, and is aligned with your core agreed-upon responsibilities | Block 1 focused slot on your calendar within 3 business days to complete the work, or set a meeting time for the request | “Got this, I will tackle this on [date] between [time range] and share an update by EOD that day. Let me know if that timeline doesn’t work for your needs.” |
| Ask | Requires input but not your specific expertise, or you do not have access/context to answer accurately | Forward the request to the correct owner, cc the original requester | “Thanks for reaching out! This falls under the [team name]’s purview, so I’ve looped in [contact name] who can help resolve this faster than I can.” |
| Drop | Is not part of your documented role, would require you to deprioritize agreed-upon core work, or is a request for uncompensated work outside your job scope | Archive the request, only reply if the requester follows up a second time | (Only send if followed up: “I’m currently focused on [pre-defined top 2 priorities] for this quarter, so I don’t have bandwidth to take this on right now. I’d be happy to connect you with resources to tackle this on your own if helpful.”) |
You do not need to overexplain your decisions when using the snippets: the goal is to be clear, not apologetic, about how you allocate your work time. If a requester pushes back on your timeline or decision to reassign the ask, you can share your current top priorities to align on what work takes precedence, rather than defaulting to shifting your schedule to accommodate their request.
Asks that bounce because nobody was named
The most common gap in standard triage workflows is addressing requests sent to a group chat, general inbox, or long cc list with no specific owner named. These often sit unaddressed for days because everyone on the thread assumes someone else will take ownership. The four-box card has a built-in rule for these unassigned asks: if the ask is sent to a group and no owner is named, and you are not the default owner for that type of request, it falls into the “ask” box unless it is an on-call emergency. Example timing: If you receive a group chat ask for feedback on a sales pitch, and no one tagged you specifically, you can forward it to the sales enablement lead with a note that no owner was assigned, rather than spending 20 minutes reviewing a pitch that is not part of your account portfolio. If you are the person sending a group request, you can reduce this friction by naming a specific owner for the ask in your initial message: Illustrative example: A sales team that started naming specific owners for all group chat requests reduced the average time to resolve client questions from 6 hours to 2 hours in their first month of the practice.
Using the card on the next ten messages
The best way to build a consistent triage habit is to use the card for your next 10 incoming asks, no exceptions, to get comfortable with the decision framework. First, turn off message previews if you find yourself getting pulled into reading full threads before triaging, to avoid getting distracted by extra context that does not impact your categorization. When a new notification comes in, open it only to identify the core question, then match it to the four boxes within 10 seconds. If you find yourself hesitating, ask two quick qualifying questions: “Is this something only I can do?” and “Will this take less than 2 minutes?” If the answer to both is no, it does not go in the “do” box. Illustrative example: A project manager testing the card on their first 10 incoming asks found 3 went to do, 2 to schedule, 3 to ask, and 2 to drop, cutting their triage time for those 10 messages from 45 minutes to 8 minutes total. If you want to track how your triage habits shift over the first month, Find Core Insight has a free, editable tracking spreadsheet you can use to log ask categories and time saved.
On-call incidents this four-box card must not delay
The four-box triage card does not apply to urgent on-call incidents that have predefined response SLAs tied to legal, safety, or customer retention requirements. These incidents include customer outages that impact more than 10% of active users, workplace safety incidents, confirmed data breaches, or time-sensitive requests from direct reports about a blocked deadline that is due that same day. For these incidents, you bypass the four-box card entirely and follow your existing on-call response process immediately. You can add your team’s specific emergency criteria to the bottom of your printed or digital card so you don’t have to remember what qualifies when you are in a high-pressure situation. Note that non-urgent requests marked “urgent” by the requester (for example, a teammate asking for a slide review for a presentation that is next week marked “asap”) still go through the standard triage process, since the requester’s personal sense of urgency does not automatically override your agreed-upon team priorities.
Keep a physical copy of the four-box card taped to the edge of your monitor or a digital version pinned to your primary messaging app for the first 30 days of use, until triaging incoming requests becomes automatic, and adjust the eligibility rules as your role or team priorities shift each quarter.