ManageTime

Article

Does this email need a reply? The urgency nobody asked you for

No, you do not have to reply to every email at work. Most inboxes carry messages that need an answer, messages that only need reading, and messages that need nothing at all. The trouble is that they all look equally urgent on arrival, and the fastest way to end that feeling is to reply. That reflex has a cost, and the research says the urgency behind it is mostly invented by the reader rather than the sender. This article covers why the feeling shows up, and a two-question rule for deciding which messages actually earn a reply.

Do you have to reply to every email at work?

No. A work inbox is not a stack of obligations arriving one message at a time; it is a mix, and most of the mix does not need a reply from you. Some messages ask a direct question and wait on your answer. Some only tell you something, and reading them is the whole of the job. Some were sent to a list you happen to sit on, and nothing in them was ever yours to act on. The reply reflex treats all three the same, because on arrival they feel the same.

That feeling has been measured, and it does not match what senders actually expect. In 2021 Giurge and Bohns published a paper in Organizational Behavior and Human Decision Processes whose title gives away the finding: you do not need to answer right away, because receivers overestimate how quickly senders expect responses to non-urgent work emails. Across a series of experiments involving several thousand participants, people who received a non-urgent message assumed the sender wanted a faster reply than the sender actually did. The effect was strongest for email sent outside working hours, which several of the experiments were built around. Read the size of it as strongest for that after-hours case, and the direction as the part that carries over to your Tuesday afternoon.

So the urgency you feel on opening a message is partly your own invention. The sender wrote it, sent it, and moved on to their own list. The clock you are racing is one you started.

That does not make every message ignorable, and this page is not an argument for leaving people waiting. It is an argument for sorting. Once you accept that a message can need a reply, need only a read, or need nothing, the inbox stops being a queue of debts and turns into a list you triage. The email pillar covers how often to open it; the rest of this page covers what to do with each message once it is in front of you.

Why do you feel every email needs an answer?

The pull to answer at once has a name in the research. Barber and Santuzzi called it workplace telepressure in a 2015 paper in the Journal of Occupational Health Psychology: the preoccupation with responding quickly to a message, felt as your own urge rather than imposed by anyone. It is why a single unread line can sit in the corner of your attention and keep tugging at you while you are meant to be doing something else.

Their studies tracked where that urge leads. Telepressure predicted faster replies in the short run, and it also predicted more burnout, poorer sleep, and higher absenteeism, over and above other features of the person and the job. Answering fast feels like staying on top of things. Measured over weeks, it looks more like never putting the work down.

The engine underneath is uncertainty, and uncertainty is cheap to settle by looking. When you do not know whether a message needs you, checking takes seconds and answering ends the itch, so both beat the harder task of leaving it alone. A reply also produces a small, visible result: one fewer bold line, a thread you can see you handled. The task you were avoiding produces nothing that legible for another hour.

None of this means the feeling is a fault to scold out of yourself. It means the feeling is not evidence. The next message that makes you reach for the reply button is worth one question first: is this urgent because of what it says, or urgent because it is new and unread? The honest answer is often the second, and the second is not a reason to reply.

How do you decide which emails to reply to?

Two questions settle most of the inbox. Does this message ask something of me, and does my answer change what anyone does next? A message that asks nothing and changes nothing can be read and archived, whatever its tone suggests. A message that asks something but changes nothing, the update that only wants a nod, can usually wait for your next scheduled pass or go unanswered without harm. Only the message that asks something and moves something earns a reply on sight.

That is the Eisenhower Matrix pointed at your inbox. The matrix separates urgent from important because the two get confused, and email is where they get confused most. A new message announces itself as urgent simply by arriving. Whether it is important, whether anything you own depends on it, is a separate question the arrival cannot answer. Ask the importance question on purpose, since the inbox will keep answering the urgency one for you.

