CHROs Share Moves That Make Hybrid Work Policy Feel Fair and Sustainable

I focused on fairness by setting a consistent baseline that applied across teams, then using in-person time intentionally for the work that benefits most from being together. Not every role needs the same days in the same place, so the goal was to keep expectations predictable while still making room for real collaboration when it mattered. One ritual that helped schedules feel sustainable was our monthly virtual happy hour and game night, which gave everyone a reliable way to reconnect regardless of location. Having that shared touchpoint reduced pressure to force extra office days just to maintain culture. It also made the rhythm feel consistent for remote and in-person teammates alike.

As the Hybrid Working Lead for hybrid working models across technical operations, customer support and development, for multiple teams across TradingFXVPS since 2021. Modelling the challenges of managing 24/7 trading infrastructure monitoring while accommodating the flexible working preferences of both employees and stakeholders.

I setup role-based scheduling to reflect the varied needs of different jobs. Our full-time, infrastructure engineers who manage our MetaTrader servers spend most of their time remote, but work a single week out of year in various shifts of a few hours on a single day each week to check cables and swap out failed disks etc. in our facilities. Support is 100% remote as they support traders all over the world at all times of day. Sales and business development is 3 days in office where we meet with clients and discuss strategy with other teams.

Fairness was achieved by choosing "core collaboration hours" of 10am-2pm local time, three days a week, and ensuring that all teams were available for real-time communication, in-office or virtually, during those hours. This ensured that the biggest pain point of coordinating between teams during outages and critical issues with the trading platform related to rapid response could be addressed.

To make this approach sustainable we decided to implement monthly "infrastructure days." On these days all technical teams come together in-person for architectural discussions, planning and training on new functionality and upgraded processes. Non-technical teams participate in-person or virtually depending on the relevance to their roles and work. Regularly scheduled "infrastructure days" enable teams to come together in-person on a recurring basis while maintaining flexibility for other commitments.

We operate 24/7 around the clock and have maintained 99.99% uptime for our VPS services. This shift in model has already resulted in a 40% decrease in staff turnover. Predictability is a huge aspect, because, while the nature of our work is vastly different from traditional office work, we still need to have presence models for monitoring trading servers and supporting our algorithmic traders.

When setting hybrid expectations, I balanced fairness by combining employee input with clear follow-through so role differences were discussed and addressed rather than imposed. This ensured in-person days were tied to genuine collaboration needs and not arbitrary rules. One ritual that made schedules feel consistent and sustainable was a regular cadence of collecting team feedback and then publishing the agreed schedule and the rationale. That visible link between voice and action built trust and kept plans predictable for most teams.

Honestly, there aren't too many things that we do that require entirely in-person collaboration. We've made an intentional effort to make the work we do possible to accomplish remotely or with hybrid teams. That alone helps with fairness, because it allows for our employees to remain remote or maintain a consistent hybrid schedule without having to worry about needing to come into the office one day because there is a certain project that requires everyone to be in-person.

It can be difficult to effectively achieve fairness with something like this if you are making decisions unilaterally. That's what I've learned as a leader. It's much more effective to involve your team in the conversation so that they can explain what they need collaboration-wise and what they think would work best for schedules in order to accomplish that. Working with your team to figure this out will lead to a better outcome, and it will help with morale too, since they'll know that you value their opinions.

That tension between fairness and function is real - a hybrid only works when people feel the system is consistent, not negotiated case by case. I've found the balance comes from being explicit about why certain roles need more in-person time, and applying that logic transparently across teams rather than framing it as preference or seniority.

Instead of mandating identical schedules, we defined role-based "anchors": clear expectations tied to the nature of the work (for example, collaboration-heavy roles spending more time in-person during key project phases). The key is documenting this openly so people see the rationale, not just the outcome. One ritual that made this sustainable was setting fixed "team overlap days". Everyone knew, for example, that Tuesdays and Thursdays were in-person collaboration days, while the rest of the week allowed for flexibility. That removed constant coordination overhead and made planning predictable.

At Tinkogroup, this structure helped us avoid ad hoc exceptions and made the hybrid feel intentional rather than uneven - people could plan their work and lives around a system that felt stable and clearly thought through.

The decision that made hybrid work actually sustainable for us was deciding not to do hybrid at all.

We're a fully distributed web agency, with team members in Costa Rica, the U.S. East Coast, and India. When I was setting expectations for how we'd work, I briefly considered keeping a hybrid option for U.S. team members so people could meet in person occasionally. I didn't do it. The moment you have some people in a room and some people on a screen, you've created two classes of employees, and the screen ones are always at a disadvantage. Information flows before and after the meeting, in hallway conversations and whiteboard residue, and remote team members only see the formal middle. That's the fairness problem nobody talks about in hybrid. It's not about schedules. It's about which conversations count.

The ritual that's made the schedule feel fair is locking the business to one time zone. Every calendar invite, every deadline, and every team communication happens in Eastern Time. Nobody has to translate between their local time and someone else's. We lock to a single business clock, and the team can arrange their days around it however they want. Our India team has one standing weekly call at a time that works for both sides, and the rest of our collaboration happens asynchronously through a project management system we built ourselves. Nothing is urgent unless we've defined it as urgent, which is rare.

