How to Manage a Team You Can't See

A manager I worked with kept Slack open on a second monitor all day, and what he was really watching was the little green dots. Who's active. Who went idle around 2pm. Who hadn't posted anything since morning. He'd have been offended if you called it surveillance, but if you'd stopped him at any moment and asked who on his team was working right now, he'd have answered by reading those dots.

Then he hired an engineer in Manila, and the whole system fell over. His strongest person was, by the dashboard he'd been running in his head, offline nearly every hour he happened to look. Grey dot. No recent messages. Asleep straight through the American workday. And shipping more than anyone else on the team.

That's the wall a lot of managers hit the first time their team crosses a few timezones. The signal they've leaned on for years, is this person here and reachable right now, stops mapping to anything true. The good news is that it never mapped to much in the first place. Remote just takes away the illusion that it did.

The green dot was always a bad proxy

Walk into an office and you get a hundred little cues for free. You see who's at their desk, who looks busy, who left at 4. None of it tells you whether good work is happening, but it feels like it does, and managers quietly run on that feeling for years without noticing they've never actually checked.

The person typing furiously might be arguing on Slack. The one who left at 4 might have solved the hard problem in the shower and shipped it before lunch. Presence and productivity were never the same thing. The office let you confuse them because the bodies were right there, and the confusion mostly didn't cost you anything.

A distributed team removes the props. Now there's no room to glance into, so the anxious manager reaches for the nearest digital stand-in: the green status dot, the timestamp on the last message, how fast someone replies. It's the same mistake wearing new clothes. You've swapped watching bodies in chairs for watching activity indicators, and activity is an even worse proxy than presence, because it's so easy to fake and so easy to punish the wrong people for.

Think about who looks bad under an activity regime. The engineer in a twelve-hour-offset timezone, legitimately asleep during your day. The person doing four hours of deep, heads-down work with Slack closed, which is exactly the work remote is supposed to enable. Meanwhile the person who keeps the app open and reacts to every thread within ninety seconds looks like a star, right up until you notice they haven't finished anything substantial in three weeks. Manage by dots and you reward the wrong behavior with a precision you'd never manage on purpose.

Manage the work, not the person's whereabouts

The fix isn't a trick. It's a shift in what you point your attention at. Stop asking "is this person available" and start asking "is the work moving, and is it good." Those are different questions, and only the second one is your actual job.

That means you have to know what the work is with more precision than an office ever forced you to. When you can see someone, you can be vague. Hand them a fuzzy task, watch them look busy, feel reassured. When you can't see them, vagueness has nowhere to hide. If you can't tell whether a piece of work is done or good, that's not a visibility problem you solve with monitoring. It's a clarity problem you caused by never defining the work well enough to evaluate.

So define it. Every meaningful piece of work should have a shape someone could check against: what does done look like, roughly when, and how will we both know it landed. Not a Gantt chart or a stack of tickets nobody reads. Just enough that the answer to "how's it going" is something you can point at instead of something you have to feel out from a status icon. Once the work is defined that way, a grey dot at noon stops being a threat, because you're no longer trying to read productivity off of presence. You're reading it off of output, which is the only place it was ever legible.

Make the output visible on purpose

If you're not going to watch people work, you need the work itself to surface, which on a distributed team means it surfaces in writing. This is where a lot of managers panic and assume that not-watching means not-knowing. It doesn't, as long as the team has a rhythm for making progress legible.

The workhorse here is the weekly written update: a short note from each person about what actually changed, what's next, and what's stuck. Read five of those on Monday morning and you have a truer picture of your team than the green-dot manager gets in a week of staring at his sidebar. It's asynchronous, so nobody has to be awake at the same time, and it's written down, so it's still there when the person is asleep and you have a question.

Around that, keep the artifacts of the work in the open. Decisions live in docs, not in someone's head. Code lands in reviewable pull requests. The demo of what shipped gets recorded and posted so the half of the team that was asleep sees the same thing everyone else did. None of this is monitoring. It's the ordinary residue of work done in the open, and it gives you everything the green dot pretended to and never could.

The 1:1 is where you actually see them

Here's the part that surprises managers who think going async means going cold. You still need real contact with each person, and you should protect it fiercely. The written updates tell you about the work. They don't tell you that someone's quietly drowning, or bored, or about to leave.

That's what the recurring one-on-one is for, and it's the one thing on a distributed team I'd keep synchronous even when it costs someone an awkward hour. Thirty minutes where you're actually talking, not reading status, is where you catch the things no dashboard shows. How someone sounds when they say "it's fine." Whether the person you never worry about is drifting because you never worry about them. You gave up the hallway read when you went remote. The 1:1 is how you get it back, on purpose, instead of pretending a Slack status can do the job.

Don't buy the surveillance software

Some managers, faced with a team they can't see, go the other direction and buy their way back to visibility. Software that screenshots people's screens every ten minutes, logs keystrokes, scores "activity." I want to be blunt: this is a mistake, and not a subtle one.

It doesn't measure output. It measures theater, and it teaches your best people to produce theater. The engineer who used to close Slack and think hard for three hours now jiggles the mouse and keeps a doc open so the tracker stays green, and you have successfully paid money to make your team worse at the exact work you hired them for. Worse, you've told them the thing you can never take back: I don't trust you, so I'm going to watch you. People who are watched like that don't repay it with loyalty. They repay it by leaving the moment something better comes along, and the trust that a remote team actually runs on doesn't survive the first screenshot.

The teams that do this well aren't naive about accountability. They're strict about it. But they hold people to outcomes they defined together, not to hours logged or dots lit, and they treat being unable to watch someone work as the normal condition of the job rather than a problem to engineer away. Managing a team you can't see isn't a downgrade from managing one you can. Done right, it's better, because it forces you to manage the only thing that was ever worth managing.

Manage by Output, Starting With the Clock

Managing by output only works if everyone reads the plan the same way, and a deadline like "ship by Friday 5pm" quietly breaks the second it crosses a timezone. Timely converts every time mention in Slack to each person's own clock automatically, so the target you set lands correctly whether your teammate reads it in Austin or Manila, and nobody misses a commitment because they did the arithmetic wrong.

Add Timely to Slack — Free · See how it works