Messages
The 4:58pm Message
Nothing good starts with “quick one before you go”.
At 4:58pm, a work message contains more information than the words on the screen. “Quick one before you go” can be a genuine thirty-second question. It can also be the opening line to a task that has been waiting quietly in somebody else’s day and has just arrived in yours.
The reason late-afternoon messages annoy people is not simply the time. It is the uncertainty. You do not know whether the sender needs an answer, wants acknowledgement, expects action tonight or has simply sent the message before they forget.
Laptop nearly closed. Bag packed. Notification: “Quick one before you go, do you have the latest numbers for the deck?” You have the numbers. You also know that sending the numbers may lead to a second question about the deck.
There are quick questions, and there are doors
A quick question ends when you answer it. “What room are we in tomorrow?” “Can you send me the link?” “Was that figure 14 or 40?” Fine. A door question looks small but opens into work: “can you just check this”, “while you’re there”, “one tiny change”, “do you have five minutes?”
If the message includes a document you have never seen before, the word quick is already under suspicion.
“Need this ASAP” at the end of the day tells you almost nothing. Does ASAP mean before the sender’s meeting tomorrow, before close of business, or whenever you are next working? A useful urgent request includes an actual deadline.
You answer immediately. They do not reply. This is how people learn not to treat every late message as an alarm.
The same message on Friday has a different weight because unresolved work can sit in somebody’s head all weekend. That does not mean it needs doing on Friday evening. It means the expectation needs to be clearer.
“I’m logging off now, but I’ll pick this up first thing tomorrow.” No speech. No apology. No invented emergency. Just a useful answer about when the work will happen.
How to reply without turning it into a drama
If you can answer in thirty seconds and want to, answer it. If the request creates real work, say when you can do it. If the deadline is unclear, ask. The important part is not to make yourself guess what the sender expects.
Managers can make this much easier by separating sending from expecting. A message sent at 5pm is not automatically a problem if the team knows it can wait. A message sent at 5pm with an unspoken expectation of immediate work is different.
The scheduling button is also there for a reason. If the thought can wait until morning, sending it in the morning removes the little burst of “is this now my evening?” from somebody else’s day.