Monitoring employees’ computers: a blind spot of a manager who doesn’t see the team in the office

“When everyone was in the office, I could ‘feel the pulse.' I saw who was at their desk, who was in the meeting room, and who had been drinking coffee for three hours straight. The shift to remote work took that feeling away. Now, I have 25 icons in Slack, 3 of them are ‘green,' and I have zero understanding of what is actually happening. My first thought: ‘Maybe I should install monitoring software?'”

This thought is a reflex. When a manager loses visual contact with their team, the brain looks for a substitute. And it finds it in employee computer monitoring: screenshots, activity trackers, and logging open windows. The logic seems flawless: I can't see the people—so let the software see for me.

But this logic is a trap. You are replacing one blind spot (lack of visual contact) with another (the illusion of control through pixelated data).

In this article, we will examine why office-style control doesn't scale to remote work, how a “knowledge worker” differs from a factory worker, and how to build a management system for teams you cannot see—based on Drucker, Basecamp, and Article 60-2 of the Labor Code regarding remote work.

Office Control: What You “Saw” Was Never Actually Control

Before discussing employee computer monitoring in a remote setting, one must understand an uncomfortable truth: what you called “control” in the office was not actually control.

You saw a person at their desk. That didn't mean they were working. You saw an open IDE on the monitor. That didn't mean code was being written. You saw a person arrive at 9:00 AM and leave at 6:00 PM. That meant only one thing—they were physically present for 9 hours.

Peter Drucker described this paradox back in the office era: no one can be certain if an employee is thinking about work while staring at a monitor—yet that might be the most productive moment of their day. Conversely, a person typing intensely might just be sending personal messages.

“After a year of remote work, I realized: I never actually controlled the team. I controlled their presence. And that is a completely different thing. Monitoring employees' computers became a temptation to restore that same illusion—but now through software instead of my own eyes.”

The shift to remote work didn't create the problem of control. It exposed it. The office masked the lack of real management behind a curtain of physical presence. Now the curtain is gone—and the manager sees a void.

The Knowledge Worker: Why Factory Methods Don't Work for Remote Teams

Drucker, in The Effective Executive, made a fundamental distinction that most companies ignore when implementing computer monitoring:

A factory worker produces things. Their productivity is measured by parts per shift. Process control = result control. More movement → more parts.

A knowledge worker produces solutions, ideas, code, and strategies. Their productivity does not correlate with the number of movements. More clicks ≠ better code. More hours at the monitor ≠ better analysis.

Drucker emphasized: a knowledge worker cannot be controlled closely or in detail—they can only be helped. Their specific job is thinking, and no screenshot will ever show what is happening inside their head.

This doesn't mean control isn't necessary. It means a different type of control is required—one focused on results, not the process.

“Мы installed computer monitoring with screenshots every 5 minutes. After a month, our CTO showed me two screenshots. First: a blank screen with an open terminal—'inactivity for 20 minutes.' Second: a busy screen with 15 tabs—'high activity.' The first screenshot was an architect thinking through a solution that saved us 3 months of development. The second was a junior aimlessly googling because they didn't understand the task.”

Article 60-2 of the Labor Code of Ukraine (Remote Work) directly acknowledges this reality: in a remote work setting, the employee independently distributes their working time. The law granted flexibility in scheduling—and this was no accident. The legislature recognized that for mental labor, rigid process control makes no sense.

The 1% Rule: Don't Punish 100% Because of a Few Individuals

The authors of Rework formulate a principle that most companies violate when implementing employee monitoring: don't write rules for the whole company because of 1% of violators.

In any team of 30 people, 1 or 2 will abuse their freedom. This is a statistical inevitability that no monitoring can fully eliminate. But creating a total surveillance system for 100% of the team because of those 1 or 2 people is like installing metal detectors in a library because of one book thief.

What happens when computer monitoring is scaled to “everyone”:

