Make Your Working Hours Visible to Your Team

The green dot next to Theo's name said he was online, so Lena pinged him with a quick blocking question and settled in to wait. Twenty minutes. Forty. By the hour mark she'd decided he was ignoring her, got quietly annoyed, and routed around him with a worse answer than the one he would have given in ten seconds. Theo was asleep in Denver. He'd left Slack open on his desktop overnight, the way people do, and the dot had been lying to Lena since before she woke up in Berlin.

The same week, going the other direction, someone pinged Theo at 7pm his time with a "got a sec?" He did not have a sec. His day had ended at five and he was making dinner, and now he had the choice every remote worker knows: answer and teach people his evening is fair game, or ignore it and feel like he's dropped something. Neither failure was anybody being rude. Both came from the same hole. Nobody on the team could actually see when Theo worked.

The office broadcasts your schedule for free

In a shared building, when you're available is public information and you never have to say a word about it. People can see you at your desk. They can see the meeting-room door closed, the headphones on, the coat gone from the back of your chair at 5:30. A colleague walking past knows, without asking, whether this is a good moment to interrupt you or whether you left an hour ago. Your schedule is written on the room, continuously, for free.

Remote deletes every bit of that. Your hours become private information that lives only in your own head and your own timezone, and the people who need to coordinate with you are left guessing. They guess in both directions and both are expensive. They interrupt you mid-focus because they can't see you're deep in something. Or they sit on a question for a full day because they can't tell you're right there and would have answered in a minute. The cost of the invisible schedule is paid in both wasted interruptions and wasted waiting, and nobody files it as a problem because it never looks like one. It just looks like Theo being flaky and Lena being impatient.

The green dot is the wrong signal

The instinct is to let the presence indicator do the job. It won't. The green dot measures whether an app is open, not whether a person is working, awake, or reachable, and on a distributed team those come apart constantly. People leave Slack running overnight. People step out for two hours with the laptop on. People go heads-down with the app open and have no intention of answering anything. A dot cannot tell you the difference, so reading it as availability is how Lena lost her morning.

This is the same broken proxy that wrecks evaluation when managers try to judge a team by presence instead of output. The green dot is a terrible measure of whether someone is productive, and it's an equally terrible measure of whether you can reach them right now. In both cases the fix is to stop reading a signal that was never carrying the information you wanted and replace it with something explicit. For evaluation that's defined output. For availability it's your stated hours.

Publish your hours as a fact, not a vibe

So state them. Put your actual working window somewhere durable and visible, and put it in terms other people can use without doing math. Most teams have more than one place for this and you want it in the obvious ones: your Slack profile, your calendar's working-hours setting, wherever your team keeps its directory. "Online-ish, usually" is not a schedule. "I work roughly 9 to 6 Denver time, core hours 9 to 1 for anyone who needs overlap" is a schedule somebody can plan around.

Write it in your clock and, where you can, show it in theirs too, because a teammate twelve hours away reading "9 to 6 Denver" still has to convert it to know when that lands on their afternoon. The whole point is to remove the guessing, and you haven't removed it if you've just handed someone an arithmetic problem instead. Making your real local time easy to see next to your name is the smallest version of this and it does a surprising amount of the work.

This is not the same discipline as controlling the notifications that reach you, even though both touch your Slack settings. That one is about silencing the inbound stream so you can work. This one points the other way. It's about telling other people when to reach you, so they aim their questions at the hours you're actually there and stop aiming them at the hours you're asleep.

Make your status tell the truth

Published hours cover the steady state. The status line covers the exceptions, and it only helps if you treat it as information rather than decoration. A status that says "heads-down until 2, back on Slack after" tells the person with a non-urgent question exactly what to do: wait until 2. A status that's been stuck on a coffee-cup emoji since March tells them nothing, so they fall back to guessing, and you're back where you started.

The useful version of this is boring and specific. "Out at a doctor's appointment, back around 3." "In deep work, will miss messages until noon, ping me twice if it's actually on fire." "Done for the day, see you tomorrow." Each one answers the only question the other person has, which is some flavor of "can I expect you, and if not, when." Resist the urge to use the status to perform how busy or available you are. A status that's always a slightly frantic "so much going on!!" is as useless as a blank one. The job is to report your real state, not to manage an impression of it.

Hours only work if you keep them

Here's the part that's easy to skip and ruins the whole thing if you do. A published schedule is a promise, and the moment it stops being true people stop trusting it and go back to guessing. If your profile says you're off at six but you answer messages until eleven every night, you have not communicated your hours. You've communicated that your hours are fake and the real rule is that you're always on. Everyone adjusts to the behavior, not the profile, and now the person who logs off at six feels like the slacker.

This is where visible hours connect to protecting the edge of your day and to the team's response-time norms. Those two give you the cover to actually hold the line: if the team agrees that a non-urgent message can wait until the receiver's next working block, then logging off at your stated time costs you nothing socially, and your published hours stay honest. Without that cover, stated hours are wishful thinking, because the real schedule is whatever you demonstrate by answering. Keep them or don't post them. A schedule people can't rely on is worse than none, because it actively misleads.

If you lead the team

Most of this is an individual habit, but a manager sets whether it takes. Three things move the needle. Make the expectation explicit so publishing hours is the norm and not a quirk of the one organized person. Build a place where the team's hours live together, even a rough shared sheet or a channel topic, so picking a fair time for anything live stops being a round of "what time is it for you again?" And keep that map current, especially when someone travels or relocates and their old hours silently go stale.

Then model it. Publish your own hours, keep them honestly, and stop rewarding the person who answers at midnight with the implied gold star, because every time you do you teach the team that the stated schedule is decorative and the real one is always-on. On a team nobody can see, when you work has to be something you say out loud and then live by. The room used to say it for you. Now you do.

Let Timely Handle the Clock Math

Half of making your hours legible is getting them out of your own timezone and into everyone else's. When your profile says "core hours 9 to 1" or a teammate writes "let's catch you at 10 your time," Timely reads each person's Slack timezone and converts every time mentioned into their own local clock, so nobody has to do offset arithmetic to work out when you're actually around. It won't keep your schedule for you, but it makes the schedule you publish readable to the whole team at a glance.

Add Timely to Slack — Free · See how it works