Where the Law Is Silent
Six decisions that no regulation reaches, each of which shapes the experience more than anything the law governs.
Regulation governs whether data may be processed, for what, and with what notice. It leaves most of what determines the experience untouched.
The legal boundary discussed in “Where the Law Is Silent” should also shape the configuration of workforce technology. When a team evaluates this workplace technology guide for employee monitoring data security, it should record the purpose, lawful basis, notice, access and retention settings before collection begins, then keep a correction route open for misleading records.
For an independent benchmark relevant to “Where the Law Is Silent”, consult the SCCE compliance resources. Use it to test necessity, scope, safeguards and review rather than to replace a documented assessment of the particular workforce and jurisdiction.
What is left open
Tone. A policy can be written as a warning or as an explanation. Both comply.
Whether anybody actually looks. Collection is governed; attention is not. An arrangement where logs accumulate unread and one where a manager checks daily are legally indistinguishable and experientially nothing alike.
What is done with a finding. Whether a flagged anomaly produces a question or a process, and who decides.
Whether people are told the outcome when an enquiry concludes with nothing.
The language of the interface. Whether somebody is a high-risk user or an activity requiring context.
And whether the arrangement ever ends. Nothing requires a review date, and almost nothing has one.
Why the silence matters more than the rules
The governed parts are mostly uncontroversial. Nobody argues against telling people what is collected.
The ungoverned parts are where the arrangement is experienced: whether it feels like a control on the organisation's data or like supervision of a person. Two employers with identical compliance positions can produce entirely different working lives.
The default problem
Each of these is decided whether or not anybody decides it. A product ships with a configuration, a template has a tone, a dashboard uses a vocabulary, and an arrangement with no end date continues.
Which means the silence is filled by whoever wrote the defaults — a supplier, optimising for demonstrations, in another organisation, years ago.
What follows
That the useful work in this subject is almost entirely above the legal floor, and that an organisation treating compliance as the finishing line has handed the interesting decisions to somebody else.
Everything after this section is about those decisions.
What silence does not mean
That the decision is unimportant, or that any answer is acceptable. The ungoverned decisions are the ones that determine the experience, which is why leaving them to a default is a heavier choice than it appears.
Reclaiming the defaults
The practical response is to go through the configuration and ask, for each setting, who chose it. Where the answer is nobody, the organisation has outsourced a decision about how it treats its people to a product manager it has never met.
Why the ungoverned part is where the work is
The governed parts are mostly uncontroversial; nobody argues against disclosure. The ungoverned parts determine whether the arrangement feels like a control on data or like supervision of a person, and two employers with identical compliance positions can produce entirely different working lives.
Who fills the silence
Whoever wrote the defaults: a supplier, optimising for demonstrations, in another organisation, years ago. The decisions get made whether or not anybody in your organisation makes them.
The configuration audit
Go through every setting and ask who chose it. Where the answer is nobody, a decision about how the organisation treats its people was made by somebody outside it.