The Mountain Time grind: why shifting your clock actually changes your output
I spent three years running a distributed team spread across California, New York, and Denver. We tried every scheduling tool, every time-tracking app, every pomodoro hack. What actually moved the needle wasn't a framework or a piece of software. It was switching our core operating hours to Mountain Time and treating it like a real constraint instead of a novelty. Utah Time isn't a formal methodology. There's no textbook. It's the informal practice of using the Mountain Time Zone as a coordination anchor for knowledge work that spans multiple US time zones. The logic is blunt: Mountain Time overlaps with Pacific morning AND Eastern afternoon without completely destroying either side. It's the median of the country's working population. Most people think this is about geography. It's not. It's about eliminating the commute between time zones in your calendar. When you schedule everything around MT, you avoid the situation where a developer in SF has to choose between a 6 AM standup or a 9 PM review. You just pick one anchor and live there.
I learned this the hard way. We had a product launch scheduled across PST and EST. Our engineering lead was on calls until 10 PM three nights a week. Burnout wasn't coming; it was already here. Someone suggested we move all mandatory meetings to a Mountain Time window. I pushed back because it seemed like extra administrative overhead. That was my mistake.
Setting it up without making it worse
The actual setup is simpler than most guides make it. You pick 8 AM to 4 PM Mountain as your core collaborative window. That's 6 AM to 2 PM PST and 10 AM to 6 PM EST. Everything synchronous happens in that band. Everything asynchronous happens outside it. That's it. What people get wrong is the async part. They treat async as a backup plan instead of the primary mode of communication. The async pieces should carry the bulk of the work. Meetings are for decisions that can't be made through documentation. If you're holding a meeting to "sync up," you've already lost. You need tooling that respects the window. We used a mix of Slack with forced timezone display, a shared calendar that defaulted to MT, and Loom for anything that wasn't urgent. The calendar default mattered more than anything else. When new events auto-populate in Mountain Time, people stop accidentally booking at 8 AM their local time. It removes friction without requiring willpower.
Get the Full Details
Where this actually breaks down
This approach fails if your team includes people in Hawaii or Alaska. The overlap becomes too thin. You're better off running two separate windows or accepting that some people will always be slightly out of sync. We had one contractor in Honolulu who stayed on the MT schedule for six months before asking to move. I let him. He was producing fine work, just on a delayed cadence. It didn't hurt the project. It also fails for teams that depend heavily on real-time collaboration. Design reviews, live coding sessions, crisis management. If your workflow requires simultaneous input from multiple people, Mountain Time doesn't solve that. You still need overlap, and sometimes that overlap looks like early mornings or late nights regardless of where you anchor. Another edge case I ran into: legal and compliance teams. They operate on their own clocks, usually Eastern. When we shifted to Mountain, we had conflicts around filing deadlines and regulatory windows that were defined in Eastern Time. The workaround was simple but annoying. We kept all external-facing deadline tracking in EST while keeping internal work in MT. Two clocks, one system. Don't overthink it.
The numbers behind it
We tracked meeting hours for four quarters before and after the switch. Average weekly synchronous meetings dropped from 18 hours to about 9. Decision latency improved by roughly 40 percent, measured as time from question to resolution. Not because people got faster, but because the questions stopped getting lost in timezone whack-a-mole. Turnover in engineering dropped noticeably after the first full quarter. Hard to attribute entirely to the time shift, but the feedback was consistent. People weren't working less. They were just working at hours that matched their circadian rhythms instead of fighting them.
What to do if you're starting from scratch
Pick Mountain Time as your anchor. Declare it publicly and don't apologize for it. Set your calendar defaults. Kill meetings that don't require live presence. Build your async infrastructure first and treat synchronous time as the exception, not the rule. That's the whole thing. There's no download link. There's no tool you can install. It's a scheduling decision that requires enough organizational discipline to actually enforce it. Most teams try it for two weeks and then drift back to whoever has the loudest Slack presence. If you can hold the line for a quarter, you'll know whether it works for your setup.
