This summer, we faced an unexpected challenge at BandOne that organizations large and small navigate every day: how to work effectively across time zones.
Yael’s brief trip to Israel turned into a two-month stay, thanks to the realities of traveling during a war, government bureaucracy, and unplanned family opportunities. Meanwhile, Gary was back in Central Time with the rest of the BandOne team.
The basic to-dos of transcontinental work were easy enough to master: double-check meeting times, remember the Sunday-through-Thursday workweek in Israel, and take advantage of opportunities to meet colleagues and new contacts there in person — and without translation.
But the more important lesson — valuable whether you are eight hours apart or ten minutes away — was recognizing the role of synchronous and asynchronous time in any communication architecture. Two things stood out.
First, scarce synchronous time should be reserved for judgment, creativity, and working through ambiguity.
With limited overlap, time together became a precious resource. We often used it to pressure test ideas that seemed brilliant when we had developed them in isolation.
Monday mornings in Austin became especially valuable. Gary was beginning the week while Yael was wrapping up her second full day, able to hand off work that had advanced while Austin slept.
Second, good asynchronous communication requires an attention threshold — not just more information.
It’s easy to forward emails or send WhatsApp messages when something crosses your mind and your colleague is off the clock. That may feel like communication, but it can overwhelm an inbox pretty quickly without signaling what actually matters.
Instead, we focused on a daily handoff email flagging what had changed, what needed attention, and what could wait. The value wasn’t in sending an update; it was in deciding what belonged in it.
Would knowing this piece of information cause us to make a different decision or prioritize something differently before we next speak? If not, it could probably wait. That helped turn asynchronous communication from a running transcript into a way to surface what actually required attention.
Throughout it all, there were moments of frustration and days we felt we were working double time.
But the experience reinforced something we talk about daily with the organizations we support: good communication isn’t simply about sending more information. It’s about creating structures that help people stay connected, understand what matters, and work together effectively — whether they’re eight hours apart or sitting across the table.