Chapters 16 to 18 put a person in charge of agents and of mixed teams, and each assumed a manager who can judge what the systems propose. This chapter examines that assumption. Managers have traditionally learned the craft through the small, repetitive work of first-line management: drawing up rosters, allocating cases, covering absences, writing the first assessment of a colleague's work and having the difficult conversation that follows. That is now the work scheduling systems, allocation agents and performance dashboards do first. The chapter asks what happens to managerial judgement, who is promoted when the visible evidence of good work is produced by a system, and how an organisation keeps the craft and the route into it. It concerns M2 Evaluation, because a manager who accepts an AI rating without the judgement to question it is no longer evaluating, and M4 Development, because the development of the next generation of managers is at stake; it touches M1 Direction, where most of the automated apprenticeship sat. It answers open question Q5, raised in Chapter 1: what happens to the people who would have become managers when the junior management work through which managers learned is automated.
The chapter builds on three conclusions of the earlier volumes. AI Threat, Chapters 6 and 14, concluded that automation erodes the skills of the people who must catch its errors and that automating junior work removes the route by which experts are made, with drafting first, unassisted practice, seeded-error drills and a team-level oversight-quality metric as the response (F66) (34, Nordqvist, 2026). The Transformed Security Architect, Chapter 15, concluded that keeping the craft is a design decision (F77), and its Chapters 21 and 22 that competence is evidenced by records of judgement exercised, not by certificates alone (F79) (36, Nordqvist, 2026). AI Red Team, Chapters 6 and 15, added that autonomy should be paced to the skills available to supervise it (F53) (33, Nordqvist, 2026).
Linda Hill followed nineteen new managers through their first year and found that becoming a manager is less a matter of acquiring techniques than a transformation of professional identity, learned mainly on the job, by making mistakes in front of the people affected (105, Hill, 2003). Henry Mintzberg had described the same work from outside: brief, varied and fragmented activities, a preference for live communication, and a day shaped more by interruptions than by plans (89, Mintzberg, 1973).
Primary topics explored
- Learning to manage
- The automated junior management work
- Judgement and its decay
- Who gets promoted
- The narrowing route
- Freeing managers for relational work
About AI Boss
AI Boss is Book 7 of The Transformed Architecture. It examines what happens when artificial intelligence takes the manager's chair: algorithmic management of direction, evaluation, consequence, development and care, the effects on people, the management of AI agents, Europe's legal answer, and how to design an accountable AI boss, 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 and The Transformed Security Architect.
Executives, line managers, HR and people leaders, works councils and trade unions, public employers, architects and AI governance leads, data protection and legal officers, procurement and programme leaders, and risk, compliance and audit.
Gunnar Nordqvist
Conceived, directed and published the books of The Transformed Architecture.
Continue with the full chapter
Chapter 19: Skill, Judgement and Who Becomes a Manager When AI Does the Managing in AI Boss gives the detailed explanations, practical examples and implementation patterns behind this summary.
This whitepaper belongs to “Managing Machines” and is one of 37 drawn from the manuscript.