Human Computer Interaction

Human-computer interaction (HCI) is the study and practice of how people and computing systems meet: what people need to do with a machine, what the machine offers them, and how the design of one shapes the possibilities of the other.

21 frameworks, from 1945 to today · Human Computer Interaction · Computer Science

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

Overview

Human-computer interaction (HCI) is the study and practice of how people and computing systems meet: what people need to do with a machine, what the machine offers them, and how the design of one shapes the possibilities of the other1. It is a field built out of several disciplines—psychology, ergonomics, computer science, design, sociology, anthropology—and its history is largely a history of arguments about where the human being belongs in the design of technology1. At stake throughout has been a deceptively simple question: should the machine adapt to people, or should people be trained to adapt to the machine? The answer has shifted repeatedly, and each shift produced new methods, new kinds of systems, and new ideas about what counts as good design.

Human Factors and the Wartime Operator

The earliest strand came from human factors and ergonomics, the study of fitting machines to human bodies and minds. Its modern form took shape during the Second World War, when psychologists and engineers found that trained operators were crashing aircraft and misreading instruments not from carelessness but from badly designed displays and controls. The response was a science of the operator: measuring reaction times, mapping the limits of attention, and designing cockpits, radar consoles, and control rooms around those measurements. After the war this work moved into industry and into early computing. In the 1950s and 1960s, military command-and-control systems and air-traffic control put people in front of screens and consoles, and human-factors specialists studied how operators scanned displays, made decisions under time pressure, and recovered from error. The field's core conviction was that performance could be measured and predicted, and that design should follow the measurements.

The Command Line and the First Interface Debates

Early computers were operated through batch processing: a programmer submitted a deck of punched cards and waited for output2. The first challenge to this model came from interactive computing. In the early 1960s, J.C.R. Licklider wrote his influential memos on "man-computer symbiosis," arguing that computers should become partners in real-time intellectual work rather than batch processors. Ivan Sutherland's Sketchpad (1963) demonstrated that a person could draw directly on a screen with a light pen and manipulate a graphical model—an early proof that computers could respond to human gesture. Douglas Engelbart's Augmenting Human Intellect research at Stanford Research Institute produced, in a famous 1968 demonstration, the mouse, hypertext links, and a collaborative editing system, all aimed at helping people think and work together.

These systems raised a question the human-factors tradition could not answer: what should interaction itself feel like? The dominant model of the 1970s was the command line, in which users typed instructions in a formal syntax. It was powerful and precise, but it demanded that people learn the machine's language and remember its rules. The problem was not physical ergonomics but cognitive burden.

Direct Manipulation and the Graphical Interface

The turning point came with direct manipulation, a term coined by Ben Shneiderman in the early 1980s3. His claim was that interfaces should present objects of interest visibly and let people act on them with rapid, reversible, incremental operations whose effects are immediately visible3. Instead of typing a command to move a file, you drag its icon. The idea was embodied most famously in Xerox PARC's Alto (early 1970s) and Star (1981) systems, which used windows, icons, menus, and a pointing device. Apple's Lisa (1983) and Macintosh (1984) brought the graphical user interface to a mass market, and Microsoft Windows followed.

Direct manipulation changed what HCI was about. If users could see and point rather than recall and type, then design became a matter of arranging visible objects and feedback—a design problem, not only a measurement problem. This opened the door to interaction design as a distinct practice: deciding what appears on screen, what happens after a click, and how a system communicates its state over time.

Cognitive Modeling and the Science of the User

Alongside the graphical interface grew an attempt to make HCI a predictive science. The most influential effort was GOMS—Goals, Operators, Methods, and Selection rules—developed by Stuart Card, Thomas Moran, and Allen Newell in The Psychology of Human-Computer Interaction (1983)14. GOMS modeled a skilled user's task as a hierarchy of goals broken into elementary operators (keystrokes, mouse movements, mental steps), each with an estimated time. From such a model one could predict, before building anything, how long a task would take under different interface designs. The approach, together with Fitts's law (a 1954 finding that the time to point at a target depends on its distance and size), gave designers quantitative tools.

