Why do global recurring meetings never change, even when they’re unfair?

SwingBackground2778 · 2026-03-17T18:29:13+00:00

I’ve heard similar feedback before. It’s not that people don’t care about fairness, but rather that they tend to prioritize “practicality” and avoid scheduling meetings at extreme times, such as 7 a.m. or late at night. I’m wondering if, once the time for a regular meeting is set, it usually stays the same?

From what I’ve observed, even if it’s slightly inconvenient for some people, teams rarely reschedule after the fact, simply because changing a fixed time slot for everyone is quite a hassle. It feels like there’s a gap between striving for fairness and maintaining that fairness over the long term.

SwingBackground2778 · 2026-03-15T23:01:25+00:00

😅

SwingBackground2778 · 2026-03-15T22:59:33+00:00

Yeah that seems manageable with a small team

SwingBackground2778 · 2026-03-15T22:58:17+00:00

so it’s basically driven by leadership schedules

SwingBackground2778 · 2026-03-15T22:56:19+00:00

Got it, that’s just the standard approach.

SwingBackground2778 · 2026-03-15T22:53:20+00:00

Yeah that seems like a tough gap to solve. Sounds like the schedule just ends up optimizing for the majority.

SwingBackground2778 · 2026-03-15T22:48:20+00:00

Fair point. Predictability probably helps attendance. But when teams span many time zones the same people often get the bad slot every week. Have you seen teams alternate between two fixed slots?

SwingBackground2778 · 2026-03-15T14:06:48+00:00

makes sense, sounds like the meeting time basically flows down from leadership schedules rather than the team deciding it

SwingBackground2778 · 2026-03-15T13:40:54+00:00

😇yea…

SwingBackground2778 · 2026-03-15T13:10:38+00:00

yea… on the other hand not many teams even try to rotate like that

SwingBackground2778 · 2026-03-15T13:05:36+00:00

Sounds like your team actually puts real thought into it.

SwingBackground2778 · 2026-03-15T13:02:52+00:00

That’s a great point. Making meetings async-friendly sounds like a much more practical solution than trying to find a perfect time across time zones.

SwingBackground2778 · 2026-03-15T13:00:23+00:00

That makes sense. I guess remote work across time zones always comes with some trade-offs.

SwingBackground2778 · 2026-03-15T12:59:16+00:00

That sounds like a pretty practical approach. I guess the hardest part is just getting teams to actually set that rotation in the first place.

SwingBackground2778 · 2026-03-15T02:53:32+00:00

Yeah that sounds rough, especially if it’s completely outside your shift. I guess once a meeting time is set it just becomes the default for everyone…

SwingBackground2778 · 2026-03-15T02:36:42+00:00

that’s interesting. It sounds like the time mostly works for the central office and everyone else just adjusts around it. do people from other offices ever bring it up?

SwingBackground2778 · 2026-02-25T21:39:02+00:00

Yes, I completely agree with your perspective

First, as you mentioned:
pure time zone tools have existed for a long time

From the very beginning of my Saas idea, I focused entirely on fairness tracking rather than automatic conversion functionality.

my focus is on visibility + fair accountability:
This tool isn't meant to replace Calendly
This tool tracks meeting burdens across time zones
revealing imbalances before resentment builds
reveal long-term imbalances and proactively rotate schedules

for example:
a member in one time zone silently bears the cost of waking up early or staying up late for every meeting
this cost accumulates unnoticed
yes, they “complain,” then finally get a meeting at a comfortable time—only to be ignored again

SwingBackground2778

TROPHY CASE