ThemeThe hybrid setup
CardCard 58 of 65
Questions5 to explore
StepAgree the basics

Working Hours

Expectations on when to be available

The question is not what hours people work: it is what hours people are expected to be reachable, and whether that expectation is shared.

Working hours in a hybrid team are rarely as simple as nine to five. Some people flex their hours around childcare or exercise. Some are in time zones where the team's core hours fall in the evening. Some value deep focus in the mornings and are not useful in meetings before noon. None of this is a problem unless the team has no shared understanding of what is expected.

The risk in hybrid teams is that availability expectations stay implicit while feeling universal. The person who replies to messages at 7am sets an unspoken norm. The manager who schedules 8am calls teaches the team what the actual workday is, regardless of what the policy says. Explicit agreements about when to be reachable make it possible for people to actually disconnect without fear.

Make it explicitAgree on and write down the core availability hours when everyone is expected to be reachable for synchronous contact, and confirm that these are realistic for every person on the team.

How strong hybrid teams handle it

The same building block, handled well. These are patterns from teams that work well across locations, offered as illustrations to react to, not rules to copy.

Core hours, not total hours

Strong hybrid teams agree on a window of core hours when everyone will be reachable for real-time contact, then leave the rest of the working day to individual arrangement. This protects flexibility while giving the team a shared anchor.

No-reply norms after hours

Teams where leaders regularly send messages outside agreed hours create an implicit expectation of response. Strong teams either agree to send scheduled messages, or actively normalize that responses outside core hours are never expected.

Status signals that people actually use

Strong hybrid teams use simple shared signals (a calendar block, a status in their communication tool) to indicate when someone is in focus time or offline. These only work if using them is normalized, not if people feel they have to be perpetually available to be seen as committed.

Questions for your team

Use these on your own or in a group. There are no right answers, only better conversations.

What are the actual hours during which people feel they need to be reachable, and has anyone agreed to that explicitly?
Has anyone on the team felt pressure to respond to messages outside the hours they considered their working day?
How would someone on the team know it was acceptable to fully switch off for an afternoon, and what would give them that confidence?
Are the availability expectations the same for everyone on the team, regardless of their location or role?
What happens when someone needs an answer urgently, and does the team have an agreed path for genuine urgency?

Watch for

Implicit availability expectations spread through behaviour, not policy. One person replying on Sunday is enough to make Sunday feel like a workday for the whole team.
Flexibility and availability are not the same thing. A team can offer flexible hours while still having clear shared windows when everyone is reachable. Conflating the two often means neither is real.
People who work in time zones where the core hours fall late in their day rarely complain about it explicitly. The cost shows up in attrition, not in meetings.