Organizational Change

Organizational change is the practice and study of how organizations move from one way of working to another—and why so many of those moves fail.

17 frameworks, from 1911 to today · Management · Business, Management & Finance

still a working view ended · each leads to its entry below

Overview

Organizational change is the practice and study of how organizations move from one way of working to another—and why so many of those moves fail. It matters because organizations are not machines that can simply be rebuilt to specification. They are made of people, habits, power, and history, and any attempt to alter how work is done runs into all three. The field's history is a long argument about where the resistance comes from and what, if anything, a change agent can do about it: redesign the work, win the people, learn the system, or accept that change is continuous and only partly controllable.

Scientific Management and the Engineer's Answer

The first systematic approach to organizational change came from the factory floor. Frederick Winslow Taylor's The Principles of Scientific Management (1911) proposed that work should be studied, timed, and redesigned by experts rather than left to custom and craft. Taylor's method—time-and-motion study, standardized tasks, differential piece rates—treated change as an engineering problem: find the "one best way," then install it. His famous example was the pig-iron handlers at Bethlehem Steel, where he claimed that redesigning the task and selecting the right worker could roughly quadruple daily output per man.

The appeal was enormous. In the United States and Europe, factories, offices, and even households were reorganized along Taylorist lines, and the idea that management was a science to be applied spread through engineering schools and consultancies. But the approach had a blind spot that would define the next half-century: it assumed workers would comply with a technically superior design. They often did not.

Human Relations and the Discovery of the Informal Organization

The Hawthorne studies at Western Electric's Chicago plant, conducted from the late 1920s into the 1930s under Elton Mayo and colleagues, are the field's founding counterexample. Researchers testing how lighting affected productivity found that output rose whether lights went up or down—the attention itself seemed to matter12. Whatever the methodological weaknesses later attributed to the studies, their message reshaped the field: workers have social needs, informal groups set their own norms, and change that ignores these will meet resistance.

The human relations school that followed argued that change succeeds when people are consulted, when supervisors attend to feelings as well as tasks, and when the group, not just the individual, is the unit of change. This was a genuine shift in what practitioners did: the change agent now had to be part engineer and part counselor.

Group Dynamics, Action Research, and Organization Development

Kurt Lewin, a German-American psychologist who fled to the United States in the 1930s, gave the field its most durable vocabulary. His "unfreeze–change–refreeze" image described change as a temporary disturbance of a stable social field, and his concept of the "force field" framed any situation as a balance of driving and restraining forces—so that change means weakening restraints as much as pushing harder. Lewin also pioneered action research: a cycle in which researchers and members of an organization jointly diagnose a problem, try an intervention, study the results, and repeat34. The approach made the people being changed into collaborators in changing themselves.

Out of this came organization development (OD), a professional practice that emerged in the 1950s and 1960s, especially in the United States. OD practitioners used survey feedback, team building, and sensitivity training to improve how groups worked together, treating the organization as a human system to be helped rather than a machine to be rebuilt. The National Training Laboratories, founded in the late 1940s, became a hub for the group-dynamics strand. OD's optimism—that open communication and trust could dissolve resistance—was its strength and, critics later charged, its naivety about power.

Planned Change and Its Limits

The 1960s and 1970s produced the first formal models of planned change. Warren Bennis, Kenneth Benne, and Robert Chin's The Planning of Change (1961) collected the field's approaches; later, the "planned-change model" associated with Lippitt, Watson, and Westley described change as a sequence of phases from diagnosis through stabilization. The implicit assumption was that a skilled agent could steer an organization through a defined transition.

Two challenges undermined that confidence. First, research on organizations as open systems—depending on their environments for resources and legitimacy—suggested that change was often forced from outside rather than chosen from within. Contingency thinking, prominent in the 1960s, held that there is no one best way to organize: structure and change strategy must fit the environment, technology, and size of the firm. Joan Woodward's studies of British manufacturing firms in the 1950s and 1960s, and the work of Paul Lawrence and Jay Lorsch on differentiation and integration, showed that what worked in one setting failed in another. The change agent's job became diagnosis before prescription.

Second, sociotechnical systems theory, developed at London's Tavistock Institute from the 1950s by researchers including Eric Trist and Fred Emery, argued that any work system has a social and a technical side that must be jointly optimized. Trist's studies of British coal mining showed that introducing new technology without regard for the miners' self-organizing work groups destroyed productivity and morale; redesigning both together restored them. The lesson—change the technology and the social organization together, or fail—became a cornerstone of later work on work redesign.

