The short version
- At 22:00 you have three bad options: message them anyway, guess, or lose tomorrow morning. Most managers pick the first and feel bad about it.
- The situation is a design failure, not a discipline failure. Respecting someone's hours while needing an answer tonight is a genuine conflict.
- Almost every 22:00 question is retrieval: where something stands, what was decided, whether a thing was tried.
- Ask their StandIn first. It answers from what they wrote down, so the question resolves and they stay off.
It is 22:00. You are preparing for a 08:00 call with a customer and you need to know whether the export work will make the release. The engineer who knows logged off four hours ago and has, correctly, gone to live their life.
"I respect their hours and I still need the answer tonight."
The three bad options
| Option | Cost |
|---|---|
| Message them anyway | Their evening, and the norm you just set for the whole team |
| Guess | A commitment to a customer you may have to retract |
| Wait until morning | You go into the call unprepared |
The first option's second cost is the one managers underestimate. A single message at 22:00 tells the recipient, and anyone who hears about it, what the real expectation is. Whatever the policy says, behaviour from a manager is the policy.
Not a discipline problem
Advice on this topic usually addresses the manager's self-control: do not send it, use scheduled send, write it and sit on it. All reasonable, and none of it addresses the fact that you genuinely need the answer before 08:00.
A boundary that requires someone to accept a worse outcome will be broken whenever the outcome matters enough. That is not weakness; it is what boundaries without alternatives do. The honest version of this problem is that the answer exists, it is locked behind one person's availability, and every solution that only manages your behaviour leaves that intact.
What the 22:00 question actually is
Look at the last five things you needed at night. Almost always they fall into one of three shapes: where does this stand, what did we decide, or has this already been tried.
None of those require the engineer to think. They require the engineer to remember, which is retrieval, and retrieval is the one thing that does not need a person to be conscious. The rare genuine exception is a new judgement call, and those are much less common at 22:00 than the volume of evening messages suggests.
Ask their StandIn first
The rule to adopt, for yourself first and then for the team: at any hour outside someone's working day, ask their StandIn before you consider messaging them.
They spend ninety seconds at the end of each day confirming a brief, mostly pre-drafted from the work they already did: current state, open questions, blockers, next actions, decisions and why. While they are off, their StandIn answers questions from that brief in their words, with a source under every answer, clearly labelled as their StandIn. It never guesses: if the answer is not in what they wrote, it says so and names who to ask.
At 22:00 that gives you the export answer, sourced to the person who did the work, with no message sent and no norm set. And when the answer genuinely is not there, you learn that in seconds and can make a deliberate decision about whether this is worth an evening. See StandIn for leadership teams.
When it is genuinely urgent
Some things do warrant contact outside hours, and pretending otherwise produces a policy nobody believes. Define them narrowly and route them separately: customers affected right now, a legal matter, or a commitment failing tonight.
Three rules for those cases. Use a channel that is unambiguously an alarm, usually a phone call rather than a message, so there is no ambiguity about whether it could have waited. Say in the first sentence why it could not wait. And give the time back the next day, visibly, which is what distinguishes a genuine exception from an expanding expectation.
Common Questions
Is it acceptable to message a team member after hours?
For a genuine emergency, through an agreed route, yes. For a question with an existing answer, no, and the practical fix is having somewhere else to get that answer rather than relying on your own restraint.
Does scheduled send solve this?
It solves the recipient's evening and not your problem. The message arrives at 09:00, which is useful and does nothing for the 08:00 call. Use it, and do not mistake it for an answer.
What if my team says they do not mind?
They will say that, and it is not reliable information, because declining to mind is the safer answer to give a manager. Judge by what the team does rather than what they say, especially whether junior people are replying at 23:00.
How do I stop the pattern if it is already established?
Announce the change, then demonstrate it for a month, including on the night it costs you something. One visible instance of you waiting when it was inconvenient does more than any statement.
When you're off, your StandIn is on.
It answers your teammates' questions from work you've already done, in your words, with a source under every answer.