Written by RHILLANE Ayoub
TLDR: Hiring across time zones was never our real problem. The first 30 days after the offer were, and we got them wrong twice: once with a folder of documents nobody could ask a question about, and once with a buddy system that fell apart on a nine-hour gap. The version that works has three parts: a real task shipped in the first week, a written decision log the new hire reads instead of interrupting anyone, and a fixed 20-minute overlap window with one named person every working day.
The new hire’s first message arrived at 02:40 Tangier time. I read it at seven in the morning with coffee going cold: a polite question about which of two spreadsheets was the current one, sent from California nine hours behind us, sitting unanswered through her whole first afternoon. She had signed on a Monday. By Wednesday she had sent four questions like that, each one waiting a full night for a reply, and I could feel the enthusiasm draining out of the thread with every delay.
I run a digital marketing agency headquartered in Tangier, with people in Dubai and California and clients on both sides of the Atlantic. We are about fifteen people, mostly remote, across four time zones. We had become decent at hiring across borders. We were bad at what came after the yes.
The Problem With Treating Onboarding as a Handover
Most small companies treat onboarding as the transfer of information. Here is the drive, here is the tool stack, here is the person to ask. That framing makes sense when everyone shares an office and a question costs thirty seconds. It collapses when a question costs a night.
The research on this is not subtle. Gallup’s work on the onboarding experience found that only a small minority of employees strongly agree their company does a great job of onboarding, and that the experience of those first weeks shapes whether people stay. Harvard Business Review has argued for years that companies should spend more time onboarding than they do, because the first months decide the next few years. I had read both. I still built two onboardings that assumed the hire would somehow absorb the company by proximity, when proximity was the one thing we could not offer.
Attempt One: The Document Dump
Our first version was a shared folder. Forty-odd documents: process guides, client briefs, tone rules, a tool list, a pile of past decisions written up as memos. On paper it was thorough. The new hire’s first week was reading it.
The failure took about ten days to show. The documents described how things were supposed to work, not how they worked that month. A guide for a tool we had replaced. A client brief with a contact who had left. And because everything was in the folder, the hire assumed every question had an answer somewhere in it and spent hours searching before asking. When she did ask, the answer came the next morning. By the end of week two she had produced almost nothing, through no fault of her own, and she was apologising for it.
The document dump has one hidden cost that took me longer to see: it teaches the new person that the company communicates in finished documents, so they stop asking half-formed questions. Those half-formed questions are exactly what a first month is for.
Attempt Two: The Buddy Who Was Asleep
The second version fixed the obvious flaw. Every new hire got a buddy, an experienced colleague whose job was to answer questions and check in daily. This is standard advice and it works well in one time zone.
The second hire we tried it with was also in California, and her buddy was in Tangier. Their working days overlapped for about one hour, at the end of the buddy’s day and the start of the hire’s. The daily check-in got pushed by client calls three days out of five. Questions sent in the California afternoon landed in the Tangier night. Within three weeks the buddy was answering in batches at breakfast, the hire had stopped asking anything she could work around, and both of them told me privately it felt like a formality.
The buddy system did not fail because the buddy was careless. It failed because we had assigned a relationship without designing the time it needed, and time was the scarce resource.
Attempt Three: Ship, Read, Overlap
The third version is the one we still run, and it is built around three things that all address the same constraint: the new person cannot wait a night for an answer, so the answers have to already exist, or the questions have to be scheduled.
A first-week shipping task. Before day one, the account lead picks one piece of real client work that is small enough to finish in a week and real enough to be sent to a client. A section of a monthly report. A set of ad variations. One landing page block. The hire ships it by Friday, with review from the account lead on Thursday. Everything about the task is chosen so that the work itself teaches the tools, the tone and the standard, and so the hire ends week one with something a client saw rather than something she read.
A written decision log. This replaced the folder. It is one running document, newest entry on top, where every decision that affects how we work gets a dated line: what we decided, why, and who to ask. Switched reporting tools, and why. Stopped offering a service, and why. A client’s preference for how they are contacted, and why. New hires read the last three months of it on day one, and it answers the question the document dump never could, which is not “what is the process” but “why is it like this”. When they do ask, the answer gets written into the log, so the next hire does not have to ask.
A fixed 20-minute overlap window. Every working day, at a time that lands inside both people’s working hours, the hire and one named person meet for twenty minutes. For Tangier and California that is 18:00 and 09:00. It is short on purpose, so nobody cancels it, and it is protected, so client calls move around it. The questions from the day get saved for the window instead of sent into the night. In practice, half of them get answered by the decision log before the window arrives.
The rule that ties the three together is that the same named person owns all of it for 30 days. That person is a named owner with the window in their calendar and their name on the shipping task, rather than a buddy who answers when free.
What Changed
The most obvious change was speed to first real output: a week instead of the three to four weeks the earlier versions produced. The less obvious change was tone. The overnight apology messages stopped, because the hire was no longer waiting on anyone to do her job. The questions that reached the window were sharper, because they had been written down first. And the decision log, which started as an onboarding tool, became the place the whole team goes to find out why something is the way it is, which has saved me from explaining the same decision for the fourth time more often than I can count.
HBR’s more recent piece on how onboarding can make or break a new hire’s experience ties poor onboarding to lower confidence in the role, weaker engagement and a higher chance of leaving early. For a remote team, I would put the cause more narrowly. The first 30 days are where the company proves it has thought about time.
If You Are Onboarding Across Time Zones
Pick the shipping task before the start date, and make it real. Keep a decision log from today, even if the next hire is months away, because the log is only useful once it has history. And put the overlap window in the calendar before the offer letter is signed, at an hour that is honest for both sides. Everything else in our onboarding, the tool access, the introductions, the reading, hangs off those three, and none of it needs to be finished before day one. The work at the digital marketing agency I run is not unusual; the constraint is. Any company hiring people it will never sit next to has the same one.
Author Bio: RHILLANE Ayoub is the founder and CEO of Rhillane Marketing Digital, a digital marketing agency headquartered in Tangier with a presence in Dubai and California, and a team of about fifteen people working across four time zones. If you run a remote team and want to compare notes on how a small company gets its first 30 days right, you can find the team at Rhillane Marketing Digital.
