Agree on Communication Expectations Across Working Hours

Different working hours turn a routine message into a source of daily tension. One person sends a question at the end of their day, and by the time they check back, they read the silence as neglect. The other person opens their laptop hours later, sees a stack of unmarked requests, and has no way to tell which ones actually needed an answer before lunch. Nobody agreed on the rules, so everyone applies their own, and the gaps between those private rules are where trust erodes. Fixing this is not about tools or a chat app setting. It takes a direct conversation between the manager and the team about what response speed actually matches each kind of work.

Why This Conversation Goes Wrong

Most managers avoid this conversation because it feels like a small thing, and raising it can feel like overreacting to a single missed message. So the manager waits, the friction repeats, and eventually the manager brings it up only after frustration has built. By that point the conversation carries weight it should not have to carry, and the person on the other end hears criticism instead of a process fix.

The other common failure is treating the conversation as one sided. A manager decides on response windows alone and announces them, without asking the team which channels they actually check or what the overlap hours really allow. Rules built without that input get quietly ignored, because they were written around an assumption of how people work rather than how they actually work. A rule nobody helped write is a rule nobody feels obligated to follow.

There is also a habit of leaving urgency undefined. A message that says only "can you look at this" gives the reader no way to judge whether it needs an answer in ten minutes or by the end of the week. The sender knows the context in their head, but the reader does not, and that gap is what creates the false emergency.

How to Prepare

Before you raise this with your team, get specific about the actual overlap window between people's schedules. Not the schedule everyone lists in a company directory, but the hours when two specific people are both realistically online and able to respond. If Noah starts three hours after Tessa, their overlap might only be four hours in the middle of the day, and any expectation built on a full workday overlap will fail immediately.

Next, separate the categories of work by how much delay they can tolerate. Most teams have three real categories. Routine questions that can wait a day. Time sensitive work that needs an answer within a defined window, often the same day. Genuine emergencies that need someone right now, regardless of the clock. Vague categories like "urgent" and "not urgent" do not hold up, because everyone's definition of urgent differs. Attach a number to it. A time. A channel.

Ask each person which channel they actually check first when they log on, and what information helps them triage a request without asking a follow up question. A request with no deadline, no owner, and no context forces the reader to either guess or interrupt someone to ask, and both options cost time. Come into the conversation ready to propose a first draft of the rule, but stay open to revising it once you hear how the team actually works.

What to Say

Manager Priya opened with the real problem instead of a general statement about communication. She said, "Marcus, you start your day three hours after I start mine, and I've noticed I wait on answers to things I sent the evening before. I want to figure out a rule that works for both of us, not just one that works for me."

Marcus said, "From my side, I open chat at nine and there's a pile of messages with no deadline attached. I can't tell which ones needed an answer at seven and which ones can wait until after lunch. I end up guessing, and sometimes I guess wrong."

Priya said, "That's fair, and it's on me to mark things clearly. Here's what I propose. For anything time sensitive, like a customer issue that needs same day resolution, I'll write the actual deadline in the message, something like reply by eleven Eastern, and I'll tag whoever is on call. For routine questions, I'll put the request in the tracker with a due date instead of dropping it in chat. That way chat is reserved for things that need faster attention."

Marcus asked, "What about something I notice after I've logged off for the day? I don't want to sit on a real problem until morning just because I'm off the clock."

Priya answered, "Use the incident channel for anything that fits our defined emergency list, nothing else. I'll make sure the on call rotation and phone numbers are current so you're never guessing who to reach. Outside of that list, it can wait, and I mean that. You're not required to check messages after your hours end, and I'm not going to treat it as an expectation if you don't."

That last exchange matters as much as the categories themselves. Marcus needed to hear, directly, that logging off does not carry a hidden cost. Without that line, people keep checking messages out of anxiety rather than obligation, and the whole point of the agreement falls apart.

Mistakes to Avoid

Do not set the rule and skip the follow up. An agreement that only exists in one meeting fades within two weeks, because old habits are easier than new ones. Bring it back at the next team meeting and check whether it actually held up against three or four real requests from that period.

Do not let your own behavior contradict the rule you just set. If you tell your team not to expect off hours replies, then send messages at ten at night without scheduling them for the morning, you have taught them the opposite lesson through your actions. Most chat tools let you schedule a send time. Use that feature, because it removes the ambiguity of whether a late message is a demand.

Do not build the rule around a single bad week. If one project caused a spike in urgent requests, do not let that spike define what counts as urgent going forward. Base the categories on the normal pattern of work, and handle genuine spikes as their own separate conversation.

Do not treat this as a one time fix for a two person problem. The same gaps show up across an entire team once people work different shifts, time zones, or flexible schedules. Set the rule at the team level so new hires inherit it instead of having to renegotiate it individually.

How to Practice and Score It

This is a conversation worth rehearsing before you have it for real, because the tone matters as much as the content. A defensive or accusatory opening pushes the other person into justifying their schedule instead of solving the actual problem with you. Practice starting from the specific friction you observed, not from a general complaint about responsiveness.

DealSpeak lets you rehearse this exact scenario with an AI counterpart that responds the way a real teammate might, including pushing back on a rule that sounds one sided. You get scored on whether you named specific categories and deadlines instead of vague terms, whether you asked what channels the other person actually uses, and whether you addressed what happens outside their working hours without leaving it ambiguous. Run it a few times and watch whether your opening line invites input or just announces a decision.

If you manage a broader set of recurring HR conversations, the HR and Leadership practice conversations hub has related scenarios worth rehearsing alongside this one, including how to Diagnose Whether a Requested Workshop Addresses a Real Behavior Gap and how to Plan Accessible Learning Participation Through the Approved Support Route.

Closing the Loop

Write the agreement down in a short team guide that covers overlap hours, the routine response window, the urgent channel, and who owns on call. Test it for two weeks, then bring three real examples to your next team meeting and check whether the channel, deadline, and owner were clear on each one. A rule that survives real requests is worth keeping, and a rule that keeps failing needs another round of the same honest conversation.