Summary
Ask a remote worker what they do when they step away from the desk for twenty minutes and a surprising number will describe some version of keeping the dot green: nudging the mouse, leaving a video playing, setting a calendar block so nobody asks. Nobody taught them this. It emerged because somewhere a manager treated the status indicator as a timesheet, and the team adapted. Green-dot culture is the quiet agreement that appearing available matters more than being effective, and it is one of the most corrosive habits a remote team can fall into, because it rewards the wrong thing and punishes the people doing deep work. This piece looks at how it starts, what it costs, what the activity data shows when you look past the dot, and how to switch a team off the habit without a speech.
E-Monitor measures focus time and output rather than presence, so a team can stop watching the dot and start watching the work. Sign up →
How the Dot Became a Timesheet
Chat presence indicators were designed for one purpose: to tell a colleague whether a message is likely to get a quick answer. Then offices emptied and managers lost the visual cues they had relied on for decades, the person at the desk, the light under the door, and the only thing left that looked like presence was a small green circle. It was never meant to carry that weight, and it carries it badly. It goes yellow when someone is reading a long document. It stays green when someone has walked away. It says nothing at all about what was done.
The habit spreads fast because it is enforced sideways. One pointed "you were away for a while this morning" and the whole team learns the rule. From there, the behaviours follow: status padding, where people set themselves active during breaks; mouse jigglers; the reflex to answer every message within seconds to prove you are there. None of it produces work, and all of it fragments the attention that does.
What It Costs
Three costs show up reliably in teams that run on status.
Deep work gets punished. The person who turns off notifications to write for two hours goes yellow, then away, and is the one who gets asked where they were. The person who stays green by answering every ping produces less and is praised for responsiveness. Over months the team learns which behaviour is rewarded, and the deep work guide shows what that does to output.
Trust erodes in both directions. Employees who pad their status know they are performing, and that knowledge sours the relationship with a manager they would otherwise respect. Managers who sense the padding trust the dot less and look harder, which makes the padding worse. The guide to knowing whether remote employees are working covers the healthier alternatives.
Flexible workers lose out. Parents, carers and people in other time zones work in pieces. A status-driven culture reads every piece as absence, which is why green-dot norms quietly become an equity problem, as the equitable monitoring guide explains.
What the Data Shows Instead
Teams that have monitoring data can test the dot against reality, and the result is always the same: presence and output are barely correlated. The people with the highest active-status percentage are rarely the ones with the most focus time or the most output, because constant availability and sustained concentration are opposites. The strongest performers on most knowledge teams show a distinctive pattern: long focus blocks, status away or do-not-disturb during them, and responsive bursts between. On a status dashboard they look unreliable. On an output dashboard they are carrying the team.
That is the argument for replacing the dot with something that measures work. Focus blocks, application mix, output per week and workload balance all answer the question the manager was really asking, which was never "is this person at their desk" but "is the work getting done and is anyone drowning". The output-based management guide covers the shift.
Switching a Team Off the Habit
Green-dot culture ends when the manager stops looking, and it has to be visible that they have stopped. Six moves, in order.
- Say it out loud in a team meeting: status is for colleagues, not for me, and I will not be reading it
- Set a response-time norm of a couple of hours for chat, so being away is normal rather than suspicious
- Model it. Managers who set their own status to away for focus blocks give everyone permission
- Replace the signal. Review output and focus trends weekly, at team level, so people see what is being looked at instead
- Protect focus blocks on the calendar and treat a yellow dot during one as the plan working
- Kill the jigglers by removing the reason, not by hunting them; once status does not matter they disappear on their own
The second and fourth moves do most of the work. A stated response window makes absence legitimate, and a visible alternative measure gives people something real to be judged on. The attention span guide covers the response-time norm in more detail.
A Note on Monitoring Tools
Monitoring software can make green-dot culture worse or end it, depending on how it is configured. A tool that shows managers a live "active now" list and an activity percentage is a bigger, more detailed green dot, and teams will pad it the same way. A tool that shows focus time, output and workload trends by week, with short idle gaps hidden from managers and the employee able to see their own data, is the replacement. The difference is a configuration decision, and the microbreaks guide explains why the idle threshold matters so much to it.
A Worked Example
A fourteen-person marketing team had a manager who checked Slack presence each morning and messaged anyone yellow. Within a year, every team member had a jiggler or a looping video, two of the best writers had left citing "being watched", and the team's output per head had fallen while its active-status percentage had risen to 96 percent. A new manager inherited it, announced in her first meeting that she would never look at status, set a two-hour response norm, and moved the weekly review to focus time and pieces shipped.
Active status fell to 71 percent within a month, which she treated as good news. Focus blocks per person rose from 1.9 a day to 4.4 over the quarter. Output per head recovered to its previous level by month four and passed it by month six. Nobody was told to remove their jiggler; they simply stopped bothering.
Frequently Asked Questions
1. Is being online on Slack or Teams a measure of productivity?
No. Presence indicators show whether a message might get a quick reply, not whether work is being done. In activity data, active-status percentage and output are barely correlated, and the strongest performers often show away or do-not-disturb status during their most productive hours.
2. What is green-dot culture?
The informal norm, usually set by a manager who treats chat status as a timesheet, that appearing available matters more than being effective. It produces status padding, mouse jigglers, reflexive instant replies, and punishes deep work.
3. What is status padding?
Setting or keeping a chat status as active during breaks or away time so that absence is not noticed. It is a symptom of a team being judged on presence, and it disappears once presence stops being read.
4. How can managers tell if remote employees are working without checking status?
By looking at the work: output per week, focus-time trends, workload balance and the application mix, reviewed at team level. These answer the real question, which is whether work is getting done and whether anyone is overloaded.
5. How do you stop a team from padding their status?
Stop reading it, and say so. Set a chat response-time norm of a couple of hours so being away is normal, model it as a manager, and review output and focus trends instead. Padding and jigglers stop when status stops mattering.
6. Does monitoring software create the same problem as the green dot?
It can, if configured to show live active lists and activity percentages. Configured to show focus time, output and workload by week, with short idle gaps hidden and employee self-access on, it replaces the green dot rather than amplifying it.
Measure the work, not the dot E-Monitor reports focus time, output and workload by week, keeps short idle gaps off manager views, and gives every employee their own data, so nobody needs to perform presence. Sign up →