JS
RS
BS
IL
CC
CV
KW
10 people answered: RHILLANE, Joe, Roman and 7 more
Measure Results, Not Presence
We have three offices in different countries with different norms around remote work, so full fairness in the sense of identical rules was never going to happen. What we protect instead is equal visibility: every team member's work shows up in the same weekly scorecard regardless of where or how they worked, so nobody has to be seen at a desk to be seen as productive.
The tension usually shows up around promotions and opportunities, not schedules. A remote team member in Morocco can start feeling invisible next to someone who's in the room for every client call, even if their output is identical or better. We fixed that by making sure results, not presence, drive the review conversation, and by rotating who joins client calls so visibility isn't accidentally handed to whoever happens to sit closest to the door.
The policy that actually reduced tension wasn't a flexibility rule; it was making the measurement of good work the same no matter where someone did it. People stop resenting each other's schedules once they trust that the schedule isn't what's being judged.
Offset Onsite Sacrifices With Tangible Benefits
I learned this the hard way when half my fulfillment team could work from home and half couldn't. You can't exactly run a forklift remotely.
The tension was real. Our warehouse staff saw office employees working from their couches while they drove through snowstorms to pack boxes. One morning my warehouse manager pulled me aside and said three of his best people were interviewing elsewhere because they felt like second-class employees. That conversation cost me about 40 grand in retention bonuses, but it taught me something crucial.
Here's what actually worked: radical transparency about why roles differ, combined with offsetting perks that acknowledge the inequality. I started holding monthly all-hands meetings where I explicitly said, "If your job requires you to be here physically, you're making a bigger sacrifice than someone who can work in pajamas. That's not fair, and I'm not going to pretend it is."
Then we backed it up. Warehouse staff got first pick of vacation dates. Period. They got premium parking spots. We added an extra week of PTO specifically for onsite roles. When the office team wanted to do a virtual happy hour, I made them do it onsite so warehouse staff could actually join. Small stuff, but it signaled that flexibility wasn't the only currency we valued.
The policy that reduced the most tension was simple: no hybrid employee could schedule an onsite-only meeting without my approval. Remote workers had to come in for quarterly planning, but we protected warehouse staff from endless "quick syncs" that pulled them off the floor.
The real shift happened when I stopped trying to make it fair and started making it equitable instead. Fair would mean everyone gets the same thing. Equitable means people get what they need based on their constraints. Once I named the imbalance out loud and compensated for it tangibly, the resentment disappeared. People respect honesty about inequality way more than fake equality that ignores reality.
Set Visible Response Expectations
In our team, fairness comes from knowing when people are reachable and who owns the next answer, especially when one role can work quietly from anywhere and another role needs more live coordination. The communication choice I'd protect is a visible response expectation: a project manager must answer within 24 hours on business days, and we ask the same from clients; inside the company, the same expectation is mandatory. That rule works because it treats flexibility as a communication contract. If someone is onsite, remote, in meetings, or deep in delivery work, the team still knows when silence becomes a problem and who should move the thread forward.
We pair that with a single point of contact and a weekly report that says what changed, how much work was spent, and what happens next. For hybrid teams, the report matters because it gives everyone the same project reality at the same time. The onsite person should never become the unofficial source of truth because they happened to hear something in the office, and the remote person shouldn't have to chase context through private messages. Give remote and onsite people the same written decision log, the same response window, and the same owner for the next step.
Adopt a Digital-First Meeting Protocol
Equitable treatment in distributed workforces is not a question of equal workplace policies, but of equal access to power and information. As I have learned in working with global delivery teams from various time zones and office centers, resentment often arises due to proximity bias, which restricts information flows to the people who are closest to the office. In order to support cohesive teams, we stopped focusing on where our employees do their work and started looking at how their performance is monitored through a standardized digital process. When performance is measured based on objective criteria instead of the employee being present in a specific place, the issue of flexibility almost disappears since it is possible to see how each employee performs.
The Digital-First Meeting Protocol was one of the key policies that helped us alleviate the level of tension in our organization. According to this policy, all people must participate in a meeting from their own device as long as at least one participant is remote. As a result, the problem of "room-within-a-room" disappears. With this policy in place, everybody shares the same digital environment where their input is just as important as that of their counterparts who work from the office.
It is worth noting that this policy, when paired with the fact that all communication is documented and takes place asynchronously, helps build trust within the organization. It communicates to the onsite workers that being physically present does not necessarily mean being in favor, while the remote team can count on equal opportunities for advancement.
Explain Role-Based Flexibility Boundaries
Fair does not always mean identical. It means people understand the reason behind the difference.
The policy was to keep a small set of shared expectations for the whole team, then allow flexibility inside those boundaries based on the realities of each role. In both the agency and Slickplan, work that required rapid back-and-forth across several people was generally better in person, while individual execution that did not require constant collaboration was often better with uninterrupted remote time. We were deliberate about bringing remote employees into the discussion instead of letting the people physically in the room dominate it. That made the tradeoff easier to understand, and we kept the benefits of flexibility without losing the collaboration we actually needed.
Document Onsite Flexibility Arrangements
Most of the tension I have seen does not come from the policy itself. It comes from one group's flexibility being written down while the other group's stays invisible.
When we formalised remote working, the roles that have to be at a desk at set times read that document and saw something they were not getting. What nobody had written down was everything those roles already had informally: a school pickup, a swapped afternoon, a quiet hour with the phone diverted, an early finish after a heavy week. None of it was official, which meant it felt like a favour rather than a right, and favours breed resentment where entitlements do not.
So we wrote the second list. Every piece of informal flexibility the onsite roles already used got named, put in the same document as the remote arrangements and given the same status. Nothing new was granted. The only change was that it stopped being invisible. Roughly 40% of what ended up on that list had never been formally requested by anyone.
The communication choice that mattered was refusing to call any of it a perk. These are working arrangements attached to the shape of a job, and different jobs have different shapes. Once the two lists sat side by side, the arguments about who had it easier mostly stopped, because people could see the trade instead of guessing at it.
Cohesion came from the honesty, not from making the two things equal.
Share Schedules to Show Tradeoffs
My cleaning teams are never hybrid. They're in a house that day, or they're not working. A house has to get turned between checkout and the next guest, so someone has to be standing in it. The office side that handles scheduling and messages does get some flexibility. Pretending that gap doesn't exist is what breeds resentment. Fairness here is staying honest about what each side traded for what they got. Field crews trade flexibility for a locked, predictable weekly schedule. They see it at the same time office staff sees theirs, on one shared calendar. Nobody's hours get set behind a closed door. The communication choice that reduced tension was small. Every schedule, hybrid and onsite, sits in one place everyone can check. Once people can see the trade instead of guessing, the gap stops reading as favoritism. Cohesion holds because people can watch that trade play out the same way, week after week, and it's what has kept trust high on my crews.
Build Empathy Through Cross-Role Shadowing
I maintain fairness and cohesion by implementing a scheduled cross-role shadowing policy so hybrid and onsite team members understand one another's work. At MyRenoService, we had designers shadow project coordinators and estimators learn basic design tasks, which let people represent different sides of a project to clients. After a few weeks, this led designers to draft concepts and price them and helped estimators answer design questions, and it increased client trust. When everyone can step into each other's workflows, differences in flexibility feel like shared responsibility rather than privilege, which reduced internal friction and cut down on repeated handoffs and unnecessary work.
Standardize Location-Blind Recognition
Most of the resentment between hybrid and onsite teams is not really about who gets to work from home. It is about who gets seen.
Onsite people watch remote colleagues seem to have more freedom. Remote people watch onsite colleagues get the casual credit that comes from being in the room. Both groups end up feeling like the other one is getting the better deal, and no flexibility policy fixes that, because the policy is not the source of the friction.
The one change that reduced it for us was making recognition location-blind and consistent. Same milestones for everyone. Same awards, same value, same timing, whether a person is at a desk in the building or three states away. Milestone dates run off an automated trigger so nobody's anniversary depends on their manager's memory or their proximity.
Then we made recognition visible in a shared channel rather than delivered in whatever room the person happens to be standing in. When onsite staff see remote colleagues recognized specifically and by name, and vice versa, the "they have it easier" story loses its footing, because everyone can see the work being named.
Flexibility can differ by role. Recognition should not. Once people trust that being present is not the same as being valued, most of the tension over schedules quiets down.
Publish Decision Criteria and Appeal Channels
Employees rarely expect every role to look the same, but they do expect leadership to be intellectually honest about why differences exist. In a bootstrapped environment, every policy competes with throughput, training load, and retention risk, so vague language creates unnecessary cost. Fairness improves when leaders explain the system in plain terms: what must happen in person, what can happen asynchronously, and what evidence would justify changing a role's flexibility.
The communication move that helped most was replacing broad culture language with decision criteria and appeal channels. I saw less friction once employees knew how to question a classification without creating a political issue. That matters because trust is not built by promising equality of arrangement; it is built by making decisions legible, reviewable, and consistently applied.