Incrementalism, Culture, and the Process Turn

By the 1970s, a counter-current to planned change had formed. Charles Lindblom's "muddling through" (1959) and later Henry Mintzberg's work on strategy suggested that managers rarely execute grand designs; they make small, successive adjustments. James Brian Quinn's Strategies for Change: Logical Incrementalism (1980) gave this a name: strategy emerges through a series of deliberate but partial moves, each tested and revised, rather than a single leap. For change practitioners, this meant that big-bang transformation was often less realistic than a sequence of probes.

The 1980s brought culture to the center. Studies such as Terrence Deal and Allan Kennedy's Corporate Cultures (1982) and Edgar Schein's work on organizational culture argued that the deepest layer of an organization—its shared assumptions about how the world works—resists change more stubbornly than structure or strategy. Change programs that ignored culture, the argument went, would be absorbed and neutralized. Schein's later writing on how leaders embed culture made the point practical: what leaders pay attention to, reward, and tolerate teaches the organization what really matters.

Reengineering and the Promise of the Clean Slate

The 1990s produced the most aggressive change prescription since Taylor. Michael Hammer's 1990 Harvard Business Review article "Reengineering Work: Don't Automate, Obliterate" and the 1993 book Reengineering the Corporation by Hammer and James Champy urged firms to abandon existing processes and redesign them from scratch around outcomes rather than tasks. The emblematic case was the insurance company that replaced sequential claims handling with a single "case worker" who processed a claim end to end, cutting turnaround from days to hours. Reengineering spread rapidly through consultancies, and its failures were equally dramatic: estimates of the failure rate of reengineering programs ran high, and critics blamed its disregard for the people whose jobs were being obliterated.

Learning, Sensemaking, and the Political View

Alongside reengineering, a more reflective strand grew. Chris Argyris and Donald Schön's work on organizational learning (developed from the 1970s, culminating in Organizational Learning, 1978, and Organizational Learning II, 1996) distinguished "single-loop" learning—fixing errors within existing assumptions—from "double-loop" learning, which questions the assumptions themselves. Argyris's studies of skilled professionals showed a "defensive routine": people avoid exposing their reasoning, which blocks the very learning change requires. Peter Senge's The Fifth Discipline (1990) popularized systems thinking, personal mastery, and shared vision as disciplines for a "learning organization."

A parallel strand emphasized power and interpretation. Research on organizational politics showed that change is not a neutral technical exercise but a contest in which coalitions compete, resources are bargained over, and some groups win while others lose. Karl Weick's work on sensemaking—how people construct plausible accounts of ambiguous events—explained why the same change program can mean different things to different groups, and why leaders' announcements are only the beginning of the story5. The political and sensemaking perspectives together made "resistance" look less like irrationality and more like a rational response to threatened interests and unsettled meaning.

Prescriptive Models and the Practice Turn

The 1990s and 2000s also produced widely used practitioner frameworks. John Kotter's eight-step model, set out in Leading Change (1996), packaged change as a sequence: create urgency, build a guiding coalition, form a vision, communicate it, empower action, generate short-term wins, consolidate gains, and anchor changes in culture. Its popularity in management education and consulting made it the default checklist for change leaders, even as researchers noted that its linear stages fit poorly with the messy reality of most organizations.

That gap fed the "processual" school. Andrew Pettigrew's longitudinal studies of firms such as ICI in the 1980s argued that change must be studied as a process unfolding over time, shaped by context, and that the same intervention can produce different outcomes in different settings. Later practice-based research went further, examining change as something people accomplish in everyday activity—through routines, tools, and conversations—rather than something done to them by a program. This view, associated with scholars studying strategy-as-practice and routine dynamics, treats continuity and change as intertwined: routines are both the source of stability and the seedbed of variation.

Agile, Digital, and the Continuous-Change Present

The most recent era has been shaped by two forces. Agile methods, developed in software development in the 1990s and codified in the 2001 Agile Manifesto, replaced big up-front design with short iterative cycles, cross-functional teams, and continuous customer feedback. Agile spread from software into general management as "agile transformation," and its logic—small batches, rapid feedback, empowered teams—echoes both sociotechnical thinking and logical incrementalism.

