How Leaders Set Fair Office Norms for Hybrid Work

Our situation is a little different than most companies wrestling with this. We build and run the robotics that physically write our handwritten notes, so a chunk of the team has to be on site, there's no flexible version of loading paper and ink into a machine from home. But our sales, marketing, and support folks could work from anywhere.
The rule we use: if the work requires touching a physical machine or physical inventory, you're in person, full stop, no negotiation. If the work is a screen and a phone, you pick your setup, but you show up in person for anything that benefits from a whiteboard, planning sessions, onboarding a new hire, working through a messy problem nobody's solved yet. Those moments lose something over a video call that I can't fully explain, but I've watched it happen enough times to trust the pattern.
What made it feel fair instead of arbitrary was tying the rule to the type of work, not the person's title or how long they've been here. Nobody gets to negotiate their way out of the machine room, and nobody gets forced into the office to answer emails they could've answered from their kitchen table.
Rick Elmore, Founder/CEO, Simply Noted (simplynoted.com)

The fairest hybrid policies distinguish collaboration from observation. Too many companies call people in to watch presentations they could have streamed, then wonder why flexibility feels performative. In person should be reserved for work where body language, informal sequencing, or shared physical context changes the result. I treat that threshold as a quality standard, not a management preference.

The ritual is a collaboration map, created before dates are chosen. Teams identify problems that benefit from co-location, then publish dates ahead for employees to arrange caregiving, travel, and accessibility. Managers cannot add office days afterward. Predictability is an inclusion mechanism, and it forces leaders to plan collaboration instead of summoning people impulsively.

The test is: Does it involve a person's care changing hands? If yes, in person it is—patient handoff, a clinical huddle where someone's risk level shifts, a new tech's first week on the unit. Everything else, status meetings, budget reviews, can be done on the screen, and nobody is worse off for it.

Because I run a residential treatment center I can say with some confidence that there are a decent number of people at my organization who have never been hybrid. The nurses, techs, and clinicians were there in the building because the patients were so it wasn't actually a matter of "everyone has to work from home and everyone works in the building." The fairness problem in our shop wasn't remote versus office. That is when people in the billing department, HR, and utilization review could work from anywhere that there became a problem because people felt resentful when it felt like everyone else was working from home in sweatpants.

If there is a remote person, then everyone has to be on camera. So if there are five people in a conference room, then all five people are on camera. So we just had one laptop at the end of the table, which made the remote people sort of, their voices were flat, so we fixed a little bit of that with rules around meetings, and now the room has no home-field advantage.

One: If a single person is remote, everyone joins from their own camera, including the five people sitting in the same conference room. The other rule is that office time gets a stated purpose on the invite: if I couldn't articulate why I needed to be in the same room as someone, then I had to cancel. That sentence killed more pointless commutes than any policy document ever did.

The clearest rule is simple: office time should be reserved for work that genuinely benefits from being together, such as strategic planning, complex problem-solving, onboarding, relationship building, and important team decisions. Routine execution and focused individual work can remain flexible. One ritual that makes this fair is a monthly "purpose check" where each planned office day has a stated objective before being scheduled. Gallup research found that hybrid teams with a formal or informal collaboration plan are 2.2 times more likely to say hybrid work has an extremely positive impact on team collaboration. The principle is that presence should have a purpose, not simply satisfy a calendar requirement.

At LAXcar, we get people together in situations where their physical presence will make a material difference—no matter the day of the week. The dispatcher can manage scheduling, confirmations, and communication with the client remotely. However, prior to the 200- to 300-person event, I would have the operations manager, dispatchers, and field coordinators together to review the manifest, vehicles, staging, escalation, and contingency plans. It is at such a meeting that ten minutes together can save hours later in confusion.

The ceremony for ensuring that expectations were fair and balanced was always making sure the need for physical attendance was tied to a purpose. We should have been able to say to anyone who had to physically attend that they knew what needed to be done that could not be done remotely. We used this principle universally in our roles and did not give everyone the same schedule.

Purposeful office time is less about proximity than recovery. I reserve it for moments when a team has accumulated misunderstandings, not simply tasks. Misunderstandings compound across channels, especially when people interpret silence, changing priorities, or blunt written feedback differently. A well-designed gathering can restore shared context before mistrust turns into slower decisions and defensive execution.

