Chapter 9 looked at the structure of the organisation: layers, spans and the tasks of the middle manager. This chapter goes one level down, to the work itself. When agents, assistants and people take part in the same workflow, somebody has to decide which task goes where, who owns the result, who owns each agent's identity and who can stop the chain. Those are decisions about how work is organised, and they belong to L3 Organise: shaping structure and work, including roles, workflows, human-agent teams and ownership. The tests of L5 Answer (Name, Explain and Reach, Chapter 12) are applied to the workflow throughout.
The chapter treats the task, not the job, as the unit of allocation, describes the human-agent team as named owners and mandates, sets out the role of the conductor and the rule of one accountable owner per workflow, deals with shadow AI, and shows the artefact that holds this together, the accountability map ACC-*, with worked examples for Hansa Mutual and Nordvik Region.
The chapter builds on conclusions of the earlier volumes. New roles follow the usage modes, among them the agent operator who may revoke an agent's credentials (F24; AI Governance, Chapter 14) (221, Nordqvist, 2026). Every machine identity has an owner, operators and an authority who are named people (F51; AI Red Team, Chapter 6) (223, Nordqvist, 2026). Small delegations erode skill and fallback until the documented fallback no longer exists (F69; AI Threat, Chapter 26) (224, Nordqvist, 2026). A role is a versioned artefact, and an agent team works under a written mandate manifest with the person who conducts it as the accountable verifier (F73 and F75; The Transformed Security Architect, Chapters 4 and 13) (225, Nordqvist, 2026). When an agent orchestrates other agents, the chain of accountability ends with a named person (F88; AI Boss, Chapters 16 and 17) (226, Nordqvist, 2026). The loop's own agent team works under per-agent mandates, a never list and a drilled stop (F130; AI Purple, Chapter 14) (228, Nordqvist, 2026), and AI Operations, Chapter 16, applied the same pattern to operations (229, Nordqvist, 2026). This chapter generalises the pattern to any leader who organises work in which AI takes part.
Primary topics explored
- Allocating tasks
- Human-agent teams
- The conductor
- Workflow ownership
- Shadow AI
- The accountability map
About AI Leader
AI Leader is Book 11 of The Transformed Architecture. It takes leadership as its subject and asks what happens when AI is used broadly: the five leadership functions (orient, decide, organise, enable, answer), the delegation ladder and the Level 4 prohibitions, the answerability principle (name, explain, reach), the span and the middle layer, human-agent work, the board and the management body, change and adoption as claims that need evidence, regulation (the AI Act, DORA, NIS 2, the GDPR), ethics and sovereignty, and the leader as a person, for European enterprises and public authorities.
It builds on the conclusions of Architecture as Code, AI Governance, AI Platform and Security, AI Red Team, AI Threat, The Transformed Security Architect, AI Boss, AI Blue, AI Purple and AI Operations.
chairs and members of boards, chief executives and executive teams, the changing C-suite, middle managers and first-line leaders, heads of public authorities and the politicians who oversee them, HR specialists, works councils and unions, architects who advise leaders, and supervisors and auditors.
Continue with the full chapter
Chapter 10: Organise Work: Human-Agent Teams, Workflows and Role Redesign in AI Leader gives the detailed explanations, practical examples and implementation patterns behind this summary.
This whitepaper belongs to “The Craft of Leading” and is one of 37 drawn from the manuscript.