The Research Problem
Technology deployments in organizations frequently produce outcomes below expectations. Existing theories offer partial explanations, but none adequately addresses the structural conditions that may predispose organizations to suboptimal technology outcomes.
Informational Fragmentation
When operational data is scattered across disconnected tools and manual processes, it may create blind spots that persist — or intensify — after technology deployment.
Process Ambiguity
When roles, responsibilities, and workflows lack clear definition, technology can formalize confusion rather than resolve it, potentially generating new coordination overhead.
The Theoretical Gap
TOC addresses sequential bottlenecks; NAT diagnoses tight coupling; TAM/UTAUT model individual acceptance. No existing framework examines how structural preconditions shape technology outcomes at the organizational level.
Constraint Coupling Theory
CCT is a mid-range explanatory framework that integrates three theoretical traditions — the Theory of Constraints (Goldratt 1984), Sociotechnical Systems theory (Trist 1951), and Normal Accident Theory (Perrow 1984). It proposes that two primary structural conditions — informational fragmentation (F) and process ambiguity (P) — can give rise to emergent mechanisms that shape technology deployment outcomes across organizational scales, from SMEs to large enterprises.
Structural Conditions
Informational Fragmentation (F)
The degree to which operational data is dispersed across disconnected tools, manual records, and informal channels. High F can reduce organizational visibility and may complicate technology deployment by providing incomplete or inconsistent inputs to new systems.
Process Ambiguity (P)
The extent to which roles, responsibilities, and workflows lack explicit definition. High P can mean that technology formalizes existing confusion rather than resolving it, potentially generating new coordination overhead and resistance.
Emergent Mechanisms
CCT proposes that when F and P are elevated, six mechanisms may emerge or intensify:
Operational Opacity (Ω)
The inability to observe operational status in real time. When information is fragmented, decision-makers may lack the visibility needed to act effectively, potentially leading to delayed or misaligned responses.
Knowledge Centrality (K)
The concentration of critical operational knowledge in one or few individuals. High K can create single points of failure and may constrain the organization's capacity to absorb new technology.
Decision Centrality (D)
The concentration of decision-making authority. When combined with high K, elevated D can create bottlenecks that slow organizational throughput regardless of technology investment.
Reconciliation Effort (R)
The manual work required to align inconsistent data across systems. High R can consume coordination capacity that might otherwise be directed toward productive activities.
Workarounds & Shadow Systems (W)
Informal tools and processes that emerge to compensate for system inadequacies. While locally rational, W can further fragment information flows and may undermine the intended benefits of formal technology deployments.
Operational Friction (Φ)
The cumulative drag on throughput resulting from the interaction of the above mechanisms. Φ represents the aggregate organizational cost of unresolved structural conditions.
Intermediate Business Outputs
The framework identifies four business-relevant outputs through which these mechanisms may manifest:
Cycle Time
The elapsed time from order to delivery. Elevated mechanisms can extend CT through coordination delays and information gaps.
Revenue Delay
The lag between value creation and revenue recognition. Process ambiguity and reconciliation effort may contribute to billing and invoicing delays.
Hidden Coordination Hours
Untracked time spent on inter-system reconciliation, informal coordination, and workaround maintenance.
Processed Capacity
The volume of work the organization can effectively process. Structural friction may reduce effective capacity below nominal capacity.
"Technology deployment on structurally unprepared organizations may formalize existing dysfunction rather than resolve it."
Empirical Evidence
CCT draws on multi-case study research following Eisenhardt (1989) and Yin (2018) methodologies. The cases below illustrate how the framework's constructs may manifest in different organizational contexts. These are exploratory observations, not confirmatory tests.
PLC Conseil — Accounting Firm
High informational fragmentation (F): 5 disconnected tools (accounting, CRM, docs, email, spreadsheets). Elevated knowledge centrality (K) and decision centrality (D) concentrated in the managing director. An AI chatbot was deployed without first addressing F or reducing K/D. Observed outcomes suggest elevated reconciliation effort (R) and limited capacity gains.
Limited improvement observedJLM Menuiserie — Construction (€5M)
High F (11 disconnected tools) and high P (ambiguous handoffs across quoting, planning, procurement, and field coordination). Knowledge centrality concentrated in one project coordinator managing 15-25 concurrent sites. A structured intervention addressed F and P sequentially over 6 months before deploying the Saxium platform. Early indicators suggest reduced operational friction (Φ) and improved cycle time (CT).
Positive early indicatorsCerfrance — Agricultural Cooperative
Distributed process ambiguity (P) across a network of field advisors. A custom tool was deployed without prior assessment of F or P levels. Observed outcomes included elevated workarounds (W) and resistance patterns consistent with unaddressed structural conditions. This case requires further investigation to distinguish CCT-specific effects from general change management factors.
Under further analysisResearch Propositions
CCT advances a set of testable propositions. These are formulated as directional expectations rather than precise quantitative predictions, consistent with the framework's current explanatory (rather than fully predictive) status:
Research Agenda
About the Researcher
Working Paper
The working paper for Constraint Coupling Theory is under revision, targeting ICIS 2026 (International Conference on Information Systems, Lisbon) in the "Organizational Strategy, Governance, and Transformation" track.
The framework draws on 13 years of fieldwork across 80+ organizational audits, spanning SMEs, ETIs, and cooperatives.
How to Cite
Fritsch, T. (2026). Constraint Coupling Theory: How Informational Fragmentation and Process Ambiguity Shape Technology Deployment Outcomes in Organizations. Working Paper. Available at: constraintcoupling.com
Key References
- Goldratt, E.M. & Cox, J. (1984). The Goal: A Process of Ongoing Improvement. North River Press.
- Perrow, C. (1984). Normal Accidents: Living with High-Risk Technologies. Basic Books.
- Trist, E.L. & Bamforth, K.W. (1951). Some Social and Psychological Consequences of the Longwall Method of Coal-Getting. Human Relations, 4(1), 3–38.
- 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.