The Green Dot Is Watching You: Presence Indicators as Remote Surveillance
The green dot next to your name in Slack means you're available.
That's what it was supposed to mean. A coordination signal. A way to know, across a distributed team, whether someone is at their desk and able to respond. A useful, small piece of ambient information in an environment where you can't see each other.
But watch what happens when you're not actually working — when you step away from the desk, when you're in a meeting in another tab, when you're thinking in your chair without typing anything for twenty minutes. Notice the reflex. The small pull toward moving the mouse, toward opening a tab, toward doing something visible because the dot might have gone gray and you don't want anyone to notice.
You are performing availability for a system that doesn't have opinions about you. You are surveilling yourself.
The Signal That Changed Its Own Meaning
Presence indicators exist in every major workplace communication tool: the green dot in Slack, the color-coded status ring in Microsoft Teams, the active/away toggle in Zoom. The design logic was straightforward: distributed teams need lightweight awareness of who's available before sending a message or requesting a meeting. The presence indicator is the digital equivalent of glancing down the hall to see if someone's at their desk.
What Microsoft's WorkLab research found — tracking behavior across millions of remote workers during the pandemic expansion of Teams — is that people modify their work behavior to manage how they appear in the presence system. They stay logged in during breaks they wouldn't have taken in an office. They avoid long periods of stillness that might gray out their status. They structure their day around maintaining the visual signal of availability, which is not the same thing as being available.
The research on digital presenteeism uses a specific term for this: the gap between perceived availability and actual productivity. In physical offices, presenteeism meant staying at your desk past 6pm to be seen. In remote work, presenteeism means maintaining the green dot through behavior that looks like work without necessarily being work — keeping a tab open, checking messages you'll respond to later, doing something that refreshes the activity signal.
The problem isn't the dot. The problem is what the dot communicates to other people, and what it therefore communicates back to you about what you're supposed to be.
What You Opted Into
Here's the consent situation honestly stated: you agreed to use Slack. Slack's presence indicator is on by default and reflects your actual activity patterns (keystrokes, mouse movement, message sends). You can manually set your status, but the automatic detection runs in the background. You did not make a specific decision about presence indicators. You made a decision about a productivity tool, and the presence indicator came with it.
This is different from being told you'll be monitored. You were not told you'd be monitored. You installed a chat tool. The monitoring — of a kind, self-reported back to you and your colleagues — was included at no additional charge.
Cal Newport makes an adjacent observation in A World Without Email (2021): the hyperactive hive mind model of work, driven by tools like Slack, generates constant low-level visibility that creates its own performance pressure. Not because anyone explicitly demands it, but because the tool makes your communication patterns legible. How quickly you respond. When you're active. Whether you've seen something. The infrastructure of the tool becomes the infrastructure of accountability, whether or not accountability was the intention.
The cognitive cost of constant tool availability runs parallel to this — the green dot problem isn't just about surveillance, it's about the attention tax of a system that treats presence as a metric.
The Self-Surveillance No One Designed
What's genuinely strange about presence indicators is that the surveillance is lateral and self-generated. Your employer didn't implement a monitoring dashboard for your Slack activity. IT didn't install software to track your keystrokes. You and your colleagues collectively created a mutual visibility system and then internalized its norms without anyone explicitly setting those norms.
Nobody told you that going gray for two hours is a problem. But you probably know that it looks like a problem. You've noticed when others are gray and wondered, briefly, what they're doing. You've made the calculation, probably without conscious articulation, that being gray for too long sends a signal you don't want to send. And so you've adjusted your behavior to manage the dot.
This is worth sitting with. You are doing the surveillance work yourself. There is no manager checking your presence data, no HR system that flags extended inactivity. The system just makes your availability legible to your peers and yourself, and the social environment does the rest. You internalized the norm and enforced it on yourself. That's a more efficient form of behavioral control than any monitoring software, because it doesn't require anyone to actively monitor you.
Bentham's panopticon — the prison design where any guard could see into any cell but prisoners couldn't know when they were being watched — worked on the same principle. The prisoner who doesn't know if they're being observed performs compliance constantly, because the uncertainty is more effective than constant surveillance. The green dot doesn't tell you who's looking at your status. It just makes your status visible, always, to anyone who might look. The uncertainty does the rest.
The Behavioral Changes No One Tracks
The impact of ambient presence indicators on deep work is real and mostly unmeasured. Not because it hasn't been studied — Newport and others have described the mechanism — but because the productivity loss from self-surveillance is difficult to quantify against the coordination value that presence indicators provide.
What we can say: tasks that require sustained, uninterrupted attention are harder to do in environments where your availability is continuously signaled and where others' expectations of your responsiveness are shaped by the green dot's promise. If the dot says you're available, and you take two hours to respond because you were deep in something, the dot has made a promise you didn't intend to make. The mismatch creates friction — a message, a follow-up, an assumption that something is wrong.
The easiest solution, which many remote workers arrive at without naming it explicitly, is to not do the deep work during core hours when people expect responsiveness. To front-load it before the workday technically begins, or push it into evenings, or carve out explicitly blocked calendar time that signals unavailability through a different channel. These are workarounds for a system whose defaults make sustained attention the awkward exception.
The other solution, rarer, is to simply go offline when doing deep work and let the dot go gray. This requires a level of organizational trust and personal confidence that many remote workers — especially junior ones, especially those in cultures where face-time has been the traditional productivity metric — find difficult to exercise.
What the Dot Is Actually Measuring
The presence indicator doesn't measure productivity. It measures legibility. It tells your colleagues when you're producing activity signals the computer can detect. Typing, moving a mouse, sending a message. None of these are the same as thinking well, writing something substantial, making a decision that requires focused judgment.
The best parts of intellectual work are invisible to the presence indicator. Reading carefully produces no activity signal. Thinking through a problem in the shower, on a walk, over coffee produces no activity signal. The indicator rewards a specific kind of visible busyness that is correlated with, but not identical to, productive work. And anything you optimize to, you'll get more of — whether or not that's what you want.
The question is whether presence indicators are worth this tradeoff. For some teams and some roles, the coordination value genuinely exceeds the surveillance cost. For others — particularly those doing work that benefits from long periods of uninterrupted focus — the presence indicator is a structural disincentive for the kind of work the role actually requires.
Most organizations haven't asked this question explicitly, because nobody noticed when the green dot became a behavioral modifier. It was just there. It was part of the tool. And now the tool shapes how people work, invisibly, through the pressure of a small circle that may or may not be anyone's explicit intention to enforce.
Worth asking yourself: in the last week, how many times did you do something — move a mouse, check a message, open a tab — primarily to manage your presence indicator rather than because you needed to do it?
The answer says something about who, exactly, is running your workday.
Photo by cottonbro studio via Pexels