Loading field map
In the early 1950s, researchers at the Tavistock Institute in London walked into a coal mine and emerged with an idea that would unsettle the dominant way of thinking about technology in organizations. They had observed that introducing new machinery without adjusting the social organization of work led to resistance, low productivity, and even sabotage. The lesson was simple but radical: a technical system cannot be understood or designed in isolation from the human and organizational context in which it operates. That insight gave rise to Sociotechnical Systems Theory, a framework that has shaped information systems (IS) research for over seven decades—and that has coexisted, competed, and sometimes merged with two other major frameworks: the Technical-Rational Paradigm and the Interpretive Paradigm.
From the 1950s through the end of the twentieth century, the Technical-Rational Paradigm dominated both the practice and the academic study of information systems. Rooted in engineering, operations research, and management science, this framework treated information systems as technical artifacts designed to process data efficiently and support rational decision-making. The core assumption was that organizational goals were clear and stable, that information could be treated as a neutral resource, and that better technology would automatically produce better outcomes.
This paradigm produced many successes: early accounting systems, inventory control, and decision support tools that automated routine tasks and improved speed. Yet by the 1960s and 1970s, a growing number of failures—expensive systems that were never used, or that actually worsened performance—revealed a persistent blind spot. The Technical-Rational Paradigm had no vocabulary for explaining why a technically sound system might fail because of office politics, user resistance, or mismatched work practices. It assumed that people would adapt to technology, not the other way around.
Despite these limitations, the Technical-Rational Paradigm did not disappear. It narrowed over time, retreating into areas where its assumptions held reasonably well—such as transaction processing and well-structured decision tasks—while ceding ground in more complex organizational settings. Its legacy persists today in project management methodologies, software engineering standards, and the widespread belief that technology can be "rolled out" with minimal attention to social context.
Sociotechnical Systems Theory emerged in the same decade as the Technical-Rational Paradigm, but from a very different starting point. The Tavistock researchers—Eric Trist, Fred Emery, and others—studied coal mining, textile mills, and other industrial settings where technological change had disrupted existing social structures. They developed the concept of joint optimization: the idea that a work system performs best when its technical and social subsystems are designed together, each supporting the other.
This framework shifted the unit of analysis from the individual technical artifact to the whole work system—the combination of people, tasks, technology, and organizational structures. In IS, this meant that an information system was not just software and hardware, but also the users, their skills, the workflows, and the power relationships that shaped how the system was actually used. Design became a participatory process, involving users not as passive recipients but as co-designers.
For decades, Sociotechnical Systems Theory coexisted with the Technical-Rational Paradigm rather than replacing it. In practice, many organizations continued to treat technology as a given and people as obstacles to be managed. But in academic IS research, sociotechnical thinking gained traction, especially in Europe and in the participatory design movement. It provided a language for talking about the social dimensions of systems that the Technical-Rational Paradigm could not address.
By the 1990s and 2000s, Sociotechnical Systems Theory had broadened to encompass digital platforms, enterprise systems, and large-scale infrastructure. The concept of sociotechnical systems was extended to include not just single organizations but entire industries and societies, as seen in work on infrastructure and modernity. Today, it remains the most explicitly design-oriented framework in the subfield, guiding methods such as work system analysis and user-centered design.
The Interpretive Paradigm entered IS research in the 1980s, drawing on sociology, anthropology, and philosophy. Where the Technical-Rational Paradigm saw systems as objective tools and Sociotechnical Systems Theory saw them as joint designs, the Interpretive Paradigm saw them as sites of meaning-making. Researchers in this tradition asked not just how systems should be designed, but how people made sense of them, how power and culture shaped their use, and how the very categories of "technology" and "organization" were socially constructed.
This framework did not reject Sociotechnical Systems Theory outright; in many ways it extended the social dimension that sociotechnical thinking had opened up. But it also challenged sociotechnical assumptions. Where Sociotechnical Systems Theory was normative—it prescribed how systems ought to be designed—the Interpretive Paradigm was analytical and often critical. It questioned whether joint optimization was always possible or desirable, especially when power imbalances or conflicting interests made genuine participation impossible. It also introduced new methods: ethnography, case studies, discourse analysis, and other qualitative approaches that could capture the richness of organizational life.
The Interpretive Paradigm and Sociotechnical Systems Theory have coexisted in a productive tension. Sociotechnical researchers borrow interpretive methods to understand user needs; interpretive researchers sometimes adopt sociotechnical concepts to frame their analyses. But their goals differ: one aims to improve design, the other to deepen understanding. This difference has kept them as distinct traditions within the subfield.
Today, all three frameworks remain active, but they occupy different roles. The Technical-Rational Paradigm has largely retreated from academic IS research, though its assumptions still shape practice in software engineering and project management. Sociotechnical Systems Theory leads in design-oriented research, especially in areas like participatory design, work system design, and digital transformation. The Interpretive Paradigm dominates qualitative IS research, providing the theoretical and methodological tools for studying technology in use.
What do these frameworks agree on? All three recognize that information systems are not purely technical; they involve people, organizations, and contexts. Even the Technical-Rational Paradigm, in its later years, acknowledged the need for user training and change management. The deeper agreement is that the subfield's central question—how to understand and improve the relationship between technology and organization—cannot be answered by technology alone.
Where they disagree is on the nature of that relationship and the proper role of the researcher. The Technical-Rational Paradigm assumes that goals are given and that the researcher's job is to engineer efficient solutions. Sociotechnical Systems Theory assumes that goals can be negotiated through participation and that the researcher is a facilitator of joint design. The Interpretive Paradigm assumes that goals are emergent and contested, and that the researcher's job is to interpret and critique, not to prescribe. These differences are not merely academic; they shape which methods are used, what counts as evidence, and how research findings are translated into practice.
The subfield of sociotechnical systems in information systems is thus not a single theory but a living conversation among frameworks that have coexisted for decades. The Technical-Rational Paradigm provided the initial momentum; Sociotechnical Systems Theory offered a corrective that remains influential; and the Interpretive Paradigm deepened the social analysis in ways that continue to challenge and enrich both. For a student entering this field, the key is not to choose one framework over the others, but to understand what each makes visible and what it leaves out.