When productivity falls, management's first instinct is to find someone to blame. “Lazy employees,” “unmotivated team,” “nobody wants to work.” But management science is unambiguous: in the vast majority of cases, the problem lies not in people but in broken processes. People want to work productively — the system gets in their way. An employee monitoring program is not a stick for catching slackers. It is a diagnostic scanner that shows where the system is actually failing.
In this article we will explore how an employee monitoring program identifies the real “bottlenecks” in business processes, why managers so often “treat the wrong problem,” how to find your own “Herbie” (the slowest component in the system), and how to expose bureaucracy — drawing on Tracy, Goldratt, and Clear.
The Illusion of “Bad Employees”: Why We Treat the Wrong Problem
Brian Tracy describes a classic case that perfectly illustrates the central management trap. A large corporation faced falling sales. Management's conclusion: the problem was in the sales department — “ineffective salespeople.” They spent enormous sums on reorganisation, retraining, and replacing staff.
The result — zero. Because the real cause was an accounting error: a bookkeeper had set prices significantly above the market. Salespeople were physically unable to sell a product priced higher than competitors. The problem was with one person in accounting, yet the entire sales department was being “treated.”
This is a fundamental management mistake — diagnosis without data. A manager sees a symptom (falling sales) and intuitively assigns blame (the sales team). Without objective data, intuition almost always points in the wrong direction.
An employee monitoring program breaks this trap by showing exactly where the process is breaking down:
| Symptom | Intuitive “diagnosis” | What the monitoring program often reveals |
|---|---|---|
| Falling sales | “Lazy salespeople” | Breakdown at the price / document approval stage |
| Missed deadlines | “The team can't keep up” | Bottleneck at a single approver |
| Low productivity | “Unmotivated people” | 40% of time spent in internal meetings |
| High turnover | “Disloyal staff” | Chronic overload caused by process chaos |
Peter Drucker, in The Effective Executive, reminds us: “the most common source of mistakes in management is not the wrong answer to the right question, but the right answer to the wrong question.” Without data, managers answer the question “who is to blame” when the right question is “what is broken in the system.”
Finding “Herbie”: The Theory of Constraints in Action
Eliyahu Goldratt, in his Theory of Constraints, formulated a principle that fundamentally changes how we approach productivity: any system moves at the speed of its slowest component. The only way to accelerate the entire system is to accelerate that bottleneck — everything else produces no effect.
Greg McKeown, in Essentialism, illustrates this with the “Herbie” metaphor from Goldratt's The Goal: on a hiking trip, the group moves at the pace of the slowest hiker (Herbie). To speed up the whole group, you don't need to make everyone run faster — you need to find Herbie and lighten his backpack.
In business, “Herbie” is the specific bottleneck slowing the entire system:
- A manager who takes weeks to approve documents
- Outdated software that causes everything to freeze
- One overloaded specialist through whom everything passes
- An approval process with five unnecessary steps
The paradox is that “Herbie” is usually invisible. Everyone can see that things are “generally slow,” but nobody can point to the exact point of delay. An employee monitoring program makes “Herbie” visible:
| How an employee monitoring program identifies “Herbie” |
|---|
| Shows which stage tasks get stuck at for the longest time |
| Reveals whose queue tasks pile up in without moving |
| Identifies which software causes the greatest delays |
| Highlights processes with the highest waiting times |
The key insight of the Theory of Constraints: increasing effort anywhere other than the bottleneck is a waste of resources. If your “Herbie” is slow approvals, hiring five more salespeople will accomplish nothing — their deals will still get stuck at the same approval stage. An employee monitoring program helps direct effort precisely where it will have impact.
→ On identifying bottlenecks — see the article Work Time Audit: 6 Blind Spots for Managers
“System-Imposed Time”: Exposing Bureaucracy
The third type of broken process that an employee monitoring program uncovers is “system-imposed time.” These are the hours the company itself consumes through its own bureaucracy: filling out forms, endless reports, approvals, meetings.
Employees often want to work productively, but the system itself gets in their way. Research shows that people stay late not because there is too much work, but because the office has become an interruption factory — meaningful work simply cannot be done during working hours.
An employee monitoring program exposes this reality without mercy:
| Source of “system-imposed time” | Typical share | What it means |
|---|---|---|
| Internal meetings | 20–30% of time | Often unnecessary or too long |
| Reports and forms | 10–15% | Bureaucracy that creates no value |
| Internal messaging | 15–20% | Constant interruptions |
| Approvals and sign-offs | 8–12% | Overcomplicated processes |
| Duplicated work | 5–10% | Absence of a unified system |
If an employee monitoring program shows that your best specialists are spending 40% of their day in internal meetings and messaging apps — the problem is not their motivation. The problem is a toxic corporate culture and broken communication processes.
Drucker was blunt: if people spend a quarter of their time or more in meetings, it is a sure sign of poor work organisation. A one-hour meeting with ten people is not a one-hour meeting — it is a ten-hour meeting (ten person-hours of productivity exchanged for one hour of conversation). An employee monitoring program makes this arithmetic visible.
→ On “system-imposed time” and bureaucracy — see the article Time Tracking System: From Startup to Corporation
Metrics That Heal, Not Harm
A critical caveat: an employee monitoring program can itself become the source of a problem if used incorrectly. James Clear warns of Goodhart's Law: “When a measure becomes a target, it ceases to be a good measure.”
If you use monitoring solely to punish employees for “unworked minutes,” you will get a performance of activity rather than actual work. The human brain always seeks to “win” at whatever game it is forced to play. Measure hours of activity — you will get Mouse Movers. Measure message counts — you will get chat spam.
| Wrong use (harms) | Right use (heals) |
|---|---|
| Punishing employees for “unworked” minutes | Identifying systemic obstacles |
| “Hours of activity” as a KPI metric | Analysing process efficiency |
| Focus on “catching the slacker” | Focus on “removing friction” |
| Pressure on people | Removing obstacles for people |
| Result: performance of work | Result: real improvement |
The principle of correct use: an employee monitoring program tracks process efficiency rather than pressuring people. As the experience of outstanding companies shows — for example, steelmaker Nucor with its legendary culture — the goal of rigorous systems is not to turn lazy people into industrious ones, but to create a friction-free environment where industrious people can thrive.
Clear reminds us of a foundational principle: the system should serve people, not people the system. An employee monitoring program should make work easier by removing obstacles — not harder by adding pressure.
→ On Goodhart's Law and false metrics — see the article Computer Time Tracking Software: The 40-Second Rule
How to Run a Process Diagnostic: 5 Steps
An employee monitoring program used as a diagnostic scanner operates according to a clear methodology. Here is a proven sequence for diagnosing business processes:
Step 1 — Collect a baseline (2–3 weeks). Launch monitoring without making any changes or drawing any conclusions. Simply gather an objective picture: how time is actually distributed, where tasks get stuck, how much goes to meetings, communication, and real work.
Step 2 — Identify “Herbie.” Find the bottlenecks: at which stages do tasks take the longest? Whose queues accumulate tasks without movement? Which software causes the most delays?
Step 3 — Measure “system-imposed time.” Calculate how much time the team spends on bureaucracy: meetings, reports, approvals, internal communications. This is your potential for freeing up resources.
Step 4 — Test hypotheses. Before “treating” people, verify whether the problem actually lies with them. It often turns out that low productivity is a consequence of systemic obstacles, not motivation.
Step 5 — Remove obstacles, don't punish people. Act on the data: clear the bottlenecks, cut bureaucracy, eliminate interruptions. Give hard-working people a friction-free environment.
| Step | Action | Result |
|---|---|---|
| 1 | Baseline | Objective picture |
| 2 | Find “Herbie” | Bottlenecks identified |
| 3 | “System-imposed time” | Resource-liberation potential |
| 4 | Test hypotheses | Protection from false diagnoses |
| 5 | Remove obstacles | Real improvement |
Legal Considerations: Monitoring Processes in Compliance with Labour Law
An employee monitoring program, even with a focus on processes, handles personal data and is governed by applicable law. Labour legislation establishes the obligation to keep records of working hours, and employers have the right to set internal work rules.
An important nuance for process diagnostics: when the goal is analysing processes rather than “controlling people,” this is easier to communicate to the team and reduces resistance. But the legal requirements remain the same:
- A company order on the implementation of the system
- Inclusion in internal work rules and regulations
- Written consent from employees (in accordance with personal data protection legislation)
- Recording of time and applications used, but not the content of communications
- Employee access to their own data
| Legal question | How the monitoring program addresses it |
|---|---|
| Working time records (Labour Code) | Automatic logging |
| Internal work rules | System formalised in documentation |
| Employee consent (personal data law) | Written consent obtained at rollout |
| Privacy of communications | Time is logged, not content |
→ On legal implementation — see the article Time Tracker: How to Choose and Implement One Legally
Conclusions
An employee monitoring program is not a stick for catching slackers. It is a diagnostic scanner of business processes that reveals where the system is actually failing. In the vast majority of cases, the productivity problem lies not in people but in broken processes: bottlenecks (“Herbie”), bureaucracy (“system-imposed time”), and a culture of interruptions. Used correctly, the program removes obstacles for hard-working people rather than pressuring them.
Key takeaways from this article
- In 70% of cases, productivity problems are caused by processes, not people (Tracy)
- Without data, managers “treat the wrong problem” (the accountant pricing case)
- “Herbie” (Goldratt): a system moves at the speed of its slowest component
- “System-imposed time”: meetings, bureaucracy, and interruptions consume 40%+
- Goodhart's Law: monitoring as a stick = performance instead of real work
- The goal is a friction-free environment for hard workers, not punishing slackers
FAQ
How is an employee monitoring program different from a regular time tracker?
In its focus of application. A time tracker answers the question “how much time was spent.” An employee monitoring program in diagnostic mode answers the question “where is the process breaking down”: at which stage tasks get stuck, which component is slowing the system, how much time bureaucracy is consuming. Technically it may be the same tool — the difference lies in how you read the data: to find someone to blame, or to find broken processes.
How do you convince the team that monitoring is about diagnosing processes, not catching slackers?
Through action, not words. The first decision based on the data must benefit the team: remove an unnecessary meeting, simplify a bureaucratic process, clear a bottleneck that had been frustrating everyone. When the team sees that data is being used to free them from friction rather than to punish them, trust follows. Also critical: the manager is the first to share their own data, demonstrating that this is not a “top-down surveillance” exercise.
What should you do if the employee monitoring program does identify a specific individual with low productivity?
First, check whether this is a consequence of systemic obstacles — perhaps all the bottlenecks converge on that particular person. If the problem is genuinely individual, it is grounds for a constructive conversation and coaching, not punishment. Data provides an objective basis for a conversation framed as “let's figure out what's getting in your way” rather than accusations. The goal is to help the person, not find a scapegoat.
