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

Hybrid Agreement

How & when we allow remote work

A hybrid agreement is the difference between a team that manages hybrid by exception and one that manages it by design.

A hybrid agreement is the team's written record of how the arrangement actually works: who can work from where, what the expectations are around availability and communication, how decisions get made when people are in different places, and what happens when someone needs flexibility outside the agreed norm. It is not an HR policy. It is the team's own compact with itself.

The agreement matters most at the edges: when a new member joins and needs to understand the norms, when the team changes size or composition, when something is not working and the team needs a shared reference to return to. A team without a written agreement defaults to whoever has the strongest habits or the most seniority, which is a form of agreement, just not a deliberate one.

Make it explicitDraft a one-page hybrid agreement that covers location flexibility, core availability hours, communication norms, and how the team will revisit the agreement, and get every team member to add their name to it.

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.

One page, real commitments

Strong hybrid teams write their agreement in plain language and keep it short enough that people actually read it. A long policy document that no one refers to is worse than a brief shared statement that the team genuinely owns.

Built by the team, not for it

Hybrid agreements that are drafted by a manager and handed down are rarely as effective as ones the team writes together. The process of writing it is itself a useful conversation about what the team actually needs.

A living document

Strong hybrid teams schedule a regular review of their agreement (every six months is common) and update it when the team's composition or circumstances change. An agreement that reflects how the team worked two years ago is not much of an agreement.

Explicit exceptions process

The agreement covers the standard case. Strong teams also write a short note on how exceptions work: who to speak to, how to request a temporary change, and what happens if someone consistently cannot meet the agreed norms. This prevents exceptions from becoming invisible workarounds.

Questions for your team

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

If a new team member joined today, where would they go to understand the team's hybrid norms?
What is currently managed by convention or assumption that would benefit from being written down?
Does the team have a shared understanding of what flexibility is allowed, or is it negotiated individually each time?
When was the last time the team revisited how its hybrid arrangement is working, and what changed as a result?
What would need to happen for someone to request a change to the current hybrid norm, and do they know how to do that?

Watch for

A hybrid agreement written by leadership and handed to the team is a policy, not an agreement. The difference matters: people follow agreements they helped write.
Teams often delay writing a hybrid agreement because things seem to be working fine. The agreement becomes most valuable when something stops working, which is too late to start from scratch.
Agreements that cover the ideal situation but not real edge cases (a team member who needs to travel for a month, a project that requires sustained in-person collaboration) leave people guessing at the moment they most need clarity.