Lessons From Working Across Time Zones

1. Working From Japan Under WFA

With the flexibility of the company’s Work From Anywhere (WFA) policy, I decided to spend some time working from Japan. The policy allows 20 days per year from any time zone, without a strict requirement for overlap — which makes it meaningfully different from “remote, but mostly the same.”

Working from Japan introduced a large time difference and quietly changed how collaboration worked. Many of the informal habits I had relied on — quick clarifications, spontaneous calls, filling gaps verbally — were no longer guaranteed. If something wasn’t clear enough in writing, it would simply have to wait.

That shift didn’t break the workflow, but it did make its weaknesses visible. It forced me to pay attention to how much context lived only in my head, how often decisions depended on availability, and how rarely I left durable explanations behind. Instead of fighting that change, I used it as an opportunity to rethink how I communicated and structured my work so it could stand on its own.

2. When Time Zones Remove Communication Shortcuts

Once I was working from Japan, the most noticeable change wasn’t the schedule — it was the loss of immediacy. Questions no longer bounced back in minutes. Clarifications couldn’t be resolved with a quick message or a short call. If something was ambiguous, it stayed ambiguous until the next window of overlap.

That delay changed the dynamics of communication. Details that might normally be clarified quickly now required more care up front. Without that, progress tended to pause rather than correct itself organically.

This made one thing obvious very quickly: communication that only works in real time is fragile. To keep work moving, I had to be much more explicit — not just about what needed to be done, but why, with which constraints, and what decisions were already made. Writing stopped being a summary of conversations and became the primary way work progressed.

3. When Availability Changes Team Dynamics

The most interesting shift didn’t come from my mentoring intentions at all — it came from my absence. While I was working from Japan, I wasn’t readily available for ad-hoc questions from my managers. There was no implicit “we can just ask Gil” anymore.

Those questions didn’t disappear. They simply went somewhere else.

At that moment, the person consistently available in the team was the junior developer I was mentoring. So, naturally, the dynamic shifted from “let’s ask Gil” to “let’s ask Raúl.” Not because of a formal decision or a role change, but because there was a need for higher autonomy.

That small change had a cascading effect. Being the first point of contact meant he had to understand the context more deeply, make calls instead of escalating them, and represent the team’s work with confidence. Responsibility didn’t get assigned — it emerged.

4. Responsibility Through Absence

Looking back, my absence acted a bit like a bus factor exercise — but without the damage. I wasn’t gone, the project wasn’t at risk, but the team had to function without the usual fallback of asking me. The system was being tested gently, in a controlled way.

That’s what created the space for growth. With questions and decisions flowing toward him, the junior developer had to step into situations he wouldn’t have reached otherwise. He had to reason things through, commit to answers, and stand behind them. Growth didn’t come from extra tasks — it came from being relied on.

At first, that was uncomfortable. Letting go of availability requires trust, and trust is hard to extend before it’s been earned. There’s always the fear of things going wrong, of decisions being made differently than you would have made them. But that discomfort turned out to be necessary.

That moment was an inflection point. Once he had been the person others depended on, he didn’t revert back. His confidence, judgment, and presence in the team shifted permanently.

In hindsight, none of this is surprising. It’s exactly how I grew as a developer myself — by being forced to take responsibility when there was no safety net. The difference here was the stakes. WFA created a middle ground: enough distance to encourage growth, but enough safety to make it a constructive experience rather than a risky one.

5. One Year Later

I’m writing this with the benefit of distance and time. A year has passed since that first experience, and the change in my mentored junior developer isn’t just noticeable — it’s consistent. The shift in ownership, confidence, and judgment didn’t fade once I was back in the same time zone. It became part of how he works.

Over the course of this year, I repeated the same setup more than once, and the results were similar each time. Different moments, same pattern. There were always doubts — from colleagues, and from myself. Letting go of availability still feels uncomfortable, and it challenges deeply rooted ideas about how support and mentoring are supposed to work.

Despite that resistance, it’s worth pushing through. Creating a bit of distance turns responsibility into something that is exercised, not assigned. It gives people room to grow in ways that are hard to manufacture deliberately.

6. Closing Thoughts

The funniest part, in hindsight, is how prepared I thought I was. Before traveling, I had consumed a lot of content about solo travel in Japan. I felt like I already knew what I was going to find. Reality quickly corrected that assumption.

Each experience is uniquely personal. No amount of online content replaces being there, making choices, and reacting to what actually unfolds. Reality is far richer than any curated narrative — and consuming information at scale can be surprisingly myopic. That applies as much to work as it does to travel.

It also changed how I moved through Japan. I stopped chasing tourist checklists. Instead, I opened Google Maps, picked something that caught my eye — often a park, a mall, or a neighborhood — and walked. I went into bars without a plan. People talked. Things happened. A single street away from the highlights, Japan felt entirely different.

The idea that Japan is “overcrowded with tourists” fades quickly when you remember how many people actually live there (Does not apply to Nara, sorry.)

In the end, this experience gave me growth I hadn’t anticipated — professionally and personally. Distance reshaped how I communicate, how I mentor, and how I trust others. Japan turned out to be an unusually good place to try this for the first time: safe, comfortable, and well-organized, yet foreign enough to feel like a real adventure.

7. Key Takeaways

Working across time zones clarified a few things that are easy to miss in day-to-day work:

• Seniority attracts responsibility — and can block growth. As the most senior developer, larger or more complex questions naturally flowed to me. That efficiency came at a cost: it quietly removed learning and ownership opportunities from others.

• Clarity scales better than immediacy. Communication that depends on quick back-and-forth doesn’t survive distance. Clear, written context does.

• Responsibility grows through use. Growth doesn’t come from delegation alone, but from repeatedly being relied on in real situations.

• Trust precedes proof. Letting go feels risky before it feels obvious. That discomfort is often part of the growth process.

• Experience beats theory. Just like travel, mentoring and leadership only reveal their real shape when lived, not observed.

In the end, working across time zones didn’t add complexity — it redistributed responsibility and made growth visible in ways that proximity had been quietly preventing.