AI Operations · Module 2 · The Craft

Diagnose: Triage, Root-Cause Analysis and the Incident Assistant

The lesson concerns O2 Diagnose: triage, hypothesis, test and handover under incident command, and the incident assistant that retrieves precedent, correlates changes, ranks hypotheses and drafts updates. Participants read five benchmark studies for what each does not show, examine automation bias and anchoring, learn the human decision points and the second-hypothesis rule, and build an incident record that marks every assistant contribution.

Lesson 7 of 31Chapter 790 minutes

Read the chapterThe whitepaperThe slides

All courses / AI Operations / Module 2 / Chapter 7

Learning objectives

After the lesson the participant can:

Key concepts

The assistant as evidence, not authority
The chapter's own conclusion: in diagnosis the assistant is a source of evidence and hypotheses and never the authority for an action. Its tool surface is read and annotate only, and a hypothesis is a reason to act, not an authority to act.
Second-hypothesis rule
Before an action of a class above annotate, notify or scale is taken on the assistant's top-ranked hypothesis, a person records a second hypothesis and one observation that would refute the first, from a source the assistant did not select, and the result.
Automation bias
Errors of omission and commission that follow from relying on an imperfect decision aid. The review cited reports that it occurs in naive and expert users and is not removed by training or instruction, so the controls that work cost time.
Replay of closed incidents
The organisation's own measurement: past incidents are replayed with the cause withheld and the assistant's ranking scored. Hansa Mutual's illustrative replay of 60 incidents put the right cause first in 24 and in the first three in 41.
The record as a state machine
The incident record's state, not a sentence in a free-text field, gates action: a state changes only through a named role, and closure is a guard that requires evidence.

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

What the incident assistant does

Match each capability of the incident assistant with the chapter's description of it.

Interactive exercise 2 · Scenario

The first-ranked hypothesis

Apply the chapter's design against anchoring before a consequential action.

Teaching plan

15 minThe teacher sets out diagnosis before AI: the hypothetico-deductive method, the weight given to what changed, and the roles of incident command.
20 minParticipants read Table 7.1 in pairs and for each of the five studies state the task, the setting and what the figure does not show.
15 minThe four-step debate on anchoring, followed by the table of human decision points and the assistant's ceiling for each.
30 minExercise: participants reconstruct an incident record with marked assistant contributions and a second hypothesis.
10 minDebrief comparing Nordvik Region's retrieval-only assistant at Level 0 Advisory with Hansa Mutual's ranking assistant at Level 1 Assisted, and the evidence behind each ceiling.

Discussion

  1. In INC-HM-2028-0871 the assistant's retrieval helped and its ranking was wrong. Why does the chapter insist on recording the two separately, including the wrong contribution?
  2. The controls against anchoring cost minutes during an incident. For which classes of action is that cost justified in your organisation, and for which is it not?
  3. Nordvik Region chose retrieval and Hansa Mutual chose ranking. What would have to be true of your data and your rota before ranking were defensible?

Written exercise

Exercise · 30 minutes

An incident record that marks the assistant

Take a closed incident from your own organisation, anonymised, or use the outline of INC-HM-2028-0871. Rewrite it as a record with the service and objective, the commander and operations lead, the timestamps of the first flag, the first acknowledgement and the declaration, and a timeline. Mark each contribution of an assistant by kind: retrieval, change correlation, ranking or drafting, and whether it proved right. For the action that resolved the incident, record the first hypothesis, a second hypothesis, the observation that would refute the first, its independent source and the result. Note who held the stop for the assistant.

Deliverable: An incident record of one to two pages with marked assistant contributions, three timestamps, a recorded second hypothesis with refuting observation, and named decision holders.

Self-test

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

  1. According to the table of human decision points, at what level does the assistant take part in accepting a hypothesis as the basis for action?

    Show the answer

    D. Level 0 Advisory, subject to the second-hypothesis rule
    Acceptance of a hypothesis is held by the operations lead with the commander, with the assistant at Level 0 Advisory. Level 2 Supervised is its ceiling only for opening a candidate incident and for declaration, which a person confirms.

  2. What does the chapter conclude a published benchmark figure, such as 11.34 per cent of OpenRCA failures solved, tells an organisation?

    Show the answer

    B. A bound on what it can reasonably hope for, and little about what its own assistant will do
    The studies differ in task, data and setting, so they give a map of difficulty and not a rate. The figure that transfers is the one measured on the organisation's own incidents, repeated when model, prompt or corpus changes.

  3. Why may the assistant open a candidate incident at Level 2 Supervised when declaration itself belongs to the incident commander?

    Show the answer

    A. The candidate is a draft record, inert until a person confirms it, and starts no roles, clocks or pages
    The table gives the reason: a candidate is inert until confirmed in one action, so a false candidate costs little. Declaration starts roles, clocks and records and is the commander's decision.