Making Hybrid Work Policies Feel Fair Across Teams

The boundary that made hybrid work equitable at Software House was implementing what we call meeting-free mornings until 11am, regardless of whether someone is in the office or working remotely. Before this, remote team members were consistently disadvantaged because in-office people would have spontaneous hallway conversations and make decisions before the remote staff even joined a call.

By protecting mornings for deep work across the entire team, we levelled the playing field. Nobody gets a head start on decisions just because they happen to be physically present. All collaborative work, standups, planning sessions, and client calls happen between 11am and 4pm, which is our designated overlap window. Outside those hours, everyone works asynchronously at their own pace.

The impact was immediate. Our remote developers reported feeling significantly more included in decision-making within the first month. Project velocity actually increased by about 15% because people were doing their most cognitively demanding work during uninterrupted morning blocks. The sustainability piece came from making the rule apply to everyone equally. When even I as the CEO follow the same boundary and refuse to schedule morning meetings, it signals that the policy is real rather than optional.

I'll be honest, our first foray into hybrid work was a bit of a mess. We're a digital agency. We've got designers and developers and SEO experts and project managers and all that. And when people started splitting their time between working from home and working from the office, our meetings were like something out of a sitcom. Half the people in the conference room, half the people staring at a computer screen trying to jump in and participate in the meeting.

It was a very visible imbalance. The people in the office were just naturally more vocal. They'd talk over one another. They'd interrupt. They'd start drawing things on a whiteboard. The people at home were trying to figure out how to unmute themselves at the appropriate time. Nobody meant for that to happen. Nobody meant for the people in the office to start dominating the decision-making process.

After a few weeks, it was clear that this wasn't a fair system. So we came up with one rule that solved most of that.

Every meeting is a remote meeting. Even if everyone is in the office.

If there are five people ten feet away from each other, they all open their laptops and join the same video call that everyone else is on.

That one rule eliminated the invisible advantage that the people in the office had. Now everyone has the same seat at the table. The developer working from another city has just as much opportunity to contribute as the designer working just across the office.

And it also ended up being a boon for collaboration than we initially thought. A lot of our work is already done on a screen. Designers are walking around a space, or developers are showing code, or the SEO team is looking at data. When everything is on a screen, the conversation is easier and everyone participates more evenly.

Hybrid work was a lot smoother once we had these rules in place. Everyone knows exactly how meetings will work. There was no guesswork.

My advice for other founders is pretty simple. Don't overthink hybrid policies. Office days aren't the problem most of the time. The problem is how people work together when they're in the same place.

Treat every meeting like everyone on the call is remote. Because most of the time, they are. It helps the team feel balanced if everyone joins in the same way. It helps the conversation be better too.

I run an HR consulting firm and have helped dozens of NJ-based companies navigate hybrid rollouts—the fairness problem almost always comes down to unwritten expectations, not schedules.

The single most effective boundary I've seen work: a written hybrid policy that explicitly states which roles qualify for which arrangements—and why. When it's documented and tied to job function rather than manager preference, you eliminate the "why does she get to work from home?" resentment that quietly destroys team cohesion.

One client was losing in-office employees who felt penalized for commuting while remote colleagues skipped "optional" team events. We helped them restructure: in-person days were anchored to collaboration-heavy activities (brainstorming, onboarding, team problem-solving), not just presence. Remote days were protected for focused work. Suddenly both groups felt their arrangement had purpose, not just policy.

Train your managers—this is where hybrid breaks down most. A manager who informally rewards visibility will unconsciously penalize remote employees in performance reviews. We've built management training around this exact bias, and it's the lever most companies completely overlook.

When did fair start meaning identical? That assumption caused most of our hybrid problems. We have about 60 people across India, all remote, but some teams need synchronous collaboration more than others. Our tech team works best with 2 overlapping hours. HR needs more face time for sensitive conversations. Forcing the same schedule on both created resentment, not equity.

What actually worked was letting each team lead propose their own rhythm with one constraint. Everyone available Tuesday and Wednesday afternoons. Beyond that, figure it out. It took about 6 weeks for the noise to settle. Some teams went mostly async. Others cluster their meetings. If you try to enforce one policy for everyone, the teams that suffer most are the ones whose managers confused presence with productivity. That problem existed before hybrid though.