One ritual is a reset session triggered by repeated rework, delayed handoffs, or conflicting customer narratives. The invitation states the repair sought, rather than vaguely calling for alignment. Everyone receives the same pre-read, and the outcome becomes a working agreement. Tying presence to a visible breakdown keeps office time from becoming ceremonial. It makes leaders responsible for repairing the system, not blaming individuals for friction.

We use a quarterly planning studio as our most important in person team ritual. We avoid long presentations and begin with concise pre reading shared before everyone arrives. We spend the day resolving priorities dependencies and difficult tradeoffs through open discussion together. We focus on decisions that benefit from face to face collaboration and shared understanding.

We keep the schedule predictable so everyone can plan caregiving travel and personal commitments. We announce the dates early to reduce stress and improve preparation across every team. We publish every decision with the supporting context after the session ends for transparency. We make office time a focused investment in alignment while flexibility stays our standard operating model.

I only require in-person time when the work involves a decision no one has made yet. Kickoffs where scope is still fuzzy, disagreements that have gone two rounds over text, and anything where someone new needs to be read into how we operate. Everything else runs remote by default, because most of my team's output doesn't improve by putting bodies in a room.

The test I use is whether the meeting is producing information or transferring it. Transferring information is a document. Producing it, where people argue, sketch, and change their minds in real time, is worth the travel and the babysitter and the lost morning.

What made it feel fair was publishing the reason on the invite. Every on-site block has a one-line note saying why it can't be async. If I can't write that line, I cancel and send a doc instead. People started holding me to it.

Running distributed teams across time zones, I've watched companies cut development costs by 60 to 70 percent compared with U.S. equivalents, and none of that works if presence becomes a loyalty test. So I never count office hours. I count whether the hard calls got made and whether the person who wasn't in the room found out the same day.

First and foremost, we try to make in-person requirements as minimal as possible. The whole point of allowing remote work is to accommodate the lives of your employees and ensure that working is accessible to them, so if they normally work remotely it's not fair to them to require them to come in often. A rule we try to stick by to help maintain this is not requiring in-person meetings or work for remote/hybrid workers more than once per quarter. That way, we really do respect their time and we give them plenty of time to prepare for any in-person events well in advance so that they can work it into their schedule.

Our team is global and mostly works remotely, but every year, we think it's important to have a company meeting in a city we decide on. It's a moment to connect personally with other team members, build a good-quality network, and share important knowledge we've learned throughout the year. The whole team gets excited about it because it's a way to feel more engaged with the company.

Distinguishing between moments that call for physical presence is about differentiating between high-context teamwork and individual tasks. In the management of distributed engineering and delivery teams located all over the world, one must realize that making someone sit in the office just to be on a video call or to code alone at their desk goes against all the principles of trustful hybrid work. To make the time spent in the office really useful and fair, we use the following rule: if the task can be done with headphones on, it is best done at home.

We use our office space only for high-context collaborative activities. This implies that all the in-office meetings are aimed at the cross-functional alignment of architecture, retrospective meetings on complicated client onboarding processes, and strategic project kickoff meetings where nuances matter, feedback must be obtained quickly, and psychological safety needs to be guaranteed. Just so that you understand the significance, for instance, if you are kicking off a significant software delivery period or trying to overcome a complicated technical problem, all the product owners, UI designers, and systems architects present in the same room will help you reduce the time needed for alignment.

Moreover, in order to keep everything fair and maintain an inclusive environment for our totally remote and distributed team members, we perceive the office as an interactive collaboration hub rather than the source of surveillance. When an employee comes to the office, their calendar for that day is fully cleared from any routine tasks and execution work. Such clear separation ensures that coming to the office means having exciting and valuable meetings, while regular individual work is done from any point without disruption.

I decide which moments must be in person by adopting a remote-first default and reserving co-location only for interactions that cannot be replicated remotely. That approach preserves flexibility and inclusion because being onsite is the exception, not the baseline. The clear ritual I established was that all key business decisions and future updates are documented in writing and shared with the team. That rule made expectations about office time feel fair, reduced proximity bias, and kept in-person meetings purposeful rather than arbitrary.

