Ground Rules

Expected etiquette & response time

In a shared office, people absorb the norms by watching each other; in a hybrid team, those norms have to be written down.

Ground rules are the shared agreements about how your team behaves: when you are expected to reply, how meetings are run, what counts as available and what does not, how you handle it when someone does not follow through. These things exist in every team. In a hybrid team, the difference is that they have to be explicit, because you cannot pick them up by sitting next to someone.

Without written ground rules, every person on the team is operating on their own assumptions. The person who replies to everything instantly assumes everyone should. The person who responds end-of-day assumes that is normal. Neither is wrong, but the collision between those two assumptions is a constant source of friction.

Ground rules are not about control. They are about giving everyone the same starting point so that the friction is about the actual work, not about differing expectations nobody has named.

Make it explicitWrite down your team's core ground rules covering availability, response times, meeting norms, and how you handle disagreement.

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.

Write them together

Ground rules imposed from above tend not to stick. The strongest hybrid teams write their norms together in a short session, so that each person has had a say and understands the reasoning. The document that comes out of that session has more weight than one handed down.

Separate availability from responsiveness

Being online and being reachable are different things. Strong teams are clear about when people are working (available in principle) versus when they are in deep work (not responding) versus when they are genuinely off. All three are legitimate states, but they need names.

Revisit them when the team changes

Ground rules made with one team composition do not automatically apply when someone new joins or the team's work changes. Building in a regular, short review keeps the norms current and gives new members a natural moment to shape them.

Name the repair mechanism

Every ground-rules document should say what happens when someone does not follow them: not a punishment system, but a way to surface the friction early and address it without it becoming a bigger issue.

Questions for your team

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

Does your team have written norms for response times, and do people actually follow them?
When someone is in deep work or offline, does the rest of the team know and respect that?
How do new team members find out how things work here, and is that reliable?
When a norm is not working, how does your team surface that and change it?
Are there unspoken rules on your team that some people know and others do not?

Watch for

Ground rules written in a team meeting and never looked at again are not ground rules, they are intentions.
The loudest or most senior person's habits often become the unofficial norms, which means quieter or more junior people are held to standards that were never their own.
Hybrid teams often have different de-facto norms for office-based and remote members, and this asymmetry rarely gets named directly.