Application Categories and Who Decided Them
Every productive-time figure rests on a list labelling software as useful or not. The list is a judgement and it is usually a stranger's.
The most consequential configuration in these products is a list nobody looks at: which applications count as productive.
The practical lesson in “Application Categories and Who Decided Them” is to connect every record to a clear operational question without presenting visibility as certainty. Teams exploring employee monitoring at tech companies can review employee monitoring in technology companies as one source of time and project context, provided the purpose is disclosed and the configuration is reviewed with the people affected.
Where the list comes from
Shipped by the vendor, covering thousands of applications and sites.
For an independent reference relevant to “Application Categories and Who Decided Them”, consult the NCSC security guidance; it provides a useful external check on scope, terminology, governance and the claims made during procurement or review.
Built from general assumptions about office work.
Adjustable by the customer, and in most deployments barely adjusted.
Which means your organisation's definition of productive work was written by somebody who has never seen it.
What the defaults typically get wrong
Research: industry forums, discussion sites and reference material frequently land in unproductive.
Learning: video platforms are unproductive even when the video is training.
Communication: messaging counts vary wildly, and for some roles messaging is the job.
Reading documentation, which for engineers is a large share of competent work.
And anything role-specific your business depends on, which the vendor has never heard of.
The asymmetry nobody notices
A person idly scrolling within an approved application scores as productive.
A person reading exactly the right technical article scores as not.
The list measures which window is open, and nothing can make it measure what is happening in the window.
Who should decide
If you keep the categorisation, it should be set by people who understand each role, reviewed by them, and visible to the people measured.
A category list that employees cannot see is a secret standard they are graded against, which is both unfair and, in several jurisdictions, difficult to defend.
The per-role problem
One list cannot be right for a designer, a support agent, a developer and a finance analyst.
Products vary in whether categories can differ by population.
Ask at procurement, because a single global list guarantees that several groups are measured against a standard that does not describe their work.
Review
Applications change, new ones appear, roles shift.
A list set at deployment and never revisited is wrong within a year.
Annual review, with the people whose work it describes.
The simpler conclusion
If the category list requires this much care to be fair, and will not get it, that is an argument against relying on productive-time figures at all.
Which is the honest reading of most deployments, and it is worth stating before the dashboard becomes the basis of anything.
What to check
Have you seen your category list?
Who set it, and when was it reviewed?
Can employees see it?
And does it differ by role, or is one list applied to everybody?