RESHUFFLE An interactive companion to the book
Back to the lineage hub
Jobs · Framework · Lineage

Why automation vs augmentation is the wrong frame.

The 'automation vs augmentation' binary keeps the question stuck at the task. The bundle frame moves it.

  1. 01

    You keep being asked whether AI will automate this job or augment it. The conversation is framed as one or the other.

  2. 02

    Both answers are wrong because both assume the wrong unit of analysis. The unit is the bundle - and AI reconfigures it.

  3. 03

    The bundle frame replaces the binary. Below: what the binary forces you to miss, the frame that replaces it, and where the binary inherits from in the literature.

What the binary forces you to miss

Eight blind spots.

The binary's grammar - automate-or-augment - forces a wrong question. For each blind spot below: what the binary asks, what to ask instead, and why the binary's question fails.

  1. 01

    Wrong unit of analysis

    The binary asks

    Who does this task - AI or human?

    Ask instead

    Which bundle of work is being reconfigured, and into what?

    The binary asks about the worker and the task. The unit AI substitutes is a piece of a bundle - not a worker, not a single task. When AI handles part of the bundle, the bundle reconfigures: some pieces survive in the original role, some get rebundled into a different role, some get absorbed by an algorithmic platform. 'Automated' and 'augmented' are both inadequate descriptors of what happened.

  2. 02

    Wrong locus of value capture

    The binary asks

    Did the worker get more productive?

    Ask instead

    Where did value capture move, and to whom?

    Augmentation studies measure worker-level productivity gains. The gains rarely accrue to the worker. Value migrates upstream to the provider and, within the firm, to whoever sits above the algorithm. 'The worker is augmented' is a useful sentence only if the worker captures the gain - which is the question the binary doesn't ask.

    See the structural mechanism on Aspect 05
  3. 03

    Wrong cardinality

    The binary asks

    Which discrete task does AI do?

    Ask instead

    Which workflow, decision chain, or outcome does AI increasingly own end-to-end?

    Both poles of the binary presuppose a clean partition between an AI task and a human task. Agentic AI executes across the chain - calling tools, taking actions, reading replies, deciding the next call. There is no single task to assign. The binary's grammar cannot describe what an agent does.

    See the structural mechanism on Aspect 08
  4. 04

    Wrong story about what survives

    The binary asks

    Does the human still do the work?

    Ask instead

    What remains scarce, differentiated, and accountable after automation?

    Across roles where AI is most capable, the surviving human role centers on signature, attestation, sign-off, risk-bearing. AI produces the read, the filing, the diagnosis. What survives is the liability function, not the capability function. The binary calls this 'augmentation' because the human is still in the picture - but the role bundle has reconfigured around the constraint AI cannot dissolve, not around AI making the human better.

    See the structural mechanism on Aspect 07
  5. 05

    Wrong locus of coordination

    The binary asks

    Is the work being done inside the firm?

    Ask instead

    Where is the coordination layer moving, and who owns it?

    The binary lives entirely inside the firm. It has no name for what happens when unbundled fragments leave the firm and get reorganized through algorithmic platforms - dispatched, ranked, priced, monitored by the algorithm. That third locus is neither automation nor augmentation; it is a structural reorganization of where work happens.

    See the structural mechanism on Aspect 09
  6. 06

    Wrong horizon

    The binary asks

    Does AI automate this job or augment it?

    Ask instead

    How does AI's capability trajectory change the answer over the deployment lifetime?

    Both poles assume a steady state. Centaur explicitly assumes a stable human and AI complementarity. Asymmetric capability gain means yesterday's augmentation becomes today's automation, and the answer keeps moving. A binary that returns one of two answers cannot describe a phenomenon that updates its answer every six to twelve months.

    See the structural mechanism on Aspect 02
  7. 07

    Wrong scope

    The binary asks

    What happens to this job?

    Ask instead

    Which functions does this foundation model extend across, and what happens to the boundaries between them?

    Augmentation assumes AI affects one worker at one task. Cross-functional foundation models substitute across sales, engineering, support, and HR with the same model. The 'augmentation' of a sales rep is also the reorganization of the sales function and the displacement of the surrounding org structure. The binary thinks one role at a time; the model does not.

    See the structural mechanism on Aspect 04
  8. 08

    Wrong locus of capability

    The binary asks

    Does the firm possess this capability?

    Ask instead

    Which layers of capability are owned by the firm, and which are rented from the ecosystem?

    The binary assumes the capability to do the work lives inside the firm, so automating or augmenting is a choice the firm makes with assets it owns. Increasingly the model, the data, and the orchestration sit upstream with providers and platforms - the firm rents the capability rather than holding it. That reframes the decision: the firm no longer fully controls whether the work gets automated, and the surplus flows to whoever owns the layer the work depends on.

    See the structural mechanism on Aspect 05
The replacement

The bundle frame.

