Giving Hard Feedback Across Timezones

The message was three paragraphs long, and she read all of it at 6:40 in the morning, alone, before anyone she worked with was awake.

Her manager, seven timezones west, had spent his afternoon writing it. A careful, well-meant note about how her last two projects had slipped, what he needed to see change, and a line at the end about how he knew she was capable of more. He hit send at the end of his day and went to dinner feeling like he'd handled something responsibly. By the time he woke up, she had been carrying that message around for nine hours. She'd read it four times. She'd decided the "capable of more" line was a soft way of saying she was on her way out. She had not slept much. And there was no one online to ask, so she just sat with the worst version of every sentence until California woke up and he could tell her, too late, that he hadn't meant any of that.

Nothing in the message was wrong. The delivery was the whole problem, and the delivery was shaped entirely by the timezone gap.

The gap quietly pushes you toward writing it down

The trap is a comfortable one. Hard feedback needs a live conversation. A live conversation across seven timezones means finding a slot in a narrow overlap window, probably early morning for one of you, and probably scheduled two days out. All that friction sits between you and a thing you were already dreading. So the doc, or the long Slack message, starts to look reasonable. You can say it carefully. You can get the wording exactly right. You can send it now instead of waiting until Thursday.

Every one of those feels like a point in favor of writing. None of them is. What you're actually doing is trading the discomfort of scheduling for a much larger cost you won't see, because it lands after you've logged off. The convenience is real and it's pointing you at the worst possible way to deliver the thing.

This is worth naming because it runs against the grain of everything else a good distributed team does. Most of the time, async is the right default, and I'd argue that harder than most people do. Kill the status meeting and write the update. Make the decision in a doc, not a call. But feedback that stings is one of a small number of exceptions where the async instinct actively hurts you, and the timezone gap is exactly what disguises the exception as the rule.

Written criticism is not the criticism you meant

When you write hard feedback and someone reads it alone, three things happen to it that you never intended.

The tone drains out. You know you wrote it warmly. You can hear your own voice as you type, the pauses, the reassurance, the slight wince that says "this is hard for me too." The reader gets none of that. They get flat text, and flat text about their performance reads colder than anything you'd ever say out loud. A sentence you meant as gentle arrives as clinical.

Then they re-read it. Nobody re-reads a compliment five times. They re-read the hard message, and every pass finds a darker reading. "I need to see this change" becomes a threat by the third loop. The document doesn't move, but their interpretation of it keeps sliding downhill, and there's nothing to push back against it.

And the timezone gap makes the last one uniquely cruel: there's no one to answer. In an office, a hard conversation ends and the person can walk to a friend's desk, or catch you an hour later to ask what you meant, or just read your face across the room and see you're not angry. Across a wide gap, they get the message at the start of their day and the author is asleep for the next eight hours. The single most important feature of hard feedback, the ability to ask "wait, what did you actually mean," is offline. They stew instead. Managing a team you can only judge by output already asks a lot of your written communication. This is the one message where writing it down fails you.

Say it live, and treat that as the rule

The fix isn't complicated, it's just uncomfortable. Real feedback, the kind that carries weight or bad news, gets a live conversation. Voice or video, human to human, with the other person able to respond in the same breath you're speaking.

Treat this as a firm exception the way you'd treat the one in-person offsite a distributed team actually needs. Almost everything else can flatten into text and be better for it. This can't. The value of the live version isn't the words, which you could have typed. It's that the other person can interrupt, ask, hear your tone, watch you mean it, and correct their own catastrophizing in real time instead of marinating in it for a night. You lose all of that the moment you send instead of say.

Do not, under any circumstances, reach for a recorded video as the compromise. A Loom of you delivering critical feedback is the worst of both worlds: it has your face and your tone, so it feels personal, but the person still can't respond, still watches it alone, and now gets to replay the exact frame where you looked disappointed. If it's hard enough to need your voice, it's hard enough to need theirs back.

The recurring one-on-one you already keep synchronous is usually the right container for this. But don't wait two weeks for the next scheduled one to raise something that matters now, and don't ambush a routine 1:1 with a bombshell either. If it's big, give it its own slot and a light heads-up so the person isn't blindsided.

Put the conversation in their morning, not your convenience

Once you've committed to talking live, when in their day you do it matters more than people expect, and the timezone gap gives you a lever most managers waste.

Aim for the early part of the other person's working day. Not the end of it, and never their Friday afternoon. The reason is simple: after hard feedback, a person needs somewhere to put the feeling. If you deliver it at 5pm their time, they close the laptop and carry it into their evening with no colleagues around and nothing to do with the adrenaline. Deliver the same thing at 10am their time and they have a workday ahead, people to talk to, and a chance to ask you a follow-up before you sleep. The feedback is identical. The landing is completely different.

This means anchoring the time to their clock, deliberately, and eating the awkward slot yourself if the math demands it. If your report is in Warsaw and you're in Seattle, their 10am is your 1am, and that's a genuinely bad hour to run an emotionally loaded conversation. Sometimes you split the difference and take their early evening over your own dead of night, a real tradeoff with no clean answer. The point is that you're choosing it on purpose, in the receiver's interest, instead of defaulting to whatever's easy for you. Getting the time itself unambiguous, so nobody shows up an hour off, is the floor here, not the finish line.

What actually belongs in writing

None of this means the conversation is purely verbal. Writing has a real job, it just comes after the talk, not instead of it.

Prep beforehand so you use the scarce live time well, because you may only get thirty focused minutes. Know your two or three concrete examples cold. Then, once you've talked, write the recap: what you discussed, what you both agreed happens next, and by when. That written follow-up is where the async default comes back and earns its place. It gives the conversation a durable record both of you can return to when you're not online together, and it protects against the memory drift that a wide timezone gap makes worse. The order is the whole trick. Talk first so the human part lands right, write second so the substance doesn't evaporate.

Feedback is the one place a distributed team should override its own async instincts. The gap makes the live conversation annoying to schedule, and that annoyance is precisely the thing nudging you toward a version that will hurt more and help less. Book the call. Put it in their morning. Say the hard thing to a person who can say something back, and let the writing do the part it's actually good at.

Give the Hard Conversation the Right Hour

The hardest part of feedback across timezones is landing it at a moment that's kind to the person receiving it, which starts with everyone reading the time the same way. Timely converts every time mentioned in Slack to each person's own clock automatically, so when you propose "10am your time Wednesday" for a conversation that matters, it arrives as exactly the moment you meant, with no one doing the math wrong at the worst possible time.

Add Timely to Slack — Free · See how it works