AI Boss · Module 1 · The Question

The AI Boss Defined: Management Functions, Degrees of Delegation and Accountability

The lesson turns the description of Chapters 2 and 3 into instruments. Participants learn the book's definition of the AI boss, the degrees of delegation per function and action class, the four criteria that set a degree, the default ceilings, and the rule that Level 4 Autonomous is never used for M3 Consequence. They examine the accountability problem in its two forms and write a first delegation profile on the model of DLG-NR-ROS-01 and DLG-HM-CTA-01.

Lesson 4 of 33Chapter 490 minutes

Read the chapterThe whitepaperThe slides

All courses / AI Boss / Module 1 / Chapter 4

Learning objectives

After the lesson the participant can:

Key concepts

AI boss
Any AI system or agent that performs part of a management function for or over a person. It acts for a person when it assists a manager who remains the one acting, and over a person when its output reaches the worker directly or takes effect without a manager acting.
Default ceiling
The highest degree an organisation should allow for a function unless a recorded decision justifies otherwise, set by reversibility for the person, breadth, the person's stake, and the law and agreements.
Named human decider
Not a signature. The decider can be identified, can decide otherwise with real authority, sees the information, has the time, is protected when deciding against the recommendation, and answers for the decision.
Moral crumple zone
Elish's term for responsibility misattributed to a human actor who had limited control over an automated system. In management it is the line manager who confirms a dismissal a score recommended without the means to decide otherwise.
Delegation profile
States for one system or team the degree per function and action class, the decider, the representatives' agreement, the stop path and the review. It also records the functions the system does not perform and the inputs it may not use.

Interactive exercises

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

Interactive exercise 1 · Sort

Default ceilings by action

Sort each action under the default ceiling Chapter 4 sets for it: the highest degree of delegation an organisation should allow without a recorded justification.

Interactive exercise 2 · Scenario

The degree as observed

Apply the chapter's practical guide for a first delegation profile to the situation below.

Teaching plan

15 minThe teacher presents the two definitions and tests them on cases: Hansa's claims assistant, an office assistant that proposes task owners, ShiftWise and the claims-triage agent.
20 minPresentation of the degrees, the four criteria and the default ceilings; participants explain why M2 Evaluation has a lower ceiling than M1 Direction and why M5 Care is asymmetric.
15 minDiscussion of the rule for consequences, the six capabilities of the decider, and the two failure modes: many hands and the moral crumple zone.
30 minExercise: groups write a first delegation profile for one system and check it against the definition of done in the chapter's practical guide.
10 minDebrief: groups read out one Level 3 class and its playbook, and the others test whether it is enforced outside the model.

Discussion

  1. The chapter says Hansa's claims assistant becomes part of an AI boss on the day its usage logs become a figure per handler. What does it mean that the boundary is crossed by a decision about data and not by a change in the model?
  2. Reversibility is judged from the position of the person affected: the evening a nurse arranged childcare for cannot be given back. How does that change the way you would classify routine scheduling actions?
  3. Open question Q2 asks who is accountable when a manager accepted a recommended consequence without reading it. What do you make of the chapter's answer that accountability can move to whoever set the volume?

Written exercise

Exercise · 30 minutes

A first delegation profile

Choose one system that already takes part in managing people: ShiftWise at Nordvik Region, the claims-triage agent at Hansa Mutual, or a system in your own organisation. Following the chapter's practical guide, list its action classes, at most fifteen, and assign each to a function by its effect on the person. Record the degree as observed, not as intended. Compare each class with the default ceilings and lower or justify any that exceed them. Name the decider for each class and the stop path, write the playbook and the excluded inputs for each Level 3 Bounded class, and state which functions are not delegated. Add the representatives' procedure and the review triggers.

Deliverable: A delegation profile in the form of DLG-NR-ROS-01: action classes per function with degree and decider, playbook and excluded inputs, functions not delegated, stop path, representatives' position and review date.

Self-test

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

  1. Why do Nordvik Region's open-shift offers sit at Level 3 Bounded in DLG-NR-ROS-01 without exceeding the ceilings of M2 Evaluation and M3 Consequence?

    Show the answer

    D. Because acceptance history and sick-leave history are excluded as inputs, so the action does not rank people
    The chapter says the class sits at Level 3 Bounded only because of the excluded inputs; without that exclusion the action would rank people and exceed the ceilings of M2 Evaluation and M3 Consequence.

  2. What is the default ceiling the chapter sets for an adverse M3 Consequence decision, such as rejecting an applicant or dismissal?

    Show the answer

    B. Level 1 Assisted
    For adverse consequences the ceiling is Level 1 Assisted: the system drafts and a named person decides with their own authority. Level 2 Supervised applies to favourable or neutral consequences applying a rule already decided.

  3. According to the chapter, what is Level 3 Bounded without a written playbook enforced outside the model?

    Show the answer

    A. Level 4 under another name
    The line between Level 2 and Level 3 is where per-decision approval stops; the playbook is what bounds the system, so without one enforced outside the model the system in effect acts at Level 4 Autonomous.