Going remote in the Central Timezone has posed...

Going remote in the Central Timezone has posed some interesting new challenges. After almost 4 years in New York (and the Eastern Timezone), I've had to recalibrate how I schedule meetings in several ways." "" "First of all, I've had to continuously remind myself to subtract only 2 hours instead of 3 when lining things up with my California colleagues. While this isn't that hard, it's so easy to fall back into my habits of subtracting 3 hours to evaluate a meeting time." "" "Second, and more importantly, I've found that not being in the same timezone as another cohort of my peers has been a bit tricky. It used to be far easier to say: "That's lunch hour here in NYC. Can we do this an hour earlier or later?"" "" "Now, I'm one of the only ones taking lunch at 10 am Pacific, and 1 pm Eastern at LinkedIn, so meetings aren't optimized for my schedule. This has forced me to take a handful of lunch meetings in the first few months that I'd typically never allow." "" "Lastly, though, on the positive side, it's extended the window with which I can meet with my peers in California, which used to be a very tight window since I work 8 am-4 pm local time. Before, that meant meetings with CA had to be in their pre-lunch morning chunk of work." "" "That extra hour may not sound like a lot, but it makes a difference. I know I feel it outside of work, where for example, NBA games that used to start at 10 pm and that I could barely stay awake for now begin at 9, and I can more easily watch the entire game." "" "While there've been some challenges, being in the Central timezone has been a net positive for me, both for work and personally! #bendevtip

---

Original post on LinkedIn