The one rule that changed everything for our team at ResumeYourWay was simple: no meetings on days when people aren't in the office together. It sounds obvious, but most hybrid teams get this wrong. They schedule a Tuesday meeting and then three people are remote and two are in person, and the remote people feel like they're watching a conversation happen without them.

We set core collaboration days where everyone who can be in person is in person. Those are the days for brainstorming, client strategy sessions, and the kind of work that actually benefits from being in the same room. The other days are for deep focus work, client calls, and writing. Nobody is expected to be on camera for six hours on their remote days.

The fairness problem with hybrid isn't really about schedules. It's about visibility. The people who are in the office more tend to get more face time with leadership, which turns into more opportunities. We noticed this early and made a deliberate choice: every promotion conversation, every project assignment, every piece of feedback happens in a structured format that doesn't depend on who happened to be in the hallway that week. We run 110,000+ client projects and the team members handling those projects need to know they're evaluated on their output, not on whether they were physically present when a decision got made.

The boundary that made it sustainable was protecting remote days from creep. It's tempting to say "just this one quick meeting" on a focus day. But once you do it twice, the whole system falls apart and you're back to a schedule that works for nobody.

We make hybrid schedules feel fair by establishing core "collaboration hours," a routine I call the "shared window." Everyone remote or in-office blocks these hours for meetings, brainstorming, and cross-team discussions, while leaving the rest of the day flexible for focused work.

For example, we set 10 a.m.-2 p.m. as the collaboration window. This ensured remote employees weren't disadvantaged by spontaneous in-office chats, and in-office teams respected remote colleagues' availability. The boundary created predictability, reduced scheduling friction, and made hybrid work equitable. Team feedback improved noticeably, and cross-team projects ran more smoothly because everyone knew when synchronous work would happen.

The takeaway: fairness in hybrid work isn't just about equal days in the office; it's about creating structured overlap where collaboration can thrive without penalizing anyone's location or schedule.

Hybrid schedules are designed around the needs for collaboration rather than individual employees' preferences. This allows the team to understand that the purpose is to facilitate teamwork rather than to monitor the physical location of the employees. This is documented to ensure that the team is aware of the time for synchronous collaboration and the time for individual remote work.

One routine that facilitated the fairness of the hybrid work was the creation of shared 'days of team collaboration' where the team would be either physically present at the office or fully online as a team. This removed the inequity of some employees being physically present in the conference rooms while others were connected remotely. This ensured that critical discussions and decisions took place in a setting where everyone was at par.

At SnapADU, we make hybrid schedules feel fair by holding a standing weekly 30-minute video meeting for each department. That predictable checkpoint gives every team member the same access to updates, deadlines, and recognition regardless of where or when they work. We use that time to share wins and client feedback and to surface blockers so work stays coordinated. Because the meeting is short and scheduled, it respects flexible hours while keeping collaboration strong.

From my perspective as a founder at Wisemonk, the biggest challenge with hybrid work is not logistics but perception. Teams start to question whether people working remotely and those working in person have the same access to information, opportunities, and visibility.

One principle that helped us maintain fairness was designing collaboration as remote first, even when some people were physically together. This meant that key discussions, documentation, and decisions always happened in shared digital spaces rather than informal in person conversations. When information lives in one accessible place, everyone operates with the same context regardless of location.

A boundary that made hybrid work more sustainable was establishing clear communication routines around decision making. Important updates, project changes, and strategic discussions were documented and shared with the entire team instead of relying on hallway conversations or quick verbal updates. This ensured that no one felt excluded from important information simply because they were not in the room.

What this approach reinforced is that hybrid work becomes equitable when transparency replaces proximity. When teams rely on structured communication and shared documentation, collaboration becomes intentional rather than dependent on who happens to be present in a physical space.

The broader lesson is that fairness in hybrid environments comes from clarity. When organizations design processes that keep everyone equally informed and involved, teams can collaborate effectively without location becoming a disadvantage.

