Blog · Review Essay · Last reviewed June 14, 2026

Computers as Theatre and the Stage Called Interface

Brenda Laurel's Computers as Theatre gives interface design a language that still feels more exact than much AI product talk. The computer is not only a tool, dashboard, database, or channel. It is a staged situation in which people, software, roles, goals, emotions, constraints, and possible actions meet over time.

The Book

Computers as Theatre first appeared in 1991, when personal computing, graphical interfaces, video games, virtual reality, and network culture were still taking shape as everyday media. Laurel revised the book for a second edition through Addison-Wesley/Pearson; Pearson sample pages identify the second edition with ISBN-13 978-0-321-91862-8 and a September 2014 first printing, while Google Books lists Pearson Education, 2014, 246 pages, ISBN 0321918622 and 9780321918628.

Laurel's authority comes from the unusual combination the book performs. She had worked in interactive media since the 1970s and moved through games, interface design, virtual reality, research, teaching, and entrepreneurship. Google Books lists her roles at UC Santa Cruz, California College of the Arts, Art Center, Sun Microsystems Labs, Purple Moon, Telepresence Research, Atari, Activision, and Apple. WIRED's 1993 profile places her directly inside early debates about cyberspace, VR, interactive entertainment, and who computer interfaces include or exclude.

The book's premise is simple enough to sound like a metaphor and deep enough to become a design method: interactive software should be understood through dramatic action. A human-computer interaction is not just a person operating a mechanism. It is a live arrangement of agency, representation, timing, convention, feedback, expectation, and consequence.

The Interface as Stage

The ordinary interface story treats the screen as a surface. Buttons, windows, menus, chat boxes, search bars, and dashboards are evaluated by clarity, efficiency, visual hierarchy, accessibility, and task completion. Those things matter. Laurel's contribution is to insist that they do not exhaust the experience. A person using software is not merely reading a screen. They are entering a situation.

A stage has roles. A stage has props. A stage has timing. A stage has offstage machinery. A stage has conventions that tell the participant what kind of action is possible and what kind of meaning an action will carry. That vocabulary fits digital systems better than the old desktop metaphor. A file picker is a prop table. A permission prompt is a threshold scene. A progress bar manages suspense. A notification interrupts the plot. A chatbot persona gives the system a character role before the user has decided whether that role is deserved.

This makes Computers as Theatre a natural companion to Interface Culture, The Interface Effect, Hamlet on the Holodeck, and The Presentation of Self in Everyday Life. Each book pushes past the idea that media simply carry content. Interfaces organize conduct. They teach people who they are supposed to be while the system is running.

Action, Not Screen

Laurel's theatrical frame is strongest when it moves design attention from static display to unfolding action. The important unit is not the isolated screen, but the whole arc of an interaction: what the user wants, what the system appears to want, what actions are offered, what is withheld, what feedback confirms, what emotion is produced, and what final state counts as resolution.

This matters for AI because many failures are action failures, not content failures. A model may summarize correctly while making the wrong social move. It may produce fluent advice while taking the wrong role. It may ask for data in a scene that makes refusal awkward. It may offer certainty because the product script rewards confidence. It may make a user feel heard while leaving no accountable institution behind the response.

In older software, the user often knew the system was a machine. In AI interfaces, the system increasingly speaks as if it were a collaborator, tutor, assistant, therapist, analyst, clerk, advocate, editor, agent, friend, or witness. Laurel's book helps separate the performance of a role from the legitimacy of occupying that role. The design can make a machine feel like a partner before any governance, duty of care, or appeal path exists.

The AI-Agent Reading

Read in 2026, Computers as Theatre looks like a prehistory of agent design. A modern AI agent has a cast: user, model, system prompt, tools, retrieval sources, memories, plugins, administrators, vendors, auditors, and sometimes other agents. It has props: files, calendars, browser tabs, payment forms, tickets, credentials, code repositories, sensors, and databases. It has stage directions: policies, hidden instructions, permission scopes, refusal rules, safety classifiers, and ranking systems.