“We introduced screenshots for 45 employees because of one person who consistently failed to close tasks. Three months later, that one person still wasn't closing tasks (they just learned to keep the ‘right' window open). Meanwhile, three top performers left for a competitor that offered ‘normal conditions.' Monitoring employees' computers solved the problem of 1 person at the cost of losing 3.”

The Basecamp solution: if someone chronically fails to deliver results—have a conversation. If that doesn't help—fire them. Но don't punish the entire team with surveillance because of one person. It’s cheaper, more honest, and more effective.

The “Green Dot” is Not Control: The Trap of Remote Presence

The authors of It Doesn't Have to Be Crazy at Work described a new form of control that appeared with remote work: tracking statuses in messengers. Managers check the “green dot” in Slack or Teams and demand instant replies—this is their substitute for “seeing the person at their desk.”

This is what Basecamp calls the “Presence Prison”—and for remote teams, it is even more toxic than for office ones.

In the office, you could distract a colleague “for a second” and see that they were busy. In a remote setting, you write in Slack—and if a response doesn't come within 5 minutes, you start to get nervous: “Are they even working?”

Employee computer monitoring often exacerbates this trap: software shows “inactive for 15 minutes”—and the manager panics, even though the employee is just eating lunch, reading documentation, or thinking.

“I caught myself checking Slack statuses every 10 minutes. ‘Why is Olena offline?' ‘Why hasn't Maksym responded in 20 minutes?' This isn't employee monitoring—this is a manager's anxiety disorder. A results dashboard cured this anxiety in a week.”

Basecamp formulates the solution clearly: the only way to know if a person is working is to look at the results of their work. Not at a green dot, not at a screenshot, not at an ‘activity %'—but at closed tasks, submitted projects, and written code.

How to Manage Those You Cannot See: 5 Principles

If “police-style” employee computer monitoring doesn't work, what does work for remote teams? Here are five principles proven by companies from Basecamp to GitLab.

Principle 1 — Agreement on Results, Not the Process

Stephen Covey describes stewardship delegation: you fix the “what” and “when,” and the “how” is decided by the performer. For remote teams, this is the only scalable approach. Instead of “work from 9 to 6 and keep your screenshots clean,” use “the API endpoint must be ready by Friday; here are the quality criteria.”

Principle 2 — Async “Heartbeats” Instead of Sync Stand-ups

Basecamp practices Heartbeats—short written reports once a week where everyone describes: what they did, what they plan to do, and where they are stuck. This replaces daily stand-ups that eat up 30-45 minutes and require simultaneous presence.

Principle 3 — Tracking Time by Project, Not by “Activity”

An automatic tracker records the distribution of time by category (Project A — 4 hours, meetings — 2 hours, admin — 1 hour)—without screenshots, without keyloggers, without measuring “mouse movements.” This provides analytics, not surveillance.

Principle 4 — “Red Flags” for Anomalies, Not Minutes

Jim Collins describes this as needing information that cannot be ignored. For remote teams, this means: a task with no progress for 3 days; an employee logging 11+ hours/day systematically; a project receiving zero hours for a week. Specific alerts—instead of minute-by-minute monitoring.

Principle 5 — Trust as Default, Control as the Exception

David Allen, in Getting Things Done, suggests a “Waiting For” list—fixed expectations with review dates. For 90% of tasks, it's enough to say: “I expect the result by Friday. If it's not ready, we'll talk.” Increased control is only for specific situations, not for “everyone, just in case.”

“We rebuilt our remote employee computer monitoring based on these principles. The result after 3 months: team velocity increased by 22%, turnover dropped by half, and I freed up 6 hours a week that I used to spend reviewing ‘activity' reports. Because I no longer needed to ‘see' people—I saw their results.”

Legal Framework: Art. 60-2 of the Labor Code and the Limits of Remote Control

Law of Ukraine №1213-IX introduced Article 60-2 into the Labor Code, which regulates remote work. This article creates a legal framework that employee computer monitoring must take into account.

