AI Operations · Module 6 · People and Career

Operators as People: On-Call, Toil, Trust and Wellbeing

The lesson treats operators as people and concerns all five functions. Participants learn what studies report on on-call duty, alert fatigue and toil, with the limits of each source; the ironies of automation and the moral crumple zone; blameless culture and psychological safety; what working-time law and co-determination require of rota design; and how an on-call charter records the response, rest, load and agent clauses agreed with employee representatives.

Lesson 25 of 31Chapter 2590 minutes

Read the chapterThe whitepaperThe slides

All courses / AI Operations / Module 6 / Chapter 25

Learning objectives

After the lesson the participant can:

Key concepts

Load as a design property
The chapter's first claim: the load on operators follows from the design of the loop, its alerts, rota and agents, and is not a personal failing. A breach of the noise budget is a finding on the alert rules, and the rota that carried the pages is not at fault.
Moral crumple zone
Elish's name for the pattern in which responsibility for a failure of an automated system lands on the nearest human operator. The charter answers it with a delegation record that names the delegator and owner of each agent.
Stop right without penalty
The rule that the stop right is exercised without approval and without penalty: an engineer who stops an agent on suspicion and is wrong has used the right as designed, and the review treats it as a data point for the observer's thresholds.
Response time as a working-time parameter
The chapter's organisational reading of Directive 2003/88/EC and the Court of Justice's judgments on stand-by: a very short response time and frequent call-outs weigh towards stand-by counting as working time, so page targets and page budgets are legal parameters as well as design ones.
On-call charter
The instrument, agreed with employee representatives before it takes effect, that records the response target, rest after a night call-out, the page budget, supervision limits for agents, the stop right and metrics reported for the rota and never the person.

Interactive exercises

Do them here and get feedback at once. Choose a card and then where it belongs, or drag it.

Interactive exercise 1 · Match

Charter clauses by usage mode

Match each usage mode with the clause of the on-call charter that the chapter's table sets against it.

Interactive exercise 2 · Scenario

A stop that turned out to be unnecessary

Apply the three design rules the chapter writes into the on-call charter.

Teaching plan

15 minThe teacher presents the table pairing each source of load with what studies report and the lever in the charter, stating the population and method of each study.
15 minDiscussion of automation and the operator: the ironies, complacency, the moral crumple zone and the three design rules, followed by blameless culture and its limit.
15 minInput on working time and co-determination in the two organisations, framed as organisational implications; participants list which of their own planned changes would need agreement first.
35 minExercise: participants draft an on-call charter.
10 minDebrief on the open question of whether AI relieves or intensifies the load, and how the charter decides it team by team.

Discussion

  1. The chapter found no independent study of operators' wellbeing under autonomous operations agents. How should an organisation act on a question the evidence leaves open?
  2. When an agent acts at Level 3 Bounded and something goes wrong at night, who in your organisation would be asked to explain it, and does your delegation record name that person?
  3. What would have to be true in your team for an engineer to stop an agent without hesitation and report a near miss without fear?

Written exercise

Exercise · 35 minutes

An on-call charter for one rota

For one rota, yours or Nordvik Region's technical on-call of eleven engineers, collect or estimate a quarter of facts aggregated for the rota: pages per shift, share marked actionable, out-of-hours pages that were not Tier 1, and night call-outs. Draft the charter as a list of checkable decisions: the response target per tier, rest after a night call-out, the page budget and what happens on a breach, limits on supervising agents, the delegation record that names delegator and owner, the stop right without penalty, and the metrics, reported for the rota only. List the clauses that need negotiation or agreement with employee representatives before they take effect.

Deliverable: A draft charter of one to two pages with numbered clauses, each with a number or rule that can be checked, and a list of clauses requiring agreement.

Self-test

Choose an answer to see whether it is right, or open the answer below each question.

  1. According to the chapter, who is at fault when a rota's noise budget is breached?

    Show the answer

    B. Nobody on the rota; the breach is a finding on the alert rules and the correlation policy
    The noise budget is a property of a rota and a service, reported for the team. A breach is a finding on the alert rules and the correlation policy, which is the chapter's claim that load is a design property.

  2. What does the chapter conclude about whether AI relieves or intensifies the load on operators?

    Show the answer

    D. It is open, and the charter decides it team by team
    The table of usage modes marks the effect on load as direction not measured. The chapter says the question is open and that the design of the charter, team by team, decides which way it goes.

  3. Why does a Tier 1 page target of five minutes to acknowledge matter beyond service levels at Hansa Mutual?

    Show the answer

    A. A very short response time bears on whether stand-by counts as working time, a question for counsel
    The chapter reads a response-time target as a working-time parameter: the constraints on stand-by, including response time and frequency of call-outs, are factors in the Court's test, so the question is live and goes to counsel.