Confusion can hinder the hybrid workplace's ability to offer equitable experiences for employees by making the work of the leadership team—deciding what "fair" equates to—mean to have no differences in how the two groups provide work to one another, versus the anticipated challenges that occur with different roles. That means that true equity is based on being able to provide role-based transparency (in other words, showing teams that a System Architect's needs for deep work vary greatly from those of the Project Manager practicing their high-frequency sync activities). We also continue to foster collaboration through "intentional togetherness," which means that if we impose office requirements, we will only do so for those high-bandwidth activities, such as Sprint Retrospectives and Complex Problem Solving sessions, requiring the use of face-to-face interaction to truly benefit from those sessions.

A routine we developed to make our hybrid working approach sustainable was the development of "Core Sync Windows." Rather than measure the amount of time spent sitting at a desk, we established a four-hour block of time during which all people must be available for collaborative work regardless of where they are working. This effectively took away Proximity Bias from all staff members, as all people were expected to be available at all times, for all purposes during that time period. Additionally, this allowed our engineers' deep work cycles to remain intact outside of that time, while at the same time, allowing all people to not feel "left out" every day due to the non-presence within the office.

The only way to make hybrid work feel equitable over the long term is to create a shift in focus from measuring presence to measuring output. When the focus is on what employees will be delivering, as well as the predictable windows of communication throughout the day and through the entire week, the anxiety of where an employee is seated throughout that day tends to go away. At the end of the day, it is all about building a culture of trust and that the guardrails around the definition of "working" are defined and clear enough that employees know exactly what "working" means.

I think hybrid only feels fair when the rules are clear and the trade-offs are shared, not quietly pushed onto a few "office people." For me, the sweet spot has been one simple idea: hybrid gets shaped at the team level, inside a few company guardrails. We co-create schedules with each team, set a couple of shared "collaboration days," and hold managers accountable for judging output, not chair time. One boundary that really helped was this: if one person is on video, everyone joins from their own laptop, even if a few are sitting in the same room, so no one is the ghost on the screen.

At Medical Director Co., our addition of hybrid working arrangements has always been guided by a fundamental principle: employees would block time for two distinct collaborative meetings on their calendar every week while keeping their weeks flexible. This offers comprehensible times for team meetings/decisions while allowing employees autonomy to determine when to work on the balance of their available time. Additionally, one of the major challenges we have faced in implementing hybrid working environments is that some remote employees will miss essential conversations occurring in the office, and this change helps alleviate this issue.

A successful tip to monitor performance is to track participation rather than attendance. For example, Medical Director Co. measures the rating of employees on project completion times and employee genesis on projects based on the number of employees participating in the collaboration meeting, rather than the number of hours employees were found at their desks or how many employees arrived at the office before their assigned hours.

Additionally, when starting a new national team using multiple time zones, we were able to use this time blocking to improve overall response times and reduce scheduling conflicts.

Fairness in hybrid work is everyone following a reasonable guiding principle, versus everyone having the same hours of work. - Blaz Korosec, CEO, Medical Director Co.

At my organization, we achieved equity and sustainability by moving away from the traditional 9-to-5 model and adopting a strictly assignment-based workflow. Because our media operations span multiple continents and bureaus, we provide our teams with total autonomy over their own schedules. We focus on the quality and deadline of the deliverable rather than the hours spent at a desk.

This shift has significantly boosted team morale and fostered a culture of extreme transparency. By removing the pressure of "clocking in," we've found that team members feel more comfortable approaching management for support when needed, as their contributions are valued based on impact rather than attendance. This routine of radical trust has not only made our hybrid work more sustainable but has been the primary driver behind our ability to rapidly expand as a global company.

One challenge that shows up quickly in hybrid setups is the "proximity advantage." People in the office tend to get more visibility, faster decisions, and more spontaneous discussions. That can quietly create unfairness for remote teammates.

A practical way to handle this can be setting a "remote-first meeting rule." Even if several people are in the same office, everyone joins important meetings through their own laptop with shared docs or boards. This keeps conversations structured and documented, and remote team members stay equally involved. For teams working on product builds or custom software development, this also helps because discussions, decisions, and task notes stay recorded inside project tools instead of hallway conversations.

