The AI Productivity Paradox

Organizations invest billions in AI, yet productivity often decreases after deployment. This isn't a technology problem — it's a constraint problem that no existing theory adequately explains.

01

TOC Can't See It

Goldratt's Theory of Constraints assumes singular, physical bottlenecks. It wasn't designed for coupled human-IS constraints.

02

TAM/UTAUT Miss It

Technology adoption models explain individual acceptance, not systemic organizational failures caused by pre-existing bottlenecks.

03

The Gap

No theory explains what happens when you deploy technology on a system where human and IS constraints are structurally interdependent.

Constraint Coupling Theory

CCT extends Goldratt's Theory of Constraints to explain why technology deployment on coupled human-IS constraints produces the opposite of the expected effect.

Constraint Coupling Mechanism Two coupled constraints — Human Constraint (Owner-Manager SPOF) and IS Constraint (Fragmented Tools) — connected by structural interdependence arrows. An AI Deployment trigger amplifies the coupling, resulting in three failure modes: Amplification, Rejection, and Workaround. Human Constraint Owner-Manager SPOF IS Constraint Fragmented Tools Structural Interdependence + AI Deployment COUPLED SYSTEM Amplification Rejection Workaround

Constraint Coupling

When a human constraint (the owner-manager as bottleneck) and an IS constraint (fragmented, disconnected tools) are structurally interdependent — resolving one requires the other's participation, creating a circular dependency.

The Constraint Amplification Effect

Deploying technology on coupled constraints degrades rather than improves performance. The technology adds cognitive load to an already overloaded human node while introducing new failure modes into a fragmented IS. This is the mechanism behind the AI Productivity Paradox.

Three Failure Modes

Amplification — increased data volume and coordination overhead. Rejection — users resist technology that disrupts their workflow. Workaround — shadow systems that fragment information further.

"You cannot automate chaos. You must first align the flows, then assist the people, then — and only then — automate."

The A→B→C Invariable Sequence

CCT proposes that successful technology deployment in coupled constraint systems requires a strict three-phase sequence:

A

Align

Stabilize data flows. Eliminate double entry. Connect existing tools before adding new ones.

B

Assist

Deploy technology that reduces the human bottleneck's cognitive load. Build team readiness.

C

Automate

Only now can AI and automation succeed — clean data and prepared teams are in place.

Skipping phases produces systematic failures: Skip A → technical failures. Skip B → change resistance. Skip A and B → both.

Empirical Evidence

CCT is grounded in multi-case study research across three French SMEs, following Eisenhardt (1989) and Yin (2018) methodologies.

Case A

PLC Conseil — Accounting Firm

Managing director = strategic + operational bottleneck. 5+ disconnected tools. AI assistant deployed at C level without A or B.

Marginal gains (H2 confirmed)
Case B

JLM Menuiserie — Construction (€5M)

Project coordinator = SPOF for 15-25 concurrent projects. 11+ disconnected tools. A→B→C sequence followed deliberately.

Positive indicators (H3 testing)
Case C

Cerfrance — Agricultural Cooperative

Field advisors = individual bottlenecks. Tool deployed directly at C without A or B phases.

Bugs + resistance (H4, H5 confirmed)

Falsifiable Hypotheses

CCT proposes five testable predictions, distinguishing it from frameworks that describe but cannot predict:

H1
Coupled constraints degrade system throughput more than singular constraints of equivalent severity.
H2
Technology deployment on coupled constraints without prior decoupling produces a measurable amplification effect (≥5% performance decrease).
H3
The A→B→C sequence produces superior outcomes compared to any alternative ordering.
H4
Skipping Phase A (direct automation) produces technical failures in ≥70% of cases.
H5
Skipping Phase B (A→C without assistance) produces adoption rates below 40%.

About the Researcher

TF

Thibault Fritsch is the CEO of Robinswood, a consultancy specializing in digital transformation for SMEs.

With 13 years of fieldwork and over 80 operational audits across construction, accounting, agricultural consulting, and professional services, his research bridges the gap between management theory and the daily reality of small business operations.

CCT emerged from a recurring observation: the same structural pattern — a human bottleneck coupled with fragmented information systems — appeared in nearly every SME that struggled with technology adoption.

He holds a degree in information systems and has been a practitioner-researcher since founding his consultancy in 2013.

Working Paper

The foundational paper for Constraint Coupling Theory has been submitted to ICIS 2026 (International Conference on Information Systems, Lisbon) in the "Organizational Strategy, Governance, and Transformation" track.

Read the Working Paper

A proposal has also been submitted to MIT Sloan Management Review. The theory builds on 13 years of fieldwork across 80+ SME audits.

How to Cite

Fritsch, T. (2026). Constraint Coupling Theory: Why Technology Deployment on Coupled Human-IS Constraints Produces the Opposite of the Expected Effect. Working Paper. Available at: constraintcoupling.com

Key References

  • Goldratt, E.M. & Cox, J. (1984). The Goal: A Process of Ongoing Improvement. North River Press.
  • Brynjolfsson, E. (1993). The Productivity Paradox of Information Technology. Communications of the ACM, 36(12), 66–77.
  • Eisenhardt, K.M. (1989). Building theories from case study research. Academy of Management Review, 14(4), 532–550.
  • Yin, R.K. (2018). Case Study Research and Applications: Design and Methods (6th ed.). Sage.
  • Venkatesh, V. et al. (2003). User acceptance of information technology: Toward a unified view. MIS Quarterly, 27(3), 425–478.
  • DeLone, W.H. & McLean, E.R. (2003). The DeLone and McLean Model of IS Success. JMIS, 19(4), 9–30.