The cognitive approach rested on a picture of the user as an information processor: perception, memory, and decision-making could be described as mechanisms and simulated. It was powerful for well-defined, expert tasks, and it shaped usability engineering, heuristic evaluation, and the laboratory experiment as the field's standard method. Its limitation was that real work rarely looks like a clean hierarchy of goals. People improvise, get interrupted, and act within social settings that a model of an isolated mind cannot capture.

The Turn to Work, Collaboration, and Context

In the 1980s and 1990s, a sociological challenge reframed the field. Lucy Suchman's Plans and Situated Actions (1987) argued, from studies of people using a photocopier's help system, that human action is not the execution of pre-formed plans but is situated—improvised in response to the concrete circumstances of the moment. If that is so, then interfaces that assume users follow a fixed procedure will fail when real situations diverge. The lesson was that design must support people's own ways of organizing work, discovered through observation rather than assumed from a model.

This insight fed two related movements. Computer-supported cooperative work (CSCW), which took shape at a conference first held in 1986, studied how groups use technology together: shared calendars, messaging, group editors, and later video conferencing. Its practitioners found that systems designed for individual users often broke down when placed in organizations, because coordination, awareness of others' activity, and social norms mattered as much as the interface. Contextual design, developed by Hugh Beyer and Karen Holtzblatt in the 1990s, turned this into a method: designers go into workplaces, observe and interview people doing real work, and build models of the work before designing anything.

A parallel strand was participatory design, which emerged in Scandinavia in the 1970s and 1980s out of trade-union and workplace-democracy projects. Its premise was that the people who will use a system should help design it, not merely be consulted. Projects such as the Utopia effort, involving newspaper workers and researchers, developed techniques for bringing workers into the design process. The approach spread internationally and became a standard commitment in many design traditions: users are partners, not test subjects.

User-Centered Design and the Design Disciplines

The 1980s and 1990s also saw HCI absorb ideas from design practice. Donald Norman's The Design of Everyday Things (1988) popularized the notion of affordances—the properties of an object that suggest how it should be used—and argued that good design makes the right action obvious and errors hard to commit. User-centered design became the banner for a process that begins with understanding users' needs and iterates through prototyping and testing5. Design thinking, championed by IDEO and later by Stanford's d.school, generalized this into a staged process of empathize, define, ideate, prototype, and test, and carried it beyond software into business and public services.

The design disciplines also brought a critical sensibility. Value-sensitive design, articulated by Batya Friedman in the 1990s, argued that technical systems inevitably embody human values—privacy, autonomy, trust, fairness—and that designers should identify and deliberate about those values explicitly rather than let them arrive by accident6. Critical and speculative design, associated with Anthony Dunne and Fiona Raby, used designed objects and scenarios to provoke debate about possible futures rather than to solve immediate problems78. Feminist HCI, named in a 2010 paper by Shaowen Bardzell, asked how design could support values such as equity, participation, and advocacy, and drew attention to whose perspectives were missing from the field9. Postcolonial computing, developed by scholars including Lilly Irani, Janet Vertesi, Paul Dourish, and Kavita Philip, examined how HCI's assumptions about users, progress, and technology were shaped by colonial histories and Western contexts, and argued for design that respects local practices.

Ubiquitous Computing and Embodied Interaction

A different trajectory came from Mark Weiser, who at Xerox PARC in the late 1980s and early 1990s described ubiquitous computing: a world in which computers recede into the background of everyday life, embedded in walls, objects, and clothing, so that people interact with them without thinking of them as computers10. Weiser's vision of "calm technology" shifted the design question from the screen to the environment. It anticipated later developments in mobile and wearable computing, sensor networks, and the internet of things.

