Designing AI Operating Models Around Humans

How humans are adapting to AI between June 2024 and June 2026, weighing measured benefits and harms, and how organizations should design operating models around human cognitive load and behavioural patterns rather than forcing adoption, covering cognitive overload from supervising multiple agents at machine speed (context switching, automation complacency, vigilance fatigue), the poor budget and value outcomes of top-down AI mandates and token-maximizing usage, the gap between model welfare functions (such as Anthropic's) and any equivalent human or worker welfare function, and how much good human outcomes depend on model training versus orchestration and deployment design.

GPT-5.5
financial
frontier
academic
vc
blogs
tech

Synthesised 2026-06-15

Narrative

The strongest business coverage in 2025 and 2026 points to a clear split between individual task gains and weak organisation-level returns. The Financial Times reported in June 2026 that workers save time with AI but lose much of it to 'botsitting' and a 'toggle tax' across multiple tools, while only a small minority see meaningful gains in company performance. That matches the 2026 FT reporting on AI's adoption problem, which found a large gap between employer enthusiasm and employee belief that AI will improve jobs.

The labour evidence is also more uneven than the broad 'AI lifts all boats' story. The FT and Focaldata found in April 2026 that daily use is concentrated among higher earners and more experienced staff, with a persistent gender gap, suggesting that AI often amplifies existing workplace advantages rather than flattening them. Formal studies reinforce that pattern: the NBER customer-support paper found the biggest gains among novice workers, while work on novice programmers and experienced open-source developers shows that assistance can also erode independent judgement or even slow skilled workers in realistic settings.

The better enterprise cases lean towards worker-in-the-loop design rather than mandates to use more tokens or more tools. The FT's October 2025 essay on adoption argued that firms should let employees shape where AI fits, train them properly and stay honest about cost-cutting aims, while Walmart's 2026 rollout paired AI deployment with certification and operational redesign. Studies on knowledge workers and worker well-being suggest the same lesson from a different angle: outcomes depend heavily on task choice, incentives, trust and the boundary between copilot support and over-automation.

Sources

ID	Title	Outlet	Date	Significance
f1	AI and the productivity paradox	Financial Times	2026-06	This FT newsletter gives a current enterprise view of AI's hidden supervision costs, including 'botsitting' and the 'toggle tax', and ties them to weak company-level productivity gains despite heavy employee usage.
f2	Successful AI adoption needs workers in the loop	Financial Times	2025-10	This piece is directly on point for operating-model design, arguing that firms get better results when employees retain agency and oversight rather than being subjected to abstract top-down AI programmes.
f3	High earners race ahead on AI as workplace divide widens	Financial Times	2026-04	The FT and Focaldata survey shows adoption is uneven by income, experience and gender, which matters for any claim that AI benefits are broadly distributed across organisations.
f4	AI's adoption problem	Financial Times	2026-05	This article captures the widening gap between executive optimism and worker scepticism, and links adoption failure to poor organisational messaging and weak trust.
f5	Walmart tells workers that AI will improve their jobs, not steal them	Financial Times	2026-06	Walmart offers a concrete case of a large employer trying to pair AI rollout with certification, workflow redesign and job-security messaging rather than explicit substitution.
f6	Generative AI at Work	National Bureau of Economic Research	2023	This field study remains one of the strongest pieces of causal evidence on measured gains, showing productivity improvements in customer support but with large differences by worker experience.
f7	The Widening Gap: The Benefits and Harms of Generative AI for Novice Programmers	arXiv	2024-05	This paper matters because it examines novice workers directly and highlights that AI can help complete tasks while worsening metacognitive habits and independent problem solving.
f8	Automation from the Worker's Perspective	arXiv	2024-09	Based on a large cross-country worker survey, this study shows that perceptions of benefit are conditional on job design, worker status and incentives rather than simple demographic labels.
f9	Measuring the Impact of Early-2025 AI on Experienced Open-Source Developer Productivity	arXiv	2025-07	This randomised study is useful because it cuts against the standard productivity story, finding that frontier coding tools slowed experienced developers in realistic project settings.
f10	Generative AI Uses and Risks for Knowledge Workers in a Science Organization	arXiv	2025-01	This organisational study distinguishes copilot use from workflow-agent use and documents risk concerns around security, publication norms and job effects inside a real science institution.
f11	AI and Worker Well-Being: Differential Impacts Across Generational Cohorts and Genders	arXiv	2025-11	Using OECD survey microdata, this paper is one of the cleaner pieces of evidence that AI's gains and harms vary by life stage and gender rather than a crude young-versus-old frame.
f12	Generative AI and the Reallocation of Time: Productivity, Leisure, and Fulfilling Work	arXiv	2026-02	This paper matters for ROI claims because it finds that time savings can be real while measured output barely moves, with some gains taken as on-the-job leisure rather than higher throughput.
f13	From Future of Work to Future of Workers: Addressing Asymptomatic AI Harms for Dignified Human-AI Interaction	arXiv	2026-01	This study names slow-building harms such as skill atrophy and loss of judgement, which are central to the question of whether better outcomes depend more on deployment design than model behaviour alone.