The message arrives on a Thursday, always a Thursday, in the tone reserved specifically for changes nobody asked for: warm, slightly apologetic, thoroughly unnecessary in its reassurance. “We’re rolling out a new tool to help us get better visibility into how the team works. This isn’t about tracking anyone, it’s just about visibility.” The word “just” is doing an enormous amount of work in that sentence, roughly the same amount of work it does in “I’m just saying” and “it’s just a suggestion,” which is to say it is a small word standing in front of something considerably larger.

This is the “Just for Visibility” myth, the employer-facing cousin of every promise this category has taken apart so far. Where the others sold workers on autonomy, speed, or opportunity, this one sells management on a comforting idea: that the reason accountability feels hard to measure is a visibility problem, solvable with the right dashboard, rather than what it has almost always actually been, a trust problem that no amount of activity tracking was ever going to solve.

The Myth, As Sold To You

The pitch to leadership uses a specific, careful vocabulary, chosen because it sounds nothing like what it describes. Not surveillance, but “visibility.” Not monitoring, but “insights.” Not tracking, but “understanding how the team works so we can support them better.” The software itself is rarely subtle, keystroke logs, screenshot captures at random intervals, idle-time counters, a running “productivity score” assembled from all of it, but the language wrapped around it is deliberately soft, framed as a service to the very people it is watching.

The justification usually leans on fairness: this will protect quiet high performers from being overlooked, this will make sure everyone gets credit for the hours they actually put in, this levels the playing field between the person who is visibly typing and the person doing careful, slow thinking with their hands off the keyboard. It is a genuinely appealing argument, right up until someone asks the obvious next question, which is whether any of this actually measures whether the work was good, and the answer, every time, is that it does not, because that was never what the tool was built to measure.

Notice, too, who is nearly always exempt from the rollout. The dashboard rarely reaches the leadership team that approved it, a detail almost never addressed directly and almost always noticed anyway. If activity tracking genuinely served fairness, the argument for applying it evenly would be straightforward. That it consistently stops at a particular level of the org chart says something quiet but clear about which problem it was actually built to solve.

Where This Myth Comes From

Scientific management showed up on factory floors more than a century ago with a nearly identical promise: time a worker’s every motion closely enough, and the resulting data will reveal the one best way to do any job, benefiting everyone through pure, objective measurement. It did produce efficiency gains, on the narrow, repeatable tasks it was built to measure. It also produced an entire discipline of workers learning to perform the measured behavior rather than the actual goal behind it, a pattern that has repeated with almost total fidelity every time a new measurement technology has arrived since.

Call centers refined this into calls-per-hour and average handle time, metrics that reliably improved call speed and just as reliably taught agents to rush people off the phone before their actual problem was solved. Remote-work monitoring software is the newest costume on the same body, now applied to knowledge work that was never especially amenable to being measured this way in the first place. The tool changed. The underlying confusion, mistaking an easily countable proxy for the thing actually worth valuing, did not.

What makes the software version notably more totalizing than its factory-floor predecessor is scope. A stopwatch could only measure one motion at a time, on one factory floor, during one shift. A monitoring suite installed across an entire distributed workforce captures continuously, silently, and at a scale no supervisor with a clipboard could ever have managed, which means the same century-old mistake now gets made with far more data, far more confidence, and far less opportunity for anyone to notice the mistake being made at all.

What Monitoring Actually Measures

Every one of these tools measures a proxy for work rather than work itself, because activity is cheap to capture and value is not. Keystrokes, mouse movement, active-window time, and idle gaps are all trivially countable. Whether an email actually resolved a client’s problem, whether an hour of quiet thinking prevented a costly mistake three weeks later, whether the slowest person on the team wrote the only code nobody else had to fix, none of this shows up anywhere in the dashboard, because none of it produces a keystroke at the moment it matters most.

The predictable result is a second economy growing up alongside the first: entire product categories exist specifically to simulate activity for software built to detect its absence, devices that nudge a mouse every few seconds so a idle timer never triggers, browser tabs left auto-scrolling, keyboard shortcuts run in a loop. None of this is a moral failing on the part of the people doing it. It is the entirely predictable response to being measured on the wrong variable by a system with real consequences attached to the number it produces.

To Be Fair, Some Tracking Is Genuinely Legitimate

None of this makes all measurement illegitimate, which would be its own overcorrection. Time tracking tied directly to client billing serves an honest, specific, mutually understood purpose that has nothing to do with surveillance, because both sides agreed to it and both sides can see exactly what it produces: an invoice. Safety-critical roles, where an unresponsive operator genuinely endangers people, have a defensible reason to monitor attention in ways an ordinary desk job does not. The distinguishing feature, every time, is whether the measurement was designed around a specific, named, mutually understood purpose, or whether it was purchased first and justified afterward with whichever purpose sounded least alarming at the time.

The Trust It Actually Costs

Here is the paradox the rollout email never quite reckons with: a tool introduced to build confidence in remote work, almost by definition, communicates the opposite of confidence to everyone required to install it. Trust is not a resource a dashboard can generate. It is depleted, quietly and immediately, the moment someone is told their employer needs software to confirm they are actually working, regardless of how gently that need gets phrased in the announcement.

This cost rarely shows up on the same spreadsheet as the tool’s price, which is exactly why it is so easy to miss in the initial decision. It shows up later, in slightly higher attrition among people with other options, in a specific chilling effect on the kind of quiet, unscheduled thinking that never produces a keystroke but often produces the actual insight, and in a workforce that has learned, correctly, that its employer’s stated trust and its employer’s actual behavior are two different things worth tracking separately.

There is a specific irony worth sitting with here: the people most likely to leave over a monitoring rollout tend to be the ones with the most options elsewhere, which pushes the tool’s actual effect toward the opposite of its stated purpose. Rather than protecting quiet high performers, it often places a small, steady tax on retaining exactly the people whose hard-to-measure work was the entire justification for buying the software in the first place.

What Actually Helps

If you are the one deciding whether to introduce measurement, start from the outcome you actually want and work backward to whether activity data would meaningfully predict it, rather than starting from whatever a vendor’s demo happened to make countable. In most knowledge work, the honest answer is that finished, verifiable outcomes, a shipped feature, a resolved ticket, a closed deal, are both more meaningful and less invasive to measure than the process that produced them, and measuring outcomes does not require anyone’s screen to be recorded.

If you are the one being measured, it is worth understanding precisely what the tool captures and what it does not, since the gap between the two is usually larger than the rollout email implies, and knowing that gap changes how much weight the number deserves in any conversation about your actual contribution. Where possible, advocate directly for outcome-based accountability in place of activity tracking, framed not as resistance to accountability but as a request for the kind that actually reflects the work.

And if a mouse jiggler crosses your desk at some point, treat its existence as data in itself, a small, physical piece of evidence that the measurement in question was never quite measuring what it claimed to. A device built entirely to fool a system is, among other things, a fairly clear verdict on what that system actually deserved.

The Bottom Line

The word “just” will keep doing its quiet work in the next rollout email, softening a decision that was never really about visibility at all. The underlying problem, whether a specific person’s specific work was worth what it cost, was never a measurement problem waiting on better software. It was always a trust problem, and no dashboard yet built has figured out how to install that back into a relationship once the announcement making its absence obvious has already gone out.