Key provisions of Art. 60-2:

• The employee independently distributes working time (within the limits of Art. 50 of the Labor Code).
• Working time and rest periods are determined by the employee independently.
• The employer is obligated to provide means of communication and technical resources.
• Communication between the employee and employer is carried out via information and communication technologies.

“A lawyer explained: Art. 60-2 gives the employee the right to independently determine their schedule. Our requirement to ‘be online from 9 to 6 with a green status' technically violated that right. We rephrased: ‘be available for communication during core hours 11:00-15:00, the rest is up to your schedule.' Computer monitoring remained—but it shifted from ‘monitoring presence' to ‘recording results.'”

The Law “On Protection of Personal Data” (Art. 6, 12) adds: monitoring employees' computers remotely requires written consent and notification of what data is being collected. For remote workers, this is especially critical: they work from home, and the line between work and personal life is blurred. A keylogger on a home PC that intercepts personal correspondence of family members is not just a violation of Data Protection Law, but a potential violation of Article 163 of the Criminal Code.

From “Seeing” to “Knowing”: The Evolution of Control

Monitoring employees' computers is an attempt to see what is happening. But managing a remote team requires you to know, not just see. The difference is fundamental.

Brian Tracy formulates a rule for remote team managers: set clear goals and deadlines. If a person performs their work with quality and on time, it shouldn't bother you how many YouTube videos they watched in the process. If they don't perform, computer monitoring won't solve the problem anyway. Conversation, training, or replacement will.

Basecamp adds: look for and hire “managers of one”—people capable of independently setting goals and executing them without daily supervision. For remote teams, this isn't a suggestion; it's a survival requirement. If every employee needs a daily “look over their shoulder,” your problem isn't monitoring; it's hiring.

“The best solution for remote employee monitoring is to stop monitoring computers and start monitoring results. The computer is the employee's tool. The result is the product for the business. Control the product, not the tool.”

Conclusions

Monitoring employees' computers is a temptation to restore “visual contact” with a team you can't see. But what you saw in the office was never actually control. And what monitoring software shows won't provide control in a remote setting. Real control is knowing the results, not watching the screens.

Key takeaways from this article:

• Office “presence” never equaled “productivity”—remote work simply exposed this.
• Knowledge Worker (Drucker): You cannot control the thinking process—control the result.
• The 1% Rule: Don't punish 100% of the team with surveillance because of 1-2 violators.
• The “Green Dot” is not control: It is a manager's anxiety disorder.
• Art. 60-2 Labor Code: Employees distribute their own time—the “online from 9 to 6” requirement is disputable.
• 5 Principles: Results, heartbeats, project-based tracking, alerts, and trust as default.

“Monitoring employees' computers is the answer to the wrong question. The question isn't ‘what is the employee doing at the computer?' The question is ‘what has the employee done for the business?' When you learn to ask the second question, the first one ceases to matter.”

FAQ

How to control a remote team without screen monitoring?

Three tools: agreement on results (what and when), an automatic tracker (time distribution by project, not “activity”), and weekly heartbeat reports (a 5-minute written status). Tracking time by project provides more insights than a thousand screenshots.

Can I install monitoring on an employee's home PC?

Only on a corporate device and only with written consent (Art. 6 of the Law “On Protection of Personal Data”). If the employee uses a personal PC, your options are limited to time tracking and access to corporate systems. Keyloggers or screenshots on a personal PC are a legal risk (Art. 31 of the Constitution, Art. 163 of the Criminal Code).

What if a remote employee doesn't deliver results and there is no monitoring?

The same thing you do with any employee failing to deliver: a specific conversation with data (“this week 3 out of 7 tasks weren't closed—what is hindering you?”), an improvement plan for 2-4 weeks, and a re-evaluation. If that doesn't help, termination (Clause 3 of Art. 40 of the Labor Code for systematic failure to perform duties). Screen monitoring doesn't solve performance issues—it only records the symptoms.