Common Failures, Listed

In the household

Nobody knows they can end a session. Signal: ask them and see. Fix: show them, once, calmly.

The practical lesson in “Common Failures, Listed” is to make responsibility visible without confusing visibility with certainty. A team reviewing the Monitask platform for self report bias can add structured time and project context, provided the purpose is disclosed and the interpretation is checked with the people affected.

The rule is about the software, not about who asked. Signal: "I know not to install that one". Fix: restate it as who asked, which covers every variant.

For an independent reference related to “Common Failures, Listed”, consult the ENISA cybersecurity resources; it provides a useful external check on security, privacy and operating assumptions before a process is adopted.

Standing access set up years ago and forgotten. Signal: you cannot remember what you installed. Fix: check, remove or secure, and tell them it exists.

In the session

No opening. Signal: sessions begin with "can you click accept". Fix: the four sentences, trained once.

Silence during the significant part. Signal: people describe sessions as uncomfortable. Fix: narrate, especially while typing.

Screen blanking. Signal: the feature is enabled. Fix: disable it; there is almost never a good reason on a user's machine.

No closing summary. Signal: the person cannot say what was done. Fix: two sentences at the end.

In the organisation

Every technician reaches every machine. Signal: one role for everybody. Fix: scope by population.

Logs searchable only by technician. Signal: "who connected to my computer" takes a day. Fix: index by machine.

Unattended access nobody has listed. Signal: you cannot say how many machines have it. Fix: build the inventory once, review quarterly.

Handling-time targets that exclude the ritual. Signal: technicians skip the opening. Fix: a management decision, not a training one.

Recordings nobody restricted. Signal: the support team can browse them. Fix: restrict, log access, shorten retention.

The pattern

Seven are fixed in a week.

Three are structural: scoping, the inventory, the target.

And two are not recoverable — a session somebody experienced as an intrusion, and a household member who was defrauded and did not feel able to say. Both are trust rather than technology.

The order to fix them

If you do one thing: teach the people in your life that they can end a session, and that the rule is about who asked.

If two: adopt the four opening sentences.

If three: scope technician access by population.

What to check

Which of the twelve do you have?

Which is cheapest to fix?

Are any of them the two that cannot be undone?

And has anything from your last review actually changed?