RESEARCH · HUMAN–AI WORK DESIGN
Why Human–AI work design matters more than tool adoption
AI capability changes what is possible. Work design determines what the organization actually becomes: who does what, where judgement sits, how exceptions move, what expertise is retained, and whether better model performance produces better operating outcomes.
Adoption is an input. Work is the system.
Enterprise AI is often measured through licences, active users, prompts, copilots or deployed agents. Those measures describe access to technology. They say much less about whether work has become faster, more reliable, more intelligible or more valuable.
The same model can sit inside radically different operating arrangements. It can remove low-value effort, strengthen judgement and accelerate learning. It can also create review queues, hidden rework, fragmented accountability and faster execution of a poorly designed process.
The useful unit of analysis is the Human–AI work system: the connected arrangement of activities, decisions, evidence, people, models, conventional software, authority, controls, exceptions and feedback through which an outcome is produced.
WORK-SYSTEM ARCHITECTURE
1. Jobs are bundles of tasks, but work is a network
The ILO’s 2025 global analysis assessed nearly 30,000 occupational tasks and found that one in four jobs worldwide is potentially exposed to generative AI. The more important design implication is that transformation, rather than wholesale replacement, is the likelier outcome because most occupations still contain activities requiring human input.
Task decomposition is therefore necessary but not sufficient. Removing drafting time may increase review demand. Automating retrieval may change how expertise is exercised. Accelerating analysis may shift the bottleneck to approval. A local productivity gain can improve, degrade or leave unchanged the performance of the wider workflow.
Do not stop at “Can AI perform this task?” Ask what changes upstream, downstream and at the decision boundary when it does.
2. Decompose the work before assigning the technology
A useful decomposition separates five different objects that are often collapsed into one process map: activities performed, decisions made, evidence required, handoffs between actors and systems, and exceptions that break the normal path. AI can affect each differently.
3. Allocation needs more than automate versus augment
Human–AI allocation should follow the requirements of the outcome: consequence, ambiguity, reversibility, context, speed, repeatability and learning. Conventional automation remains preferable when rules are stable and deterministic. AI becomes useful where interpretation, synthesis, generation or probabilistic judgement adds value. Human work remains central where contextual responsibility, negotiation, novel exceptions or consequential judgement dominate.
The allocation is a design hypothesis. It should change when operating evidence shows a better configuration.
4. Authority is a separate design variable
Capability does not imply permission. A model may be technically able to generate a recommendation or trigger an action long before the organization has enough evidence to grant it that authority. Human oversight is therefore not a label placed on a workflow; it is work with time, information, competence and escalation requirements.
OECD employer evidence makes this boundary concrete: managers report decision-quality benefits from algorithmic management, while unclear accountability for wrong decisions and difficulty following algorithmic logic remain prominent concerns.
5. Individual productivity does not automatically redesign work
A 2025 field experiment across 66 firms and 7,137 knowledge workers found that workers given access to an integrated generative-AI tool who used it saved roughly two hours of email time per week and reduced after-hours work, without detectable broader changes in task composition from individual-level provision alone.
A person can therefore become more efficient while the workflow, decision structure and operating model remain substantially unchanged. Capturing released capacity requires an organizational choice: remove work, increase throughput, deepen analysis, shorten cycle time, change staffing, redesign roles—or allow the time to dissipate.
6. Exceptions determine where judgement really lives
Routine-path automation is usually easier than exception architecture. Enterprise workflows contain incomplete data, conflicting signals, unusual customers, policy collisions, edge cases and changing conditions. These are often precisely where contextual judgement has most value.
A mature design specifies the normal path and the exception path separately: what the system may resolve, what requires more evidence, what must escalate, who receives the escalation, and what is learned from recurring exceptions. Repeated exceptions become operating intelligence: they can reveal weak rules, missing data, process defects, emerging risks or work that should never have been standardized.
7. Cognitive load moves; it does not simply disappear
AI can remove searching, drafting and reconciliation effort while creating new burdens: verification, monitoring, switching between machine and human representations, resolving uncertain outputs and supervising a larger volume of work. Review capacity is therefore a design constraint.
If AI increases throughput faster than humans can verify consequential outputs, the system has not removed the bottleneck; it has moved it. Work design should measure review demand, interruption, queue growth and the evidence needed to challenge an AI recommendation—not only model latency or task completion time.
8. Expertise can be amplified—or quietly depleted
AI can make expertise more available by retrieving institutional knowledge and helping less-experienced workers perform difficult tasks. But work is also where expertise is formed. If people cease performing the diagnostic or interpretive work through which judgement develops, short-term productivity can coexist with long-term capability loss.
The design problem is temporal as well as operational: which skills must remain practiced, which cases should be reserved for learning, when should people inspect reasoning rather than only outputs, and how should knowledge from exceptions return to the organization?
A work system that optimizes only today’s throughput can consume tomorrow’s expertise.
9. Participation supplies design information
Worker involvement is not merely a change-management device. People performing the work hold tacit knowledge about exceptions, workarounds, customer realities and dependencies absent from formal process maps. OECD experimental evidence from three German manufacturing firms found that consultation among workers, managers and works-council representatives could produce technology designs perceived to preserve productivity gains while improving job quality.
The implication is practical: involve operators early enough to alter the architecture, not only late enough to explain it.
10. Measure the work system, not the model
These measures reveal whether an intervention improves the system or merely increases activity around a new tool.
11. A practical Human–AI work redesign method
The implementation unit should be a bounded work system: one consequential decision, workflow, role cluster or operating problem with identifiable inputs, actors, systems, controls and outcomes.
12. Tool adoption becomes useful when it disappears into better work
The strongest enterprise AI outcome is not widespread interaction with AI. It is a work system that produces better outcomes because AI has been placed where it has comparative value and surrounded by the organizational conditions required to use it well.
That shifts transformation from technology diffusion to organizational design. The questions become concrete: What work should change? Where should judgement sit? Which evidence should move faster? Which decisions can be delegated? What happens when the system is uncertain? How will expertise develop? What operating result will justify the intervention?
Sources
- International Labour Organization (2025), Generative AI and jobs: refined global index of occupational exposure.
- Dillon, Jaffe, Immorlica & Stanton (2025), Shifting Work Patterns with Generative AI, NBER Working Paper 33795.
- Dell’Acqua et al. (2025), The Cybernetic Teammate, NBER Working Paper 33641.
- OECD (2025), How widespread is algorithmic management in workplaces?
- Milanez, A. (2025), Exploring win-win outcomes of algorithmic management, OECD AI Papers.
- NIST, AI Resource Center / AI Risk Management Framework resources.
IMPLEMENTATION IMPLICATION
Design the work system before scaling the tool.
Start with one consequential workflow. Make work allocation, authority, exceptions, evidence and learning explicit. Build the smallest operational intervention, run it in the real workflow, and redesign from measured outcomes.
Enterprise AI Transformation →