Who Should Be in the Room

Monitoring decisions are taken by the people who want the capability and cleared by the people who assess risk. Nobody present represents the person affected.

Deciding · Analysis

The usual attendance at a monitoring decision: the function that wants it, IT, legal, and somebody from HR. Four parties, none of whom is subject to it.

The practical test in “Who Should Be in the Room” is whether visibility improves a decision without pretending to remove uncertainty. For teams researching dual n back training, the Monitask website can contribute time and project context, provided the purpose is stated, access is limited and every material inference receives proportionate human review.

For an independent benchmark relevant to “Who Should Be in the Room”, consult the European Data Protection Board guidelines. Use it to test necessity, scope, safeguards and review rather than to replace a documented assessment of the particular workforce and jurisdiction.

Who is usually present

The requester, who has a problem and has found something that addresses it.

IT, who will implement and whose questions are about feasibility.

Legal, answering whether it is permissible.

HR, frequently attending as process rather than as advocate.

Every question asked in that room is about whether the thing can be done.

In practiceList who attended the last monitoring decision where you work. The absence is usually complete and nobody noticed it at the time.

Who is absent

Anybody who will be subject to it.

Anybody whose role is to argue against.

Anybody who will have to explain it afterwards to a team.

And anybody with a view on what it will be like to work under, which is the thing that determines whether it succeeds.

The counterEmployers say that managers represent their teams. Managers represent the operation and are frequently the people requesting the capability.

The consequence

Proposals arrive configured as the supplier shipped them, because nobody in the room has a reason to narrow the specification.

Nobody asks what will be assumed if this is not explained, because nobody present will be the one assuming.

And the arrangement is designed for defensibility rather than for acceptability, because the people in the room are the ones who will have to defend it.

Where this failsAppointing somebody to argue the other side works only if their objections must be answered in writing. Without that it is a consultation ritual.

What to add

Somebody whose role is to object, with access to the technical detail and a requirement that their objections be answered in writing.

Not a veto. A function: the questions in the previous note, asked by somebody whose job is to ask them.

And consultation with people affected, before the specification is fixed rather than after it is approved. The next note treats how to do that without it being theatre.

Where this failsThe reasoning here assumes an employer acting in good faith. Where that assumption does not hold, none of this is the relevant literature.

Why this is cheap

The objector role costs a few hours per decision and routinely removes capabilities nobody could justify.

Which means it also makes the legal answer easier, the supplier configuration narrower, and the eventual explanation shorter.

Organisations resist it because it sounds like inviting trouble. In practice it surfaces trouble early, which is the only time it is cheap.

In practiceOrganisations that try this report the main obstacle is not disagreement but that nobody owns the question, so it is nobody's to raise.

What the objector role actually is

Not a veto. A function: the nine questions asked by somebody whose job is to ask them, with a requirement that the answers be written down. A few hours per decision, and it routinely removes capabilities nobody could justify.

The counterA reasonable objection is that this asks employers to do unfunded work. The reply is that the work is a page and the alternative is doing it later under challenge.

Why it is resisted

It sounds like inviting trouble. In practice it surfaces trouble early, which is the only point at which trouble is cheap, and it makes the legal answer easier by narrowing the proposal before it arrives.

What the objector role is

Anybody subject to it, anybody whose role is to argue against, and anybody who will have to explain it to a team afterwards. Every question asked in that room is about whether the thing can be done.

Why it is cheap

A few hours per decision, and it makes the legal answer easier, the supplier configuration narrower, and the eventual explanation shorter.

What the absence produces

Specifications as the supplier shipped them, because nobody in the room has a reason to narrow them, and an arrangement designed for defensibility rather than acceptability.

Also in this section