The first time someone brings monitoring results into a leadership meeting, they almost always bring screenshots. It is the most common mistake, and it fails twice: a screenshot cannot be compared to anything, and in a room it reads as surveillance rather than management.
The three numbers
1. Coverage. What share of the workforce is actually recorded, with the agent running? If it is 70%, the rest of the report is decoration. Coverage is the confidence interval on every other number.
2. Deviation rate. What share of person-days falls outside the expected pattern? Around 3% is healthy. 30% does not mean people are not working — it means the baseline is wrong, and the report is measuring your assumptions rather than their work.
3. Time to conversation. How many days pass between an anomaly appearing and someone talking to that person about it? If the answer is "never", the system produces suspicion and nothing else. This is the number that predicts whether the rollout survives year two.
Why screenshots are the wrong instrument
- No context. A capture does not show that the person covered two roles for three weeks, or that the ticket queue tripled.
- No comparability. One frame cannot be trended, so it cannot support a decision, only an impression.
- No scale. Nobody reviews 200 captures. The one selected for the meeting is always the most striking, not the most representative.
- It invites the wrong conversation. The meeting drifts to "is this legal / is this spying" instead of "do we need a second shift".
Compare months, not people
"Weekly active hours in support dropped from 6.1 to 5.4 after the shift change" leads to a staffing decision.
"Marta averaged 4.2 and Paul 7.8" leads nowhere, because you cannot act on it without first deciding whether the difference is skill, workload, or equipment — and that decision needs data you do not have.
Team-level trends survive scrutiny. Individual comparisons invite disputes you will lose on procedure, not on facts.
A one-page format
Three short paragraphs:
- What changed — one sentence, dated.
- Which number shows it — the trend, not the single frame.
- What was decided — the action, the owner, the date to review.
If there is no decision, the third paragraph does not exist, and the report should probably not be sent. Monitoring data that never changes a decision is a cost with a liability attached.
The mistake that ruins the data
If the first report is used to sanction someone, the second year of data will be false. People learn quickly which signal is rewarded, and they will produce that signal.
Say it in writing, on day one: what the data is for, and what it will not be used for. Then hold that line the first time it is inconvenient — that moment is what everyone is actually watching.
What to do before the first report
- Agree the three numbers with whoever will read the report, before you collect anything
- Fix the retention period for the report itself (it contains personal data)
- State the aggregation floor — no group smaller than five people
- Decide who can see the raw data versus the report
Ten minutes of agreement up front saves a year of arguments about methodology.
iMonitor EAM collects session and application metadata, file operations, USB events and keystroke counts on your own server — enough to produce the three numbers, without the content that turns a management report into an investigation.
General information, not legal advice.
Top comments (0)