Managing Up When Your Boss Is Asleep

A backend engineer I know in Kraków spent a whole Thursday stuck on a one-word answer. She'd built two ways to handle a schema migration, both defensible, and she needed her manager in Seattle to say which one to ship. She wrote it up cleanly at 3pm her time, laid out the tradeoff, asked the question. Seattle was asleep. So she picked up a smaller task to fill the afternoon, logged off, and came back Friday to a reply that said, essentially, "go with the second one." Ten seconds of decision. A full day of her week spent waiting for it.

She hadn't done anything wrong, and neither had her manager, who answered the morning he saw it. The problem was the shape of the thing. Her boss was the one person who could unblock her, and her boss was reachable for maybe an hour a day, at the very tail end of hers.

Almost everything written about distributed teams looks down the org chart, at how a manager should run people they can't see. This is the other direction. If you're the one being managed from another timezone, your boss is a dependency, and it's one of the least forgiving ones you have. When they're asleep through your whole working day, every decision you need from them, every approval, every "is this even the right priority," gets priced in a full sleep cycle. Learning to work around that gap is most of what separates the people who thrive reporting across a time difference from the ones who spend half their week blocked.

Your boss is a dependency you can't schedule

Start by seeing the relationship for what it mechanically is. Your manager controls things you need to do your job: decisions above your pay grade, sign-off on the risky stuff, priority calls when two efforts collide, air cover when another team pushes back on you. In an office you get these in seconds. You catch them in the hallway, you lean into their doorway, you read their face and know whether to push now or wait. That entire channel, the fast and cheap and in-person one, is gone when they're eight hours away, and nobody hands you a replacement for it.

What you're left with is a version of the same problem an open pull request has when it waits on one reviewer: a task blocked on a single person's attention, available only in a narrow window. Every round-trip with your boss, question out and answer back, costs you a day if it crosses a night. So the whole game is cutting how many times you have to cross that night to get what you need. Not replying faster. You can't reply faster than their morning. Crossing fewer nights.

Stop asking, start proposing

The highest-leverage change is in how you ask for things.

The instinct, carried over from the office, is to surface the problem and let the boss solve it. "Hey, not sure how we should handle the migration, can we talk?" In person that's fine, because the conversation happens right then. Across timezones it's a small disaster, because you've handed your manager an open-ended question that needs a live back-and-forth to resolve, and there's no live time available. Best case they reply with a clarifying question of their own, and now you've burned two nights before anyone has decided anything.

Flip it. Instead of asking a question, send a proposal. "Hit a fork on the migration. Option A ships a day sooner but locks us into the current schema. Option B is slower but leaves room to change it later. I'm going with B unless you tell me otherwise by your Tuesday morning." Now your boss does the easy thing instead of the hard thing. They can reply "yes" in the ten seconds they actually have, and even if they say nothing, you've told them you're moving, so silence reads as a green light rather than a wall. This is the same move as running decisions as written proposals with a deadline and silence as consent, except you're aiming it upward, at the person who signs off on your work.

The discipline this takes is real. It means doing the thinking before you message, arriving with a recommendation instead of a question, and being willing to be wrong in writing. That's harder than lobbing the problem over the wall and waiting. It's also the thing that turns your boss from a bottleneck into a rubber stamp, which is exactly what you want them to be.

Batch your asks into one door

The other round-trip killer is the drip. You think of something you need, you ping. An hour later, another thing, another ping. Each lands in your manager's overnight pile as a separate thread, and each is a separate cross-night wait. Scatter five small asks across your afternoon and you've potentially spent five days of latency on things that could have cost one.

Hold them instead. Keep a running note of what you need from your boss, and unless something is genuinely on fire, send them as one considered message near the end of your day, so it's sitting at the top of their morning as a single answerable block. This is the managing-up version of batching review round-trips instead of dribbling them out one at a time. It feels less responsive. It is dramatically faster.

The exception is the true emergency, and you should agree, out loud and in advance, on what counts as one. Ask your manager directly: if I'm blocked on something that can't wait for your morning, how do you want me to reach you? Most bosses would far rather get pinged on their phone twice a year for a real fire than have you sit blocked on something urgent because you were being polite. But that door only works if you've settled it beforehand and you don't lean on it. This is really just the response-time contract, negotiated one level up.

Make your work visible without being online

Here's the anxiety nobody says out loud: when your boss can't see you working, you start to worry they assume you aren't. So people over-correct by being online whenever the boss is, replying fast, keeping the green dot lit, which is both exhausting and a lie about what actually produces value.

The fix isn't presence. It's output your manager can see without a meeting. Send a weekly update written for the person who wasn't in your week and your boss reconstructs what you did on their own time, in their own morning, without you performing availability at your midnight. This matters more reporting across a timezone than it ever did down the hall, because your manager is judging you by what you ship rather than by watching you work whether they'd admit it or not. When they can't observe the effort, the artifact is the only evidence they have. A clear written trail of what you decided, what you shipped, and what you're worried about does more for how your boss sees you than any volume of fast replies ever will.

And keep the one synchronous thing synchronous. The recurring 1:1 is the meeting you should fight to protect, because it's the one place to raise the stuff that doesn't survive a Slack message: that you're stuck, that the priorities feel off, that you're heading somewhere your boss might not love. Don't waste it on status you could have written down. Spend it on the things that genuinely need a voice.

The goal is to need them less

All of this points at one thing, which is buying yourself the room to stop waiting. Every proposal you send instead of a question, every batched message, every call you make and document rather than escalate, builds a record that lets your manager give you more rope. The engineer in Kraków who reliably sends "here's what I'm doing unless you object" trains her boss to trust her judgment, and a boss who trusts your judgment stops being a gate you have to line up at.

That's the real prize of managing up across a time gap. Not getting faster at pinging someone who's asleep, but arranging things so their being asleep matters less and less. Do it well and the eight hours between you stop feeling like a leash and start feeling like what they can be: a long stretch of quiet work nobody's going to interrupt, and a boss who reads the results in their morning and mostly just says "yep."

Stop Losing a Day to "By Your Tuesday Morning"

Half of managing up across a gap is the arithmetic of when your message actually lands: whether "by your Tuesday morning" means what you think it does for a boss three timezones over, and whether the deadline you set falls on their workday or their weekend. Timely converts every time mentioned in Slack to each person's own clock automatically, so when you write "I'm shipping this unless you object by 10am your time," your manager reads it as the exact moment you meant. Fewer misfired deadlines, fewer decisions that wait an extra day because nobody was sure whose morning it was.

Add Timely to Slack — Free · See how it works