Balancing in-person collaboration with flexibility is one of the more challenging aspects of leading a modern team. For me, the key was establishing a clear and intentional purpose for office time. At my company, we set non-negotiable workdays in the office twice a month, strictly reserved for high-impact activities like strategic planning, brainstorming sessions, and team-building efforts. This ensured that when we came together, it wasn't just about being present but about creating value that video calls couldn't replicate.

At the same time, flexibility remained a non-negotiable in our culture. We made schedules predictable well in advance, allowing the team to plan effectively while accommodating personal needs. The clarity brought structure, and the balance respected everyone's time. By framing these in-person days as valuable collaborations rather than obligations, we built trust and engagement. This approach resulted in a rhythm that fostered connection, improved decision-making, and ultimately drove growth in both financial performance and team morale.

We believe inclusion begins by making physical presence a thoughtful choice rather than a default expectation. We bring people together at the beginning and end of important work when shared discussion adds value. This creates alignment early and keeps everyone focused on the same goals from the start daily. The rest of the work can happen wherever people do their best work.

We follow a simple agenda check before every in person meeting. Organizers share the goals key materials and the reason live collaboration is helpful. We invite everyone to privately share travel caregiving disability or time zone concerns. When participation feels uneven we redesign the meeting so everyone can contribute equally.

We have two criteria for required on-site time: It needs to be meaningful, and it needs to be predictable. We aren't going to make someone come into the office on a fixed schedule if they have no in-person meetings or intensely collaborative work scheduled, and we aren't going to make someone come into the office unexpectedly on short notice. Most of our in-office time is for team meetings, client pitches, and other valuable face time. We'll also do occasional milestone and teambuilding days a few times a year.

I avoid blanket office mandates because fairness does not always mean identical schedules. Fairness means people understand the criteria, receive adequate notice, and have a meaningful way to contribute. In-person time is reserved for work where proximity creates clearer communication, stronger relationships, or faster resolution.

The ritual is a short retrospective after every planned office gathering. Participants answer two questions, what was uniquely better because people were together, and what could have been handled remotely? Patterns become visible quickly. If a meeting repeatedly produces no distinct benefit, it is redesigned or removed from the calendar. This feedback loop keeps leaders accountable and gives employees evidence that their time is respected. It also turns hybrid work into an evolving practice, shaped by real outcomes rather than assumptions about where productive work must occur.

We reserve in person time for moments that create institutional memory. We do not treat these gatherings as meetings moved into one building. We share customer stories examine setbacks recognize contributions and make the few decisions that shape our next chapter. We design every gathering so people leave with shared context and confidence to work independently afterward.

We publish a simple why together memo before each gathering to explain the purpose outcomes participants and sessions. We also provide a remote access path for anyone facing travel caregiving disability or distance. We believe inclusion should never depend on a private request for an exception. We have found clear purpose makes office time feel like an investment.

Hybrid policies become exclusionary when people closest to headquarters receive spontaneous influence than colleagues who travel. The issue is not only attendance, it is where unfinished decisions migrate after meetings. I have seen remote contributors sidelined by corridor conversations that no calendar captured.

One ritual protects against that drift. Any decision started in person remains provisional until it is posted in the decision log for one day. The log names the owner, the alternatives considered, and the input still welcome. Leaders are expected to bring unresolved questions back into that channel, even if everyone in the room agrees. This modest delay prevents geography from becoming a shortcut to authority.

The only meeting we made mandatory in-person was the one where someone could leave feeling blindsided. Performance conversations, big product pivots, anything where tone matters more than information. Everything else stayed async or video.

We run Pageloot across Tallinn and Bali, so "in person" was never the default. That forced us to be deliberate early. The rule we landed on: if the outcome of a conversation depends on reading the room, you need to be in the same room. If it doesn't, you're wasting someone's travel budget or sleep schedule.

The ritual that made it feel fair was announcing the in-person criteria publicly before anyone had to ask. People stopped guessing whether remote meant second-tier. They knew exactly which situations would pull them into a physical space and why, which made the ask feel legitimate when it came.

The inclusion piece followed from the same logic. Hybrid setups fail when in-person time is social and optional for some but subtly career-critical for others. Once the criteria were written down, proximity stopped being a competitive advantage. Remote team members could prepare for the same high-stakes moments on equal footing.

