In an office, a lot of fairness gets established informally — people see who's been staying late, who took the last inconvenient meeting slot, who's been quietly overloaded. Remote teams lose almost all of those ambient cues, which means the informal fairness a co-located team takes for granted has to become an explicit, visible process instead.
Why fairness perception is harder to build remotely
Without shared physical space, teammates can't observe each other's workload, effort, or mood the way they might in an office, which means trust in "this was decided fairly" has to come from the process itself rather than from ambient social proof. A remote manager who privately decides a task rotation is trusted less by default than one who runs the same decision as a visible, recorded spin on a shared call, simply because there's no other way for a distributed team to verify the process was fair.
Rotating meeting times fairly across time zones
Teams spread across time zones inevitably have to put some meetings at an inconvenient hour for somebody. Rather than always defaulting to whichever time zone happens to include the most senior people, spin to decide which time zone "wins" a given recurring meeting slot, and rotate that decision periodically so the same group isn't permanently stuck with the early or late slot. A visible process here matters more than the specific decision, since a remote employee already inconvenienced by time zones is far more likely to accept it when they can see the rotation was decided fairly rather than assumed by habit.
Distributing async tasks fairly across a distributed team
For teams that work mostly asynchronously, task distribution can't rely on "whoever's in the room and free right now," since nobody's reliably in the same room at the same time. A saved team roster in a wheel gives a remote lead a fast, consistent way to assign asynchronous tasks fairly, without defaulting to whichever teammate happens to respond to Slack first, which otherwise quietly rewards constant availability over actual capacity.
Random pairing for virtual coffee chats
Distributed teams lose the casual hallway conversations that build relationships in an office, and that gap doesn't close on its own. A recurring randomized pairing — two teammates matched for a short, informal video call every couple of weeks — is one of the more effective low-effort ways to rebuild some of that cross-team familiarity, and spinning through the team list with "Remove winner after each spin" turned on generates a full round of fair pairs in one pass.
Making the process visible on video calls
Everything about visibility that matters in person matters more, not less, on a video call. Share your screen while you spin rather than announcing a result after running it privately, and consider recording or screenshotting the spin for anyone who couldn't attend live, so a decision affecting a distributed team isn't only verifiable to whoever happened to be on the call when it happened.
Building trust in distributed decision-making generally
Once a remote team sees a manager consistently use a visible, fair process for the small stuff — meeting rotation, task assignment, pairing — that trust tends to extend to bigger decisions too, since the team has direct evidence of how decisions get made rather than having to take it on faith. This matters more for remote teams precisely because there are fewer other signals available to build that trust incidentally.
Fairness across a mix of remote and in-office staff
Hybrid teams add a specific risk: in-office staff can end up with more informal access to decision-makers simply by being physically present, while remote colleagues only see the formal, documented version of how things get decided. Running fairness-relevant decisions through a shared, visible tool like a wheel — and doing it on the same video call everyone joins, rather than deciding informally in the office first — helps close that gap rather than widen it.
Adjusting for asynchronous time zones
When a decision genuinely can't wait for a live call where everyone's present, record the spin (a short screen recording works fine) and share it in your team's usual async channel along with the entry list that was used. This preserves the same visibility a live spin would have provided, just delivered on each person's own schedule instead of requiring real-time attendance across every time zone involved.
Handling disagreements about a remote decision
Even a fair, visible process won't eliminate every disagreement about an outcome — someone can still end up unhappy with which time-zone slot they got, or which task landed on their plate. What a visible spin does change is the shape of that conversation: instead of arguing about whether the decision was made fairly, the discussion can move straight to the substance, such as whether an exception makes sense this one time, which is a considerably easier conversation to have in good faith.
Onboarding new remote hires into the process
A new remote hire has no history with how the team makes these decisions, so it's worth explaining the process once, early, rather than letting them discover it mid-rotation and wonder why a wheel is involved. A short note in onboarding material — "we rotate meeting times and tasks with a visible spin so nobody gets stuck with the inconvenient slot every time" — sets the expectation before they've had a chance to assume the opposite, that things get decided informally by whoever's most connected.
Combining fairness tools with regular check-ins
A random, visible process handles the specific moment of a decision, but it doesn't replace the ongoing work of checking in on how a distributed team is actually doing — whether the rotation feels sustainable, whether the time-zone trade-offs still feel balanced a few months in. Pair a visible spin for the decision itself with a periodic, direct question to the team ("is this rotation still working for everyone?") so the fairness of the process gets revisited, not just assumed to hold indefinitely once it's set up.
Practical setup for remote teams
- Keep your full distributed team roster saved in SpinPick, ready for any decision that needs a fair, visible process.
- Screen-share the spin on every video call where a decision is being made, rather than deciding privately and announcing a result.
- Use "Remove winner after each spin" for full-round decisions like pairing or a complete meeting-slot rotation.