Fantastic Beasts and How to Align Them: A Technical Writer’s Guide to Extreme Time Zones (Ep. 2)

You may remember my article from two years ago about working with big time zone differences. This article is the second episode of a Technical Communicator’s experience working in a distributed team with a 10-hour time zone difference.

If you prefer a summary, here is the TL;DR: In the article linked above, I explain the life of a Technical Writer on a team with large time zone gaps. I share how it changes my communication and planning. I use strategies like independent work and flexible schedules to stay on top of my workload.

My project ended shortly after that article was published. I spent two months waiting for my next assignment. In that downtime, I rediscovered the joys of “normal working hours” — starting at 9:00 am instead of 11:00 am, finishing at 5:00 pm instead of 7:30 pm. Suddenly, my evenings weren’t just about dinner and reading before bed. I had time to meet with friends, run errands, or enjoy hobbies for hours on end.

Understandably, I had high hopes for my next project. I wanted something that would fit into my rediscovered normal schedule. Instead, my career path handed me chaos, burnout, and a new time zone twist. This time I was in Europe, and my team was in Australia. This may not sound impressive on its own, so here is an illustration of the time zones.

Let’s add the seasonal time shift between summer and winter in the Northern and Southern hemispheres, and we get a meeting roulette wheel. By the time I started my day, my team’s workday was already over — by two hours.

There I was, once again, a lonely astronaut orbiting the planet. And if you think I’m writing this article to introduce many new lifehacks — spoiler alert! — I won’t. Most hacks are already in that article I wrote two years ago. If you haven’t read it, I highly recommend you do so. The part about space travel is enjoyable too!😊

But ok, I do have one lifehack and a sprinkle of lucky charm to share.

Lifehack: Living Without Meetings

One of the first things I had to let go of was my habit of conversation.

In my last role, I made the choice to stay late and meet with my team to ask questions. This time, this option was no longer on the table. There was no way teams would meet at the end of their day to accommodate my schedule. I, on the other hand, wouldn’t wake up early enough to accommodate their schedules, especially in winter.

I missed talking to people, asking quick questions, joking, or just catching up. To fill the silence, I tried watching team standup recordings and demo sessions, but it didn’t work. Without knowing the people or the background, those moments felt empty. Eventually, I learned to rely on information forensics. I pieced things together from scattered documents, past Jira tickets, and context clues. I then confirmed everything through short, direct pings for review.

It turned out I could produce decent writing using information forensics. I only set up calls when they were absolutely necessary. Asking someone to stay late or waking up at dawn isn’t a card you can play often without draining goodwill. What defined number of meetings was the extent to which I could make myself and others uncomfortable attending them.

Side effects of using this approach for a long time include hesitating to meet with people, even in your own time zone.

On the positive side, I was no longer the only Tech Writer on the project. There were other people living in the same harsh reality of time zones. No, they didn’t teach me to read minds, but shared tips and tricks that worked for them before. Luckily, I wasn’t alone, and I always had someone to ask for advice or peer review.

I also formed the habits of:

• Sharing early drafts to ask for clarification.
• Being persistent to obtain feedback.
• Confirming assumptions even when it means asking obvious questions.
• Being direct and communicating as clearly as possible.

Instead of asking “Hey, I’d like to set up a short sync to discuss A and B. Does Tuesday work?” I would write “Hey, I’d like to discuss A and B with you because I need to write documentation for X. I’ve set up a short sync, hopefully the time works for you. See ya!” The time usually worked, and people were happy to talk.

A Sprinkle of Lucky Charm

My saving grace was the work of previous teams. They left behind two things.

1. Meticulously Detailed Checklists

And I really mean they’re meticulous! Those checklists could include:

• Step-by-step instructions with screenshots on how to find a certain value in a repository file.
• Reminders to ping someone on a certain day before a release.
• Links to gazillions of pages to remember to update.

First, I was overwhelmed by the sheer amount of minute details and tasks to do. Later on, I was immensely grateful to all the people who put effort into writing those checklists.

2. Well-Developed Asynchronous Culture

Because all other teams existed in the same reality of scattered time zones, most people learned to deliver as much context as possible upfront.

In practice, this means that instead of a vague “Hey! Could you help us with UI text for a feature?” I would receive: “Hey, we’re working on this feature. It does X and Y. Here’s a short demo video with additional context, and here’re my questions.” In many cases, the context provided was enough for me to start drafting, and I could have a finalized text in a few iterations.

Bonus Point

We also incorporated the use of customized AI agents. So, whenever I needed to brainstorm three more versions of the error message title or needed a quick draft of a release note, I could have those ready in seconds.

In the end, how did I handle this situation? Simple enough: there was team reorganization. After a bunch of team structure and responsibility changes, I found myself handling diverse documentation assignments and working more with people in my time zone. And a few months later, the project assignment ended.

Phew, the burnout crisis was averted! Or was it?

Source: Blizzard Forum

Concluding Thoughts

That experience made me wonder what was it about meetings that mattered. Was it the structure, the efficiency, or just the feeling of being part of something shared?

People build trust slowly. Smaller teams make that easier because there’s room for small talk, sharing weekend stories, and having those intentional “ice breaker” moments that managers may introduce to strengthen connections. When the team scales in size and across geographies, and dozens of Slack channels appear, this is where the human touch is at risk, and some professions are more sensitive than others.

Technical Writing already has its fair share of solitary work; remove direct interaction, and it’s easy to slip into isolation mode. Without human touch, the people you work with are distant spaceships drifting through the corporate void. On better days, they are fantastic beasts roaming an enchanted forest of tasks and releases.

Remote work is not just about tools or time zones but also about staying visible. Whether you use checklists or AI, keeping the human touch is key. Even a lonely astronaut needs to hear a voice from Earth once in a while.

Have you worked across extreme time zones? What helped you stay sane — or at least productive? Share your experience in the comments. What’s one habit or tool that made the biggest difference for you?