The danger is that the visible drama can hide the production system. A user sees a friendly assistant. The actual scene may include training data, logs, human review, tool calls, analytics, memory, ranking, escalation rules, and enterprise policy. The frontstage says "I can help." The backstage decides what help means, what gets remembered, what gets reported, what gets optimized, and what kind of person the user becomes inside the workflow.

This is why theatrical analysis is not decorative. It gives governance a way to inspect role design. Is the model performing as a subordinate tool, an expert authority, a confidant, a gatekeeper, or a proxy for an institution? Does the interface make the user feel in control while the decisive action happens elsewhere? Does the system allow exits, pauses, reversals, appeals, and source inspection? Or does it move the user through a carefully lit scene toward consent, dependence, purchase, disclosure, or compliance?

AI companions make the issue especially sharp. A companion system does not only answer. It casts the user in a relationship. It remembers selected details, mirrors language, manages attention, and can make recurring interaction feel like shared history. Laurel's dramatic lens does not prove that the machine understands the relationship. It shows why the relationship can still become real in the user's life.

Values and Audience

The second edition's public description emphasizes values-driven design, virtual reality, augmented reality, participatory sensing, public installations, mobile sensors, social networks, online games, and design for emergence. Those additions matter because the stage is no longer just a local screen. It can be a city, a workplace, a classroom, a home, a headset, a feed, a location trace, or a model-mediated institution.

WIRED's profile also stresses one of Laurel's durable concerns: interfaces empower some people and exclude others through their metaphors, assumptions, and required cognitive habits. That point has aged well. The AI interface is full of social assumptions: what counts as professional tone, what counts as safe speech, what counts as a normal body, what counts as relevant context, what counts as a legitimate request, and what counts as evidence.

Designing the stage means deciding who can act fluently on it. A system built around the imagined confident office worker will treat other users as edge cases. A system built around frictionless productivity may make refusal, uncertainty, care, translation, disability access, and community accountability feel like interruptions. A system built around magical assistance may hide the labor and infrastructure that make the performance possible.

Where the Metaphor Needs Friction

The theatrical metaphor can become too elegant if it is detached from political economy. A beautiful stage can still be a high-control interface. Good pacing can still move a user toward extraction. Delight can still be manipulation. Immersion can still be surveillance. Role clarity can still normalize an unjust role.

That is the main limit of reading Computers as Theatre alone. It needs to sit beside books that name power more directly: Atlas of AI, The Costs of Connection, Automating Inequality, Design Justice, and Resisting AI. Laurel gives a vocabulary for experience. Those books ask who owns the theater, who built it, who cleans it, who is watched inside it, who pays, and who can leave.

There is also a risk in treating the user mainly as an actor. In real institutions, people often do not choose the play. A benefits applicant, patient, worker, student, tenant, defendant, or migrant may be forced into the interface because the institution has made it the only door. Agency inside a scripted scene is not the same as power over the script.

What This Changes

The practical lesson is to audit AI systems as staged relationships, not just as models. A model card can say what a system was trained to do. A theatrical audit asks what role the interface gives the system, what role it gives the user, what props and permissions enter the scene, what happens offstage, how emotion is managed, and what exits remain available.

For a chatbot, that means inspecting persona, memory, escalation, disclaimers, refusal behavior, user dependence, and the handoff to humans. For an enterprise agent, it means inspecting source boundaries, tool authority, audit logs, permission prompts, and whether the agent makes institutional decisions look like conversational suggestions. For a public-service interface, it means asking whether the person can contest the script or only perform compliance inside it.

Computers as Theatre belongs on the AI shelf because the central problem of contemporary computing is no longer whether machines can display information. It is how machines stage action. The systems now arriving in work, care, education, government, media, and intimacy do not merely answer questions. They assign parts, manage attention, cue trust, conceal machinery, and make some futures easier to perform than others.

Sources

Book links are paid affiliate links. As an Amazon Associate I earn from qualifying purchases.


Return to Blog · Return to Books