Another routine that often helps is creating fixed collaboration windows instead of random availability. For example, two or three overlapping hours where everyone is expected to be reachable for discussions, while the rest of the day stays focused on deep work. This boundary tends to reduce meeting overload and keeps hybrid teams from feeling like they must always be online. Over time, this kind of structure can make hybrid work feel much more balanced and sustainable.

At JS Benefits Group, we do allow hybrid schedules, but what I've learned is that flexibility only works if expectations are clear.

After COVID, we worked with a client who tried to bring everyone back to the office full time very quickly. The intention was good — they wanted to rebuild collaboration — but the shift felt abrupt to employees who had already adjusted to working differently. It created frustration and, honestly, some turnover they weren't expecting.

That experience reinforced something I believe strongly: hybrid work needs structure, not just flexibility.

For our team, we set clear rhythms for when collaboration happens and when people can focus on independent work. When people know what the expectations are and why they exist, it removes a lot of the tension around fairness.

In my experience, hybrid works best when it's designed around how the team operates together — not just where individuals prefer to work.

The fairness problem with hybrid schedules almost never comes from the schedule itself. It comes from the invisible advantages that in-office people accumulate over time: spontaneous face time with leadership, easier access to information, being thought of first for high-visibility projects. If you don't actively design against that, hybrid quietly becomes a two-tier system where remote days feel like second-class days regardless of what the policy says.

The way we address this is by anchoring decisions and visibility to output rather than presence. Promotions, project assignments, and performance reviews are tied to documented results and peer feedback, not to who was seen in the office most often. We also made one structural rule: no hallway decisions. If a conversation leads to a decision that affects the team, it gets documented and shared in a common channel within 24 hours. That sounds small, but it eliminates the biggest source of resentment in hybrid setups, which is remote employees learning about decisions after the fact and feeling excluded from the process.

The one boundary that made the biggest difference was establishing what we call "anchor days" that teams choose together rather than having leadership dictate. Each team picks two days per week where everyone is expected to overlap, whether in-office or on a shared video block. Those days are reserved for collaborative work: planning sessions, creative reviews, problem-solving meetings. The remaining days are protected for focused, independent work with minimal meetings.

What made this equitable is that the teams themselves decide which days and what format works best for their function. A client-facing team might anchor Tuesday and Thursday in-office. An engineering team might anchor Monday and Wednesday on video. The consistency is in the principle, not the prescription.

Gallup data backs this up: on teams where the hybrid policy is decided collaboratively, 90% of employees report the arrangement feels fair. The moment the policy feels imposed from the top with no input, that number drops sharply. Fairness in hybrid isn't about giving everyone identical schedules. It's about giving every team equal say in how they structure their time and then protecting equal access to information, opportunity, and recognition regardless of where someone works on a given day.

To make hybrid schedules fair and keep collaboration strong, I recommend adopting a single, published operating rhythm as a firm boundary. Specifically publishing core collaboration or operating hours, standing cadences like 1:1s and team standups, and defined decision windows so everyone knows when to be available. Label meeting times and response expectations as non-negotiables, and explicitly mark flex zones where people choose when to do heads-down work. Predictable rhythms reduce ambiguity, protect focused time, and help hybrid teams feel treated equitably.

The simplest way to make hybrid schedules feel fair is to make the rules the same for everyone. If your policy is three days in the office, that applies to every team. The moment one group gets a better deal with no clear reason, trust breaks down across the entire company.

One routine that made the biggest difference for us was setting fixed collaboration days. Everyone knows which days the team is together in the office and which days are for focused remote work. No guessing, no last-minute changes, no feeling like you missed something important because you happened to be working from home.

The key is removing ambiguity. Most hybrid frustration comes from inconsistency, not from the schedule itself. People do not mind coming to the office when they know everyone else will be there and the time will be used for real collaboration. What they hate is showing up to sit on video calls they could have taken from home.

Keep it simple, keep it consistent, and make sure in-office days are actually worth being in the office for. That is the difference between a hybrid schedule that works and one that just annoys everyone equally.