\cleardoublepage \part{Designing the Accountable AI Boss} \setbookpart{Designing the Accountable AI Boss}

Part VI: Designing the Accountable AI Boss

The earlier parts described the AI boss, weighed its effects and read the law that governs it. This part designs it. Its premise is the thesis of Chapter 1: AI may direct work, but it may not, on its own, decide about people. Turning that sentence into practice requires artefacts that an organisation can version, test, show to a worker and defend before a works council, a court or a supervisory authority. The series has built such artefacts before: the Architecture Decision Record of Architecture as Code, the AI Decision Record of the AI volumes, the delegation register of AI Threat, Chapter 26, and the mandate manifest and oversight-quality metric of The Transformed Security Architect. This part extends them to management.

The design has four elements and one consequence. Every management decision that AI makes or shapes about a person becomes a record the person can see. Every review of an AI recommendation is real and measured, not a click. Every decision can be explained, contested and corrected. Every worker is told which systems manage them, how and by whom. The consequence is a changed role for the line manager, who becomes the accountable leader of people and the conductor of agents rather than the supervisor of tasks that a system now assigns.

Chapters in this part:

  • Chapter 25, Management Decisions as Records: Decision Records and the Delegation Register, introduces the Management Decision Record (MDR) and the delegation register of management functions, with a delegation profile per system and team that states the degree of delegation for each function.
  • Chapter 26, The Human in the Chair: Oversight That Is Real, Not Rubber-Stamped, designs human oversight that survives volume and automation bias, with the oversight record and an oversight-quality metric.
  • Chapter 27, Contestability by Design: Explanation, Appeal and Correction, designs the explanation a worker receives, the appeal path, the contestation record and the correction that flows back into the data and the system.
  • Chapter 28, Transparency to the Managed: What Workers Are Told, When and by Whom, designs the worker information notice and the transparency register that serve the AI Act, the GDPR, the Platform Work Directive and co-determination at once.
  • Chapter 29, The Transformed Manager: Leading People When AI Directs the Work, describes the manager's role after the AI boss, what remains scarce in it, and the author's own projection of where it is heading, labelled as such.

Management functions in this part. Chapter 25 covers all five functions, because the delegation register states a level for each. Chapter 26 concerns chiefly M2 Evaluation and M3 Consequence, where rubber-stamped oversight does most harm. Chapter 27 concerns M3 Consequence. Chapter 28 concerns M1 Direction, M2 Evaluation and M5 Care, because what workers are told shapes their voice. Chapter 29 concerns M4 Development and M5 Care, the functions that remain most firmly with people. Every chapter names the functions it concerns in its opening and its Summary, and the rule of Chapter 4 holds throughout: Level 4 Autonomous is never used for M3 Consequence.

The thread from Part V. Part V showed that European law requires records, oversight, explanation, information and consultation, and that the requirements overlap. Part VI answers them with one coherent set of artefacts rather than one document per instrument. Each artefact appears in the chapter that introduces it, as a worked example at Nordvik Region or Hansa Mutual, and in fuller form in Appendix A; the templates are listed in Appendix B.

What you will learn in this part:

  • How to write a Management Decision Record and keep a delegation register of management functions
  • How to set a delegation profile for a system or team, function by function
  • How to make oversight real and measure whether it is
  • How to design explanation, appeal and correction into the system from the start
  • What to tell workers, when and by whom
  • What the line manager's role becomes, and what it needs

Part VII follows two organisations through a year with these designs and draws the verdict.