One number that helped: we tracked how many decisions got reversed after the meeting. In-person calls had a much lower reversal rate on the categories that mattered. That made the policy easier to defend and easier for the team to trust.

If there's an entire company that needs to be in the same room, that's when we start meeting in person. All other activities take place online, like team meetings, 1:1 meetings, reviews, etc.

That rule took away the gray area that leads to most hybrid resentment. No one has to wonder if they are needed or if they are being viewed as less committed if they don't show up.

There is one ritual that makes it work, which is our quarterly team building. It's a whole day of no work and everyone is present in person. We make plans for something fun, we eat together and spend some time together. Because it is rare, people look forward to it instead of treating it as an obligation.

The rule that held for us: in person is for disagreement, not for status.

At DexGuru we hired across time zones and the team never shared a working day. What we found was that the meetings people resented travelling for were the ones where information flowed one way. Nobody needs a room to hear an update. What people did need a room for was the argument nobody wanted to have in writing: the roadmap call where two leads disagreed, the postmortem where someone had to say out loud that the call was mine.

So the test became whether the meeting could plausibly end with someone changing their mind. If yes, that's a reason to be together. If the outcome is already decided and the meeting exists to transmit it, that's a document.

It read as fair for two reasons. It applied to me, and it was legible enough that nobody had to guess whether a given week counted. It also protected the people furthest from the office, who under a days-per-week rule are quietly paying the most for the least reason.

I'm not certain it survives at large headcount. We were small enough that everyone could name the disagreements in flight, and I don't know what the equivalent test looks like when you can't.

I decide which moments require in-person presence by looking at relationship building and high-stakes collaboration. Daily administrative tasks, lead screening, and vendor communications happen seamlessly from anywhere.

However, property walkthroughs, final pre-closing contract reviews with distressed sellers, and complex renovation feasibility walks require boots on the ground to build genuine trust and prevent costly misjudgments.

To keep office expectations purposeful, I established one clear rule: "Deal Day Tuesdays." Every Tuesday, the entire acquisitions and project management team meets at the office from 9:00 AM to 1:00 PM for deep-dive pipeline reviews, joint contractor negotiations, and team lunch.

After 1:00 PM, everyone has complete autonomy over their location for the remainder of the week. This single ritual creates a predictable cadence where face-to-face time feels collaborative rather than punitive, protecting our workplace flexibility while ensuring high-impact deals receive the collective focus they demand.

I decide in-person moments by whether multiple people truly need to participate together or whether the issue only concerns a few individuals; if it is the latter, I address those people directly rather than convening the whole team. This preserves flexibility and inclusion by not forcing others to attend unnecessary gatherings. My clear rule is to keep recurring meetings on the calendar but be ready to cancel them the day of or night before if they are not needed, and to invite only those directly affected. We also begin calls promptly and move to the business at hand so office time feels purposeful and respectful of everyone's schedule.

We believe fairness grows when leaders follow the same standards they expect from everyone. Too many hybrid meetings excuse senior leaders from explaining why meeting in person truly matters. Employees often carry the travel and scheduling burden without the same flexibility or clarity. We use a reciprocity test to decide whether attendance is genuinely necessary for everyone.

If we would not join the meeting for its stated purpose we do not require others. After every meeting we send a short receipt to each participant immediately. It captures the decision the open issue and the next owner with clear responsibility. This simple habit shows that office time leads to real progress and stronger collaboration.

My rule is: don't commute for information.

If the primary reason for gathering people in an office is a status update, presentation, or information exchange that could happen just as well remotely, it's hard to justify asking people to give up flexibility for it.

In-person time should earn the commute.

I would reserve it for the things that genuinely become richer when people share a room: building relationships, wrestling with messy ideas, repairing friction, celebrating together, and taking the small interpersonal and creative risks that build trust.

At Make Believe Works, we work with teams specifically around those kinds of interactions. One thing we've learned is that simply putting people in the same room doesn't create connection. You have to give them a reason to interact differently once they're there.

That principle also makes hybrid policies feel fairer. Instead of "everyone must be here three days because those are the rules," employees can understand why this particular moment benefits from being together.