INQUIRING LINE

Once AI agents can produce more work than any human can check, what actually changes about how we organize teams?

When agents produce work in abundance, how do human workflows need to shift?

This explores what people need to do differently once AI agents can generate drafts, code, decisions and outputs faster than humans can review them. Is the answer to supervise harder, or to change how the work is organized in the first place?


This explores how human work changes when agents can produce more than people can check one item at a time. The corpus has a fairly sharp answer: the bottleneck moves away from making things and toward designing how things get made. Instead of reviewing each output, people end up shaping the system that produces the outputs. McKinsey calls this moving humans "above the loop": small teams of agents organized around a business outcome, with people setting direction instead of approving every step Can AI agents truly operate above the loop at enterprise scale?. The same note adds a caution. Governance is lagging behind the ambition, and agents interacting with each other create risks that don't show up when you test each agent alone.

The most consistent finding is that dropping agents into existing workflows doesn't work. Deloitte and McKinsey both report that the gains come from redesigning a process end to end, not from adding agents on top of old steps Does agentic AI succeed through process redesign or workflow layering? Does agent quality matter more than workflow redesign?. McKinsey's look at more than 50 deployments found that teams obsessed with making the agent better often ended up with impressive-looking tools that didn't improve overall results. So the human job becomes mapping the work: deciding which steps an agent should own, where judgment has to stay with a person, and where hand-offs happen. Anthropic's engineering advice points the same way from the builder's side. Use the simplest setup that works, and save fully autonomous agents for tasks whose steps can't be planned in advance When should teams choose workflows over agents?. Abundance is not a reason to automate everything.

The less obvious shift is that delegation can start flowing in both directions. Holldack, Banh and Strobel argue that agentic systems can assign tasks *to* people, handing them decisions or responsibilities the system can't or shouldn't own Can AI systems delegate tasks back to humans?. That changes what a workflow looks like: a person may be one step in an agent-run process, not the boss at the top of it. This fits the MIT Sloan/BCG survey, where 76% of executives see agentic AI as a coworker rather than a tool. Agents both replace and support labor, so organizations end up managing them partly like staff and partly like equipment Does agentic AI fit the tool-or-coworker framework?.

At the scale of a single person, abundance shows up as interruption. In a study of 18 programmers, proactive coding agents cut effort but broke people's concentration. What helped was not fewer suggestions but visible signs of what the agent was doing and a shared view of the work in progress Do proactive AI coding agents actually disrupt programmer workflow?. Designers are converging on a related control, the autonomy slider. You set each task to suggest, draft, or execute, so the person decides how much output reaches them and in what form Should agent autonomy be a continuous slider or fixed levels?. The practical lesson is that people need a way to control how much agent output reaches them and when, not just more willpower to review it.

One gap to know about: the corpus says a lot about restructuring organizations and interfaces, but little direct evidence on review overload itself. It doesn't tell you how people should triage, sample, or verify a flood of agent output, or what that does to their skills over time. The engineering notes hint at one answer: make the agent system more predictable so there's less to check. Examples are explicit function calls instead of ambiguous tool selection Why do protocol-based tool integrations fail in production workflows?, and a bounded, schema-governed record of what the agent has committed to, so errors don't pile up over long workflows Can agents fail from weak memory control rather than missing knowledge?. Put another way, the way to cope with abundant output may be to make it trustworthy enough that people don't have to read all of it.


Sources 10 notes

Can AI agents truly operate above the loop at enterprise scale?

McKinsey describes AI-first workflows organized around outcome-aligned agent squads with humans providing strategic oversight, citing bank case studies showing efficiency gains. However, industry governance lags deployment ambition, and agent interactions create risks beyond individual component reliability.

Does agentic AI succeed through process redesign or workflow layering?

Deloitte argues many agentic AI implementations fail because organizations layer agents onto old workflows rather than redesigning operations. Success requires agent-compatible data architectures, robust orchestration, and new management models; HPE and Toyota illustrate this approach.

Does agent quality matter more than workflow redesign?

McKinsey's analysis of 50+ agentic AI builds shows that organizations gain value by redesigning entire workflows—mapping steps, identifying pain points, and fitting agents to specific tasks—rather than maximizing agent sophistication alone. Organizations that focus too heavily on the agent itself often end up with capable-looking tools that fail to improve overall results.

When should teams choose workflows over agents?

Anthropic recommends a simplicity-first discipline: optimize single LLM calls and workflows for decomposable tasks before adopting agents, since agents trade latency and cost for flexibility only when task paths cannot be predetermined.

Can AI systems delegate tasks back to humans?

Holldack, Banh and Strobel argue that agentic information systems capable of independent decision-making can transfer rights and responsibilities to humans, reversing the traditional one-directional delegation model. This requires moving beyond agency-primacy frameworks to delegation theory that accounts for bidirectional task assignment.

Show all 10 sources
Does agentic AI fit the tool-or-coworker framework?

A survey of 2,102 executives across 116 countries found 76% view agentic AI as a coworker rather than a tool. This duality creates operational tensions because agentic systems simultaneously substitute and complement labor, requiring both HR and asset management approaches that traditional either-or frameworks cannot accommodate.

Do proactive AI coding agents actually disrupt programmer workflow?

A study of 18 programmers found that proactive AI agents cut user effort compared to prompt-only interfaces, yet caused workflow disruptions. However, visible presence indicators and shared interaction context significantly reduced disruptions and improved programmer awareness of agent activity.

Should agent autonomy be a continuous slider or fixed levels?

The AI UX Playground glossary names the autonomy slider as a continuous control letting users dial agent independence per task, collapsing agency levels into three adjustable points: suggest-only, draft, execute. The pattern shows shared vocabulary among designers, though validation against other control shapes remains absent.

Why do protocol-based tool integrations fail in production workflows?

MCP integration caused non-deterministic failures through ambiguous tool selection and parameter inference. Replacing it with explicit direct function calls and single-tool-per-agent design restored determinism. A 306-practitioner survey confirms 85% of production teams build custom agents, forgoing frameworks.

Can agents fail from weak memory control rather than missing knowledge?

Agent performance degrades in long workflows because transcript replay and retrieval-based memory lack gating mechanisms. A bounded, schema-governed committed state that separates artifact recall from permanent memory write prevents error accumulation and constraint drift.

Papers this line draws on 8

The research behind the notes this line reads — ranked by how closely each paper relates.