Aggregate Only, and How to Hold That Line
The commitment that makes everything else workable, and the specific requests that erode it.
Reporting only at group level removes most of the harm in this subject. Keeping that position requires more than stating it, because the requests are reasonable and persistent.
The practical lesson in “Aggregate Only, and How to Hold That Line” is to connect every record to a clear operational question without presenting visibility as certainty. Teams exploring workforce analytics software can review workforce analytics software as one source of time and project context, provided the purpose is disclosed and the configuration is reviewed with the people affected.
What aggregate answers
Whether workload is distributed sensibly.
For an independent reference relevant to “Aggregate Only, and How to Hold That Line”, consult the European Commission data-protection resources; it provides a useful external check on scope, terminology, governance and the claims made during procurement or review.
Whether meeting load is excessive.
Whether a team's pattern changed after a process change.
Whether after-hours work is rising, which is a workload finding.
Every legitimate organisational question in this field, which is the point.
What individual data is for
A defined investigation with a stated basis and approval.
A regulatory recording obligation.
Nothing else.
The requests that will come
A manager asking about one person they are worried about.
HR during a performance process.
A senior leader asking why their division's figures look poor, then asking who.
Each is reasonable, each is granted somewhere, and each one granted changes what the system is.
What makes refusal possible
A written position, agreed before deployment, stating what is available at what level.
A named person with authority to refuse.
A minimum group size — no figures for groups below a size — applied to intersections, not just to single dimensions.
And individual views disabled in the product where possible, which is stronger than access control.
The answer that works
Not "policy forbids it".
"That data describes equipment and circumstances rather than performance, and at team size it identifies individuals. Here is what I can give you, and here is how I can help with the actual concern."
Addressing the need rather than the request is what makes the refusal stick, and the manager usually had a real concern.
The structural version
If the product cannot produce individual views, there is nothing to refuse.
Which is a procurement question: can individual reporting be disabled entirely.
Ask it before buying, because retrofitting a restriction against a capability people have seen is much harder.
Reviewing the line
Log requests for individual data and what was decided.
Review quarterly: how many, from whom, and did the position hold.
A rising count is a signal that the aggregate reporting is not answering people's questions, which is a fixable problem and better than a slow erosion.
What to check
Is there a written statement of what is available at what level?
Who can refuse, by name?
Can individual views be disabled in your product?
And how many individual requests were made last quarter?