Paul Dourish's Where the Action Is (2001) gave this shift a theoretical name: embodied interaction. Drawing on phenomenology and on studies of tangible and social computing, Dourish argued that meaning in interaction arises from bodily engagement with the world and with others, not from symbols processed in the head. The claim supported tangible interfaces, gestural and spatial interaction, and a view of the user as a participant in a physical and social situation rather than an information processor.

Data, Experience, and the Present

From the 2000s onward, two forces reshaped practice. The first was data-driven experimentation. As web services scaled, companies such as Google and Amazon ran large numbers of randomized controlled trials—A/B tests—comparing interface variants on live users, measuring clicks and conversions. This brought the logic of the controlled experiment into everyday product design, at a scale and speed the laboratory could not match. The second was the rise of user experience as an organizing idea, extending concern from usability and task efficiency to emotion, aesthetics, and the whole arc of a person's relationship with a product1112.

Accessibility and inclusive design became a central commitment rather than a specialty, driven by disability-rights advocacy, legal requirements such as the Americans with Disabilities Act and later the Web Content Accessibility Guidelines, and the recognition that designing for the margins improves design for everyone. The field's methods now span ethnography, participatory workshops, prototyping, controlled experiments, and large-scale analytics, and its theories range from cognitive modeling to situated action to critical and postcolonial perspectives.

The open questions are the ones its history keeps returning to: how to design for people whose lives and cultures the designer does not share; how to weigh measurable efficiency against values that resist measurement; and how to keep human agency intact as computing dissolves into the environment and increasingly acts on its own.

References

  1. Human–computer interaction (introduction, Definition), Wikipedia
  2. Command-line interface, Wikipedia
  3. Direct manipulation interface, Wikipedia
  4. GOMS, Wikipedia
  5. User-centered design, Wikipedia
  6. Value sensitive design, Wikipedia
  7. Speculative design, Wikipedia
  8. Critical design, Wikipedia
  9. Feminist HCI (introduction, History), Wikipedia
  10. Ubiquitous computing (History), Wikipedia
  11. User experience (History), Wikipedia
  12. User experience design (History), Wikipedia

