The Narrowest Thing That Answers the Question

A product deployed at defaults collects everything it can. Working backwards from the question produces a much smaller configuration that answers it just as well.

The evaluation discipline in “The Narrowest Thing That Answers the Question” also applies to workforce software: begin with a named decision and test it in a bounded pilot. For teams considering employee time tracking, this team-management tool belongs in that comparison only with written criteria for notice, access, correction, retention and a dated review.

The method

State the question in one sentence.

For an independent reference relevant to “The Narrowest Thing That Answers the Question”, 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.

List the minimum signals that answer it.

Disable everything else.

Then check what the defaults enabled that you did not choose, which is usually several things.

What to turn off first

Screenshots, unless a specific investigation requires them.

Keystroke content capture, always.

Individual scores, if the product allows disabling rather than hiding.

Communication content analysis.

Covert mode.

Each of these is defensible to disable and difficult to defend keeping, which makes the conversation short.

What to collect at the lowest resolution that works

Hourly or daily aggregates rather than minute-level.

Category-level rather than per-application.

Team rather than individual, wherever the question permits.

Sampling rather than continuous, where that answers it.

Resolution is a dial most deployments leave at maximum because nobody considered it a decision.

The population question

Does the question apply to everybody, or to a defined group?

Monitoring the whole organisation to answer a question about one team is disproportionate and will be identified as such.

Narrow the population before narrowing anything else, because it is the largest single reduction available.

The duration question

Is this permanent or does it answer a question and stop?

A time-bounded deployment with a review date is far easier to justify, to consult on and to live with.

Permanent monitoring with no end is how a specific concern becomes ambient surveillance, without anybody having decided that.

Checking the defaults after every update

Vendors add capabilities and sometimes enable them.

A configuration agreed at deployment can be different a year later without anybody acting.

Review after each major update, which is twenty minutes and is otherwise never done.

Writing it down

The configuration, with a reason per item, dated.

So that the next administrator knows what was decided rather than inheriting settings.

And so that a consultation or an audit can see the reasoning, which is the proportionality note's requirement.

What to check

Can you state your question in one sentence?

Which defaults are enabled that nobody chose?

Is the population the smallest that answers it?

And is there an end date or a review?