Leaders Share Triage Rules That Protect Deep Work from Work Chat and Email

My single triage rule for chat, email, and Slack is simple. If responding takes under two minutes, do it now or archive it. The middle category, "I'll come back to this later," is where most knowledge workers lose their day, because every "later" item gets re-read three times before getting handled. Two-minute reply or one-second archive. Nothing in between.

Stop treating Slack like a fire alarm. Most "urgent" messages aren't actually emergencies. They are just your team outsourcing their anxiety directly to you. An underwriter kicks back a commercial auto policy. A Google core update drops our ranking for "Texas liability insurance" by two spots. Suddenly everyone loses their minds. If you break your deep work to soothe them, your own productivity dies. I turn off all notifications. Completely dark.

But I leave SMS open for my managers. And they know my one strict rule. Unless the site is literally offline or we are actively getting sued, do not ask me what to do. My standard reply to a panicked message is always the exact same line. "Assume I am completely unreachable today. What is your call?" That changes the entire dynamic instantly. They stop typing. They realize they already know how to fix the problem. They just wanted a safety net.

Give your people the authority to fail small. It is the only way you survive running a business. If an SEO tech breaks a canonical tag because I wasn't there to hold their hand, we just fix it tomorrow. But if I derail my own focus block to micromanage every minor crisis, the company stops growing. Silence the noise. Force them to think.

Hi,

The rule that changed how I handle this is simple: urgency is a claim, not a fact, and it is my job to verify it before responding.

Most messages that arrive marked urgent or that feel urgent in the moment are not actually urgent in any meaningful sense. They are important to the person sending them, which is understandable, but importance to someone else is not the same as requiring my immediate attention. When I stopped treating every incoming message as a legitimate interruption and started treating urgency as something to verify rather than assume, my ability to protect focused work changed significantly.

The practical system I use is built around a simple triage question I ask before responding to anything that arrives during a focus block: if I do not respond to this in the next two hours, does something actually break? Not something that will mildly inconvenience someone. Something that genuinely breaks. Most of the time, the answer is no, which means the message waits. When the answer is yes, it immediately gets my attention, regardless of what else I am working on.

The single reply line that has drawn the most focus is this: "I have this on my radar and will come back to you by the end of the day." It does three things simultaneously. It acknowledges the message, so the sender does not feel ignored. It sets a clear expectation, so they are not following up in an hour. And it buys me the time to finish what actually matters before I context-switch into their problem.

The cultural piece that makes this sustainable is openly modeling it. When the people around you see that a calm, measured response time is how strong operators work rather than a sign of disengagement, they adjust their own expectations accordingly. Urgency culture is often a leadership culture problem before it is an individual discipline problem. When the leader stops rewarding instant responses with instant attention, the volume of manufactured urgency tends to drop on its own.

Single rule: nothing called urgent is actually urgent unless someone is bleeding or money is on fire. Slack and email feel urgent because the medium was built for interruption. At memelord.com I batch all messages into three windows: 9am, 1pm, and 5pm. Outside those windows I'm invisible. First week the team thought I'd quit. Second week our shipping speed doubled because nobody could derail my deep work for tactical questions that resolve themselves in 20 minutes anyway.

The reply line that saved my focus: "On a deep work block until 5pm, will respond then. If it's truly time-critical, text my phone." Nobody texts. They don't actually need me, they need the dopamine of a reply. Treating attention like the rare resource it is gave me back roughly two hours a day. Founders who reply to Slack in 60 seconds aren't productive, they're reactive. Output tells you which one you are.

I run ITECH Recycling, where a lot of "urgent" messages involve data destruction, pickups, compliance questions, or a client retiring hardware that may still hold sensitive records. In that kind of environment, I triage by consequence, not tone: if the message affects data security, chain of custody, or a same-day client commitment, it gets immediate attention; if not, it gets routed into the next decision window.

My single rule is: don't break focus for noise, only for risk. The reply line I use is: "I'm in the middle of an active ops block; send me the one decision needed or the compliance risk, and I'll clear it fast." That forces people to separate urgency from vagueness.

This helped a lot when we were coordinating secure device pickups and serialized logging for clients who needed proof of compliant handling. If a message says "call me ASAP," I don't jump; if it says "these drives are leaving the building at noon and need destruction documentation," that's real and I switch immediately.

What keeps momentum is having only three escalation triggers: data exposure, regulatory/compliance impact, or a client-facing deadline that moves today. Everything else can wait until I finish the task that actually moves the business forward.

I'm Runbo Li, Co-founder & CEO at Magic Hour.

The single rule that changed everything for me: nothing is as urgent as it feels. I call it the "two-hour test." If a message will still matter in two hours, it can wait two hours. That one filter eliminates about 90% of the interruptions that feel like emergencies but are really just someone else's anxiety landing in your inbox.

When David and I were building Magic Hour through Y Combinator, we were two people serving millions of users. If I responded to every "urgent" message in real time, I would have spent my entire day in reactive mode and shipped nothing. So I developed a system. During my focus blocks, I have a single auto-reply that does all the heavy lifting: "Heads down on something critical. I'll be back online at [specific time]. If something is literally on fire, call me."

That last line is key. Giving people an escalation path, an actual phone call, means they self-select. In over a year of using this, I've gotten maybe three calls. People realize their "urgent" Slack message isn't phone-call urgent. The friction of picking up a phone forces honest prioritization on their end, not just yours.

Here's a real example. During a week when we were migrating our entire infrastructure, I had a partner reach out about a deal term that "needed an answer today." Old me would have dropped everything, context-switched, lost 45 minutes getting back into flow. Instead, they got my auto-reply, waited two hours, and when I came back to it, they'd actually resolved the question on their own. That happens more than you'd think.

The deeper principle is this: every time you break a focus block to answer a "quick" message, you're not losing five minutes. You're losing the 20 minutes it takes to reload your mental state. For a two-person team building at our scale, those 20-minute penalties compound into entire lost features, entire lost weeks.