The bundle frame replaces the binary with four moves. Each move corresponds to a question the binary cannot answer.

  1. 01

    The bundle is the unit.

    Not the task, not the worker. The bundle is the package of work priced as a role. AI substitutes pieces of a bundle; the bundle reconfigures around what is left, what is new, and what the constraint requires.

  2. 02

    The constraint is the binder.

    Bundles hold together because something binds them - a credential someone must bear, a capability that is genuinely rare, a coordination point someone has to own. AI presses on the binder. When the binder gives, the bundle breaks. When the binder holds, the bundle survives but the parts redistribute.

  3. 03

    Reconfiguration is the mechanism.

    Not automation, not augmentation. The bundle reconfigures: some pieces go to AI, some get rebundled into new roles, some get absorbed by algorithmic platforms outside the firm. The reader's question moves from 'who does this task' to 'where did the bundle go.'

  4. 04

    Above-vs-below-the-algorithm is the capture diagnostic.

    Where the algorithm coordinates work, the position that captures value is the one above the algorithm - configuring, designing, owning. The role being commoditized is the one below. The binary frames the worker as the relevant actor; the bundle frame asks where the worker sits in the algorithmic coordination structure.

The binary's parents

Where each school sits on the binary.

The binary isn't a popular misreading; it inherits from the literature itself. The taxonomy below shows where every school of thought sits, organized into four stances - and one exit. Read it top-to-bottom: pole, pole, outside, partial break, the way out.

Automation pole

Schools that read AI as substitution - which tasks get displaced, which protected.

  • Task Model of Automation
    Canonical

    The task model's central question is which tasks get automated, which displaced, which newly created. The binary is not a feature of the framework; it is the framework.

  • Routinization (ALM)
    Leans in

    Polanyi's paradox (we can do more than we can say; tacit skill resists codification) decides which work survives automation. The framework accepts the binary as the substrate and argues over which work is on which side.

  • Job Polarization
    Leans in

    Middle-skill routine work gets automated; ends of the wage distribution are protected. The frame is automation-shaped at the role level.

  • Labour Process
    Engages politically

    Braverman frames automation as deskilling; Zuboff frames the firm's choice as automate vs informate. The literature accepts the binary as the choice space and argues over who controls the cut.

Augmentation pole

Schools that read AI as complement - human + AI working together, each contributing strengths.

  • Augmentation
    Canonical

    Equilibrium is human and AI working together, each contributing strengths. The augmentation pole is not a feature of the framework; it is the framework.

  • Social-Skill Complementarity
    Leans in

    Social and conversational skills become more valuable because they complement automation. Complementarity is an augmentation story for a particular skill class.

  • AI Productivity
    Leans in

    Worker-level productivity lift is the unit of measurement. The research design is augmentation by construction; the binary's augmentation pole is the studies' implicit frame.

Outside the binary

Schools whose native question doesn't engage the binary. They get dragged in when extended to AI.

  • Design Rules
    Dragged in

    Modularity is about product architecture. Native to the framework, the binary doesn't appear; it gets dragged in when modular logic is extended to AI components and interfaces.

  • Team Topologies
    Dragged in

    Conway's law is about org structure mirroring product structure. Binary-neutral in its native form; gets dragged in when team boundaries are framed as automation-or-augmentation choices.

  • Industry Architecture
    Dragged in

    Industry architecture theory operates at the firm and industry level - vertical disintegration, value-chain reorganization, architectural bottlenecks. The automation-vs-augmentation question is worker-level; the framework doesn't natively engage it. It gets dragged in when discussions extend AI's architectural redraw down to the worker.

Partially breaks the binary

Schools that name a category the binary cannot contain - but don't fully escape it.

  • Ghost Work
    Partial break

    Names a hidden third category - the annotators and moderators behind 'automation.' Doesn't fully escape the binary; shows it can't be pure. The binary survives but becomes a story about which labour is visible and which is hidden.

The exit

Where the bundle frame takes you out of the taxonomy entirely.

Where to go instead

The Reshuffle thesis

Bundles as the unit, constraints as the binder, reconfiguration as the mechanism, above-vs-below-the-algorithm as the capture diagnostic. The four pillars above are the entire exit.

Re-read the bundle frame
Where the binary lands you

Fallacies the binary produces.

Bad inferences the binary lets pundits make. Each row: the claim, why it is wrong under the bundle frame, and which schools feed the framing that produces it.

The claim What's wrong Schools that feed it
"AI will automate 30 percent of jobs."

Treats roles as the unit. AI substitutes pieces of bundles; the rebundling redistributes work across the labour market in ways the role-count framing cannot see. The 30 percent number is a confidence-level statement about the binary's frame, not about jobs.

"AI will augment knowledge workers, displace routine workers."

Treats knowledge work as a stable category. Foundation models substitute tacit pattern recognition - the core of knowledge work - across functions. The augmentation story holds for the value-capturing rebundled role, not for the original knowledge-work bundle.

"AI is just a tool; it makes workers better at their jobs."

Treats AI as a workforce productivity input. Capability sits outside the firm. The 'tool' is owned and configured upstream; surplus migrates to whoever sets the tool's policy. The worker's productivity rises and their share of the gain falls.

"Humans and AI working together outperform either alone."

Treats the centaur arrangement (human leads, AI assists) as the destination. It is a transition state. Asymmetric capability gain and agentic execution move the human out of the routine decision loop; centaur is the inflection point, not the asymptote.

"We need to regulate which jobs AI is allowed to automate."

Treats the firm and the role as the units of regulatory action. Deployment authority has decentralized below the firm; capability sits with upstream providers; unbundled fragments flow to algorithmic platforms outside the firm. Regulation pointed at 'which jobs get automated' binds where the unit of choice already isn't.