The activity trap
Activity percentage feels objective. A dashboard says one employee was 92% active and another was 48% active. It is tempting to treat that as a performance ranking. That temptation is dangerous.
Activity percentage measures input events such as keyboard or mouse activity. It does not know whether the work was valuable, whether the person was thinking, whether they were in a client call, or whether the activity was generated by automation.
Where activity percentage helps
- Finding unexplained idle gaps in hourly work.
- Spotting possible data-quality issues in timesheets.
- Understanding broad work rhythm across a team.
- Flagging sessions that need review before billing.
Where it fails
- Knowledge work that includes thinking, reading, planning, or meetings.
- AI-assisted work where the person is reviewing generated output.
- Client calls where listening matters more than typing.
- Accessibility tools or remote desktops that change input patterns.
- Fake activity tools that generate movement without work.
Better KPI stack
- Verified hours: Time connected to a credible work session.
- Proof of work: Evidence that supports the claimed work.
- Output shipped: Deliverables completed or moved forward.
- Focus depth: Uninterrupted blocks for maker work.
- Review exceptions: Sessions that require human review.
- Trend direction: Week-over-week changes, not one-day snapshots.
Manager script
I noticed your activity percentage was lower than usual on Wednesday, but I do not want to read that in isolation. Can you walk me through the work pattern that day?
The bottom line
Activity percentage is useful context and a terrible verdict. Treat it like a smoke alarm, not a performance score.