Digital transformation, the effort to reorganize around digital technologies and data, became the dominant change agenda of the 2010s and 2020s. It differs from earlier programs in scope: it touches products, processes, customer relationships, and business models at once, and it rarely has a clear endpoint. Practitioners increasingly speak of continuous change, in which the organization builds the capacity to change rather than executing discrete change projects.

Today the field holds several approaches in tension. Planned-change models and Kotter's steps remain standard in practice and teaching; OD's collaborative values persist in facilitation and coaching; process and practice perspectives dominate much academic research; and agile and digital agendas push toward continuous adaptation. The open questions are old ones in new clothes: how to change fast without breaking what works, how to distribute the authority to change without losing coherence, and whether resistance is an obstacle to overcome or a signal worth reading.

References

  1. Organizational behavior (History), Wikipedia
  2. Hawthorne effect (History), Wikipedia
  3. Action research, Wikipedia
  4. Organization development (History), Wikipedia
  5. Sensemaking, Wikipedia

The frameworks of Organizational Change

Each framework is a way of working the field has used: when it held, and the question it answers.

  1. 1911-1940

    Scientific Management

    How should work be designed for maximum efficiency?

    Fly to its tower in Nousfarer

  2. 1930-1960

    Human relations movement

    What social needs shape workers' behavior?

    Fly to its tower in Nousfarer

  3. 1945-1975

    Group Dynamics and Action Research

    How can groups change themselves through research?

    Fly to its tower in Nousfarer

  4. 1950-Present

    Organization Development

    How can consultants help organizations improve?

    Fly to its tower in Nousfarer

  5. 1950-1990

    Sociotechnical system

    How should social and technical work systems be jointly designed?

    Fly to its tower in Nousfarer

  6. 1959-1990

    Logical Incrementalism

    How do strategies actually emerge through small moves?

    Fly to its tower in Nousfarer

  7. 1960-1990

    Contingency Theory

    Which structure fits a given environment and technology?

    Fly to its tower in Nousfarer

  8. 1961-1990

    Planned change

    How can a change agent steer a defined transition?

    Fly to its tower in Nousfarer

  9. 1970-Present

    Organizational Politics and Sensemaking

    How do coalitions and interpretations shape organizational change?

    Fly to its tower in Nousfarer

  10. 1978-Present

    Organizational Learning

    How do organizations learn from their errors?

    Fly to its tower in Nousfarer

  11. 1979-Present

    Sensemaking

    How do people make sense of ambiguous events?

    Fly to its tower in Nousfarer

  12. 1982-Present

    Organizational culture

    What shared assumptions shape how an organization works?

    Fly to its tower in Nousfarer

  13. 1985-Present

    Processual and Practice-Based Change

    How does change unfold continuously in practice?

    Fly to its tower in Nousfarer

  14. 1990-2000

    Business process re-engineering

    How should processes be redesigned from scratch?

    Fly to its tower in Nousfarer

  15. 1996-Present

    Kotter's Eight-Step Model

    What steps lead a large change to succeed?

    Fly to its tower in Nousfarer

  16. 2001-Present

    Agile Transformation

    How can teams work iteratively at scale?

    Fly to its tower in Nousfarer

  17. 2010-Present

    Digital Transformation

    How should organizations remake themselves with digital technology?

    Fly to its tower in Nousfarer

How the ideas connect

Each arrow runs from an earlier idea to the later one it shaped. The list below says what passed between them.

Scientific ManagementHuman relations movementGroup Dynamics and Action ResearchOrganization DevelopmentSociotechnical systemLogical IncrementalismContingency TheoryPlanned changeOrganizational Politics and Sensemaki…Organizational LearningSensemakingOrganizational cultureProcessual and Practice-Based ChangeBusiness process re-engineeringKotter's Eight-Step ModelAgile TransformationDigital Transformation

Beyond the field

Where Organizational Change's ideas came from in other fields, and what they led to there: the strongest 12 of 44 links.

A city in Nousfarer: a red-carpeted stair climbing terraces to a crowned tower on an acropolis, more towers round it, forest and snowy mountains beyond.
A city in Nousfarer, the game played in the browser.

Organizational Change is a planet in Nousfarer

Its city has a tower for each of these 17 frameworks. Land, walk in, and climb one concept at a time.

Land on Organizational Change

Related fields

Fields its ideas are linked to

More in Management

See where Organizational Change sits on the Map of Human Knowledge