The other piece I've held firm on from the start is that I absorb the time zone gaps. If an early call is needed with our India team, I'm on it. If a client on the East Coast wants a late meeting, that's mine. As the owner, that flexibility burden is my job, not the team's. When that burden gets pushed out to employees, they quietly burn out, and you don't find out until they're halfway gone.

If I were advising a leader setting hybrid expectations for the first time, I'd say the real question isn't which days people come in. It's whether you're willing to design away from the thing that almost always makes hybrid unfair, which is an information asymmetry you can't see because you're the one with the information.

The fairness problem inside hybrid work is rarely about where people sit. It is about which meetings default to the in-office experience and which accommodations are made for the people who are not there. If the most important conversations keep happening in hallways and whiteboards, remote members of the team will quietly lose ground regardless of what the official policy says. The fix is usually to make the digital experience the default rather than the exception. Meetings that matter happen with every participant on video, not half the room on a conference speaker. Decisions get written down in a shared place where everyone can see them. Collaboration rituals are scheduled rather than assumed. What makes a hybrid schedule feel fair is predictability and a sense that the standards are the same for everyone. Flexible is good. Ambiguous is corrosive. The companies getting this right are clear about what the expectations are, then consistent in how they hold to them.

GpuPerHour is fully remote, but the fairness challenge applies to us in a different form: balancing expectations between roles that have very different work patterns. Our infrastructure engineers handle urgent on-call incidents that can happen at any hour, while our business development team operates on a more predictable schedule tied to customer time zones. Creating consistent expectations across those roles required intentional design.

The decision that made the biggest difference was defining core collaboration hours rather than mandating full schedules. We have a four-hour daily window where everyone is expected to be available for synchronous work. Outside that window, people manage their own time based on their role's demands. For engineers, that might mean shifting their deep work to early mornings or late evenings when systems are quieter. For the sales team, it means stacking customer calls outside the core window so the shared hours stay open for internal collaboration.

The fairness issue came up specifically around on-call rotations. Our infrastructure engineers felt it was unfair that they carried pager responsibility while other roles did not have equivalent after-hours obligations. We addressed this by compensating on-call time explicitly rather than treating it as an unspoken part of the engineering role. We also limited on-call rotations so no engineer is on call more than one week per month, and we give a full recovery day after any rotation that included a middle-of-the-night incident.

The ritual that made schedules feel sustainable was a monthly "working norms" retro where any team member can raise friction points about how schedules and expectations are working. This is separate from our regular sprint retros and focuses exclusively on the meta question of whether our work patterns are still serving people well. About half the time nothing changes, but the existence of the forum means problems get surfaced early instead of festering into resentment.

The principle is that fairness does not mean identical schedules. It means equivalent consideration for different roles' realities.

I'm Runbo Li, Co-founder & CEO at Magic Hour.

Fairness in hybrid work isn't about giving everyone the same schedule. It's about giving everyone the same clarity. The moment you try to create one universal policy that treats every role identically, you end up with a rule that fits nobody well and frustrates everyone equally.

David and I built Magic Hour to millions of users as a two-person team. We're remote-first by nature, not by trend. But even at our scale, we learned something critical early: async by default, sync by intention. That's the principle. Every interaction should default to async, written communication. When you need to be synchronous, whether a call or in-person session, it should be deliberate and scheduled, never ambient.

The one ritual that made everything sustainable was what I call the "72-hour pulse." Every 72 hours, we have a structured sync. Not a status update. Not a standup where people recite what they did yesterday. It's a decision-making session. We walk in with a list of open decisions, we make them, and we leave. Everything else, the context, the background, the data, lives in written docs that get shared beforehand. If something doesn't require a real-time decision, it doesn't get a meeting.

When I talk to founders running larger teams with mixed roles, like engineers who can work from anywhere and ops people who need to be on-site, I tell them the same thing. Don't try to make the schedules identical. Make the *communication architecture* identical. Everyone gets the same access to context, the same decision-making windows, the same written record of what was decided and why. A warehouse manager and a remote designer will never have the same Tuesday. But they can both know exactly what's expected of them and when their input matters.

The biggest mistake I see companies make is confusing physical presence with collaboration. Sitting in the same room doesn't mean you're collaborating. Having a clear decision framework does. The companies that win at hybrid aren't the ones with the best office perks or the most flexible PTO. They're the ones where nobody has to wonder what's going on.

Consistency doesn't come from identical schedules. It comes from identical expectations around how decisions get made and how information flows.

The thing we got wrong early at Pin was treating hybrid fairness like a scheduling problem. We spent a lot of time trying to map out which roles 'needed' in-person vs. which ones could work anywhere, and it created more friction than it solved, because people were arguing about role definitions instead of what the work actually required.

What changed it for us was shifting from role-based rules to output-based agreements. Each team lead and their direct reports picked two or three things that genuinely worked better in-person, things like whiteboard planning sessions or new hire onboarding, and those anchored the schedule. Everything else stayed flexible. The ritual that made it stick was a short monthly check-in where we'd ask whether the in-person moments were still pulling their weight. A few got cut, a couple got added, and nobody felt like the rules were arbitrary anymore.