The wider evidence favours sorting over speed. A 2024 systematic review in the Journal of Occupational and Organizational Psychology by Russell and colleagues read 62 studies from 25 years of work-email research and named four actions that predict email done well, meaning email that supports both performance and well-being at once. Two of the four bear on the reply decision: triaging your mail deliberately, reading, answering and clearing in decided passes rather than on arrival, and sending only work-relevant mail, which is the same discipline seen from the sender side. When a message does clear the two questions and needs only a line back, the Two-Minute Rule (for tasks) applies. If the reply takes under two minutes, send it now rather than filing it to answer later, because tracking it will cost more than writing it.

The clearest message that needs nothing is the one that only says thanks. An acknowledgement is a closing courtesy, and returning it sends another message that also needs no reply, which is how a finished thread keeps twitching for two more rounds. Let it stop. In practice, letting a settled conversation close costs you nothing and saves everyone on the thread a notification. The traffic you do not generate is the cheapest inbox improvement there is.

How does your working style change the answer?

The questions above are about the message. Your working style decides which part of the sorting you will actually keep up. In practice, readers closest to this site's Architect style take to the two-question rule at once and then over-apply it, drafting careful non-replies where silence would have done. Sprinters clear fast and answer more than they need to, so the useful discipline for them is the pause before the reflex reply, not another rule. Improvisers do best when the decision is attached to a scheduled pass rather than made message by message, since a running inbox pulls a reply out of them every time. Visionary-leaning readers already ask whether a message matters, and their risk runs the other way: letting the message that did need a quick answer sit because it looked routine.

The honest limits, so this page does not oversell a rule. Some roles carry a real reply promise: a client-facing desk, a support queue, a manager who has said they want an answer within the hour. There the question is not whether to reply but how fast, and the move is to make the promise explicit rather than to quietly drop it. Some messages also carry an unstated deadline that is real even when the sender was too polite to name it, and part of reading well is catching those. The two questions sort the ordinary inbox; they do not override a commitment you actually made.

And none of it works if you never look. A reply you decided not to send is a decision; a message you never opened is a gamble.

Start with the next message that makes you reach for the reply button before you have finished reading it. Ask the two questions, answer the one that earns it, and archive the ones that do not. If the larger problem is how often the inbox interrupts you in the first place, the email pillar is the page to start from, and the working style self-check points at the methods most likely to hold for the way you work.

Frequently asked questions

Do you have to reply to every email at work?

No. Most inboxes hold messages that need an answer, messages that only need reading, and messages that need nothing, and only the first group earns a reply. The reflex to answer everything comes from the reader, not the sender. A 2021 study found receivers overestimate how quickly senders expect a response to non-urgent email, so the clock you feel is often one you started yourself. Read the message, ask whether your answer changes what anyone does next, and archive it when the answer is no.

Is it rude to not reply to a work email?

Usually not, when the message asked nothing of you and your silence changes nothing: an update, a copy for your information, or a thread that has already reached its end. Rudeness attaches to the messages that did ask something and got ignored, which is a different failure. If you worry a sender is waiting, the fix is to say when you handle mail rather than to answer everything at once. People accept a slower reply from someone whose timing they can predict.

Why do you feel every email needs an answer straight away?

Because the urge to respond fast is a real psychological pull, named workplace telepressure in the research, and it runs on your own discomfort rather than on the sender's demand. A 2015 study linked that pull to faster replies in the moment and to worse recovery, sleep and burnout over time. An unread message creates uncertainty, and answering it is the cheapest way to end the uncertainty. That makes the feeling strong, and it does not make it a reliable signal of what actually needs doing.

What do you do with emails that only say thanks?

Read them and stop there. A thank-you is a closing courtesy, and replying to it sends another message that needs no reply, which keeps a finished thread alive for no reason. The same goes for noted, will do, and sounds good. In practice, letting a settled conversation close saves everyone on the thread a notification and costs you nothing. If acknowledgement matters on your team, a norm agreed out loud beats a reflex nobody signed up for.

Sources