The frameworks of Human Computer Interaction

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

  1. 1945-1990

    Ergonomics

    How should machines be fitted to human limits?

    Fly to its tower in Nousfarer

  2. 1960-1985

    Man-Computer Symbiosis

    How can computers partner people in real-time thinking?

    Fly to its tower in Nousfarer

  3. 1975-Present

    Participatory Design

    Who should have a say in designing a system?

    About Participatory Design
    Participatory design is a methodological school within human-computer interaction (HCI) that places the people who will use a system at the center of its creation—not as research subjects or testers, but as active partners in the design process. Its distinctive organizing idea is that the knowledge needed to build a successful system is distributed unevenly. Designers and developers understand technology, but users understand their own work, practices, and needs. Neither group can succeed alone. Participatory design therefore creates structured ways for these groups to collaborate, making the design process itself a shared activity rather than a handoff from experts to consumers.
    The problem participatory design addresses is the persistent failure of systems designed without meaningful input from their end users. When designers work from assumptions about how people behave, they often build tools that are technically sound but practically wrong—awkward to use, misaligned with real workflows, or simply unwanted. This problem is not merely one of usability in a narrow sense; it is a problem of power and knowledge. The approach emerged in the 1970s in Scandinavia, rooted in a political commitment to workplace democracy. The earliest projects, such as the Norwegian Iron and Metal Workers Union (NJMF) project, were collaborations between researchers and trade unions. The goal was not just better software but greater influence for workers over the systems that shaped their daily labor. This political ancestry distinguishes participatory design from other HCI approaches that seek user input primarily to improve efficiency or market fit.
    Participatory design differs sharply from its immediate predecessor, human factors engineering, which dominated HCI from the 1940s through the 1980s. Human factors engineering treats users as variables to be measured and accommodated, with designers applying ergonomic principles to fit the machine to the human body and mind. The user is an object of study. Participatory design inverts this relationship: the user becomes a subject with agency, a co-designer whose voice carries authority. It also differs from user-centered design, which emerged later in the 1980s. User-centered design typically involves observing and testing users to inform design decisions made by experts. Participatory design goes further, insisting that users should help make those decisions, not merely inform them. The designer does not abdicate responsibility—as Wendy Mackay and Michel Beaudouin-Lafon emphasize, designers must always consider what users can and cannot contribute—but the designer's role shifts from sole author to facilitator and translator of a collective process.
    To understand participatory design, several essential concepts are best learned in sequence. The first is stakeholder involvement, the principle that all parties affected by a system—employees, customers, citizens, end users—should have a voice in its design. The second is co-design, the practical activity in which designers and users work together on design problems. This is not a meeting where users are asked what they want; it is a workshop where they sketch, build, and critique together. The third concept is mutual learning, the recognition that both designers and users must learn from each other. Designers learn about the domain and its practices; users learn about technological possibilities and constraints. The fourth is prototyping, which in participatory design serves as a shared language. A prototype—whether a paper mockup, a role-play scenario, or a working software version—gives users something concrete to react to and modify, making abstract design ideas tangible and debatable. The fifth concept is the ladder of participation, drawn from Sherry Arnstein's influential 1969 work on citizen participation. Arnstein's ladder ranges from manipulation and therapy at the bottom—where participation is a sham—through consultation and placation in the middle, to partnership, delegated power, and citizen control at the top. Participatory design aims for the upper rungs, where users hold genuine decision-making authority.
    The intellectual history of participatory design begins in the 1960s and 1970s, a period of growing demand for public involvement in decisions that affected people's lives. In Britain, the idea that the public should participate in planning was raised as early as 1965, and the UK government established a committee on public participation in planning in 1968. In Australia, citizens felt they were being planned "at" rather than "for." The first international conference of the Design Research Society, held in Manchester in 1971, was explicitly titled "Design Participation," signaling a broad interest across architecture, planning, and technology. In Scandinavia, the movement took a distinctive form. The "collective resource approach" developed strategies for workers to influence the design and use of computer applications in the workplace. The Norwegian Iron and Metal Workers Union project was a landmark: it moved from traditional research about workers to research with workers, directly changing the role of union clubs in the project. These Scandinavian projects adopted an action research approach, emphasizing active cooperation between researchers and workers to improve the latter's work situation. This history is crucial: participatory design was not born as a usability technique but as a democratic practice.
    The major figures of participatory design are those who built its methods and articulated its values. Kristen Nygaard, a Norwegian computer scientist and trade union activist, was central to the early projects; his work on the Norwegian Iron and Metal Workers Union project helped establish the collective resource approach. Pelle Ehn, a Swedish designer and researcher, was a key theorist and practitioner, developing the tradition of design-by-doing and design-by-drawing, where users and designers create and manipulate prototypes together. Susanne Bødker, also Scandinavian, contributed foundational work on the theory of participatory design, connecting it to activity theory and the broader concerns of HCI. These figures, active from the 1970s onward, codified the approach and trained generations of researchers. It is important to note that participatory design's political and methodological core was established in this period; later developments, such as its application to digital platforms and large-scale online communities, are extensions of this foundation rather than its origin.
    Participatory design's continuing significance in HCI is substantial. It remains a living tradition from 1970 to the present, and its methods have been adapted to new contexts: designing with communities for urban planning, with patients for health services, with citizens for public digital services, and with marginalized groups whose voices are often excluded from technology development. The approach has also influenced adjacent frameworks. Computer-supported cooperative work, which studies how people work together and how technology supports that collaboration, shares participatory design's concern with real work practices. Value-sensitive design, which emerged in the 1990s, extends participatory design's attention to stakeholder values, though it places more emphasis on conceptual analysis than on direct user involvement. In the current era of machine learning, participatory design has been revived as a corrective to the opacity of algorithmic systems, with researchers exploring how affected communities can participate in deciding what data is collected and what outcomes are optimized.
    For a reader approaching participatory design, no specialist technical knowledge is required. The essential prerequisites are a willingness to listen, a tolerance for messy collaborative processes, and a commitment to sharing design authority. Familiarity with basic design methods—sketching, prototyping, interviewing—is helpful but not necessary; these skills are often learned through practice in participatory workshops. What matters most is the mindset: the belief that users are experts in their own lives and work, and that good design emerges from genuine partnership rather than expert decree. Participatory design is not a set of rigid procedures but a stance toward design, one that asks not "what can we build for these people?" but "what can we build with these people?"
    The 5 concepts its tower teaches
    • Stakeholder Involvement
    • Co-design
    • Prototyping
    • Mutual Learning
    • Ladder of Participation

    Fly to its tower in Nousfarer

  4. 1980-2000
  5. 1981-Present

    Direct manipulation interface

    How should on-screen objects be seen and acted on?

    Fly to its tower in Nousfarer

  6. 1985-2010

    Usability Engineering

    How can we measure and ensure a product is usable?

    Fly to its tower in Nousfarer

  7. 1986-Present

    Computer-Supported Cooperative Work

    How do groups coordinate through technology?

    Fly to its tower in Nousfarer

  8. 1986-Present

    User-Centered Design

    How do we design around users' real needs?

    Fly to its tower in Nousfarer

  9. 1987-Present

    Situated Action

    How does human action actually unfold in practice?

    Fly to its tower in Nousfarer

  10. 1990-Present

    Contextual Design

    How do we model real work before designing?

    Fly to its tower in Nousfarer

  11. 1990-Present

    Inclusive design

    How do we design for the full range of people?

    Fly to its tower in Nousfarer

  12. 1990-Present

    Interaction Design

    What should happen between a person and a system over time?

    Fly to its tower in Nousfarer

  13. 1991-Present

    Design Thinking

    What process yields creative, human-fitting solutions?

    Fly to its tower in Nousfarer

  14. 1991-Present

    Ubiquitous Computing

    How should computing dissolve into everyday life?

    Fly to its tower in Nousfarer

  15. 1996-Present

    Value-Sensitive Design

    Whose values are built into a system?

    Fly to its tower in Nousfarer

  16. 1999-Present

    Critical and Speculative Design

    How can design provoke debate about possible futures?

    Fly to its tower in Nousfarer

  17. 2000-Present

    Data-Driven Experimentation

    Which design variant performs better at scale?

    Fly to its tower in Nousfarer

  18. 2000-Present

    User Experience

    What makes an interaction feel good overall?

    Fly to its tower in Nousfarer

  19. 2001-Present

    Embodied Interaction

    How does bodily engagement shape meaning with technology?

    Fly to its tower in Nousfarer

  20. 2010-Present

    Feminist HCI

    Whose perspectives are missing from design?

    Fly to its tower in Nousfarer

  21. 2010-Present

    Postcolonial Computing

    How do colonial legacies shape technology design and use?

    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.

ErgonomicsMan-Computer SymbiosisParticipatory DesignCognitive Modeling and Information Pr…Direct manipulation interfaceUsability EngineeringComputer-Supported Cooperative WorkUser-Centered DesignSituated ActionContextual DesignInclusive designInteraction DesignDesign ThinkingUbiquitous ComputingValue-Sensitive DesignCritical and Speculative DesignData-Driven ExperimentationUser ExperienceEmbodied InteractionFeminist HCIPostcolonial Computing

Beyond the field

Where Human Computer Interaction's ideas came from in other fields, and what they led to there: the strongest 12 of 161 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.

Human Computer Interaction is a planet in Nousfarer

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

Land on Human Computer Interaction

Related fields

Fields its ideas are linked to

More in Human Computer Interaction

See where Human Computer Interaction sits on the Map of Human Knowledge