Most distributed-team scheduling problems are structural, not personal. These essays diagnose where the structures pull, and what teams can do about them, usually without new tooling.
A diagnostic essay on the drift that lands rotating meetings on the same one or two people every time. It isn't favouritism, it isn't a scheduling-tool bug, and it almost never gets noticed until someone quits. Five structural reasons it happens, the four properties a real fix has to have, and the five-minute retro exercise that catches most of the drift without any new tool.
A 6-person team on a 6-week rotation looks fair on paper. Then you actually count what each person absorbed, and one of them did roughly twice the work. Why weeks-of-rotation is the wrong unit, what to measure instead (out-of-hours minutes per quarter), why follow-the-sun isn't a fix, and the four operational moves that hold.
An explainer of the four-dimension model that powers FairlyRemote: accommodation, flexibility, social time, and rest quality. Why scheduling tools that don't model sleep produce unfair meeting times, what monthly accommodation budgets do, how the decay function keeps last year's history from haunting this year's votes, and what the score explicitly does not predict.
Sample team loads instantly. Five members, four timezones, three months of data. No signup.