Is design for agents becoming the next major design paradigm?
Does the emergence of LLMs signal a fundamental shift in design practice, where agent design subsumes interaction design the way interaction design once absorbed graphic design? This explores whether we're witnessing a historical paradigm change comparable to mass manufacturing's rise.
Hugh Dubberly, of Dubberly Design Office, argues in an October 2025 IxDC Beijing talk deck that design is entering a third paradigm, and that this paradigm is "design for agents." He frames the move as following an axiom of design theory: "Design practice changes as new technologies emerge," where "a relatively stable, normal period" gives way to a "crisis" that produces a "new paradigm," which then normalizes before the cycle repeats. The lineage he traces runs from hand-craft production, through mass manufacturing (circa 1900) subsuming most hand-craft design into graphic and product design, through interaction design subsuming "large parts of graphic design," to a third paradigm, circa 2025, in which "design for agents will subsume large parts of interaction design." He attributes the shift to large language models (LLMs) acting not only as design tools but also a new material of design.
The reasoning runs through services rather than products: Dubberly describes services as "processes, coordinating the actions of people and products," co-created by producers and consumers "at the point of delivery." Because "users will show up with their own agents as well," he argues "every service will offer software agents to assist consumers and providers," concluding that "agent design is becoming core to service design." He grounds the term "agent" in Russell and Norvig's definition — "anything that can be viewed as perceiving its environment through sensors and acting upon that environment through actuators" — and lists what designing agents implicates: rules for choosing actions, information, feedback, goals, teleology, cybernetics, learning, and play.
The claim sharpens Does agentic AI succeed through process redesign or workflow layering? by pushing the redesign argument up a level: where Deloitte argues enterprises must redesign processes rather than layer agents onto existing workflows, Dubberly argues the discipline doing that redesigning — interaction design — is itself being subsumed by a successor paradigm, design for agents. It also reframes Can AI agents truly operate above the loop at enterprise scale?: McKinsey describes humans repositioned above or within AI-first workflows as an organizational design; Dubberly treats that repositioning as a design-practice question, with service design absorbing agent design the way interaction design once absorbed graphic design. The companion note, How should agent capabilities be organized into functional layers?, gives the layered agent architecture this paradigm shift is meant to cover.
The deck is a conference talk's set of assertions and an explicit axiom, not a study of design practice; it offers no survey of studios or firms already practicing "design for agents," no adoption figures, and no criteria for when a paradigm is considered to have taken hold. The argument rests on an analogy to two prior shifts (mass manufacturing, interaction design), not on evidence that the current shift is underway at comparable scale. The claim should be read as Dubberly's extrapolation from design history, holding only as strongly as that two-case analogy supports.
Inquiring lines that read this note 4
This note is a source for these research framings, grouped by the broader line of inquiry each explores. Scan the bold lines of inquiry; follow any specific question forward.
How does interface design shape effectiveness in human-AI collaboration?- How does agent design differ fundamentally from interaction design practice?
- Why should service design absorb agent design rather than keep them separate?
- What evidence would prove agent design has achieved paradigm status?
- How do role dynamics change when UX designers, engineers, and product managers prototype together?
Related concepts in this collection 5
This note in its neighbourhood — explore the map, then jump to a related concept in the list below.
Click a node to walk · click center to open · click Open in graph to see this note in the full knowledge graph
-
Does agentic AI succeed through process redesign or workflow layering?
Explores whether organizations deploying agents should redesign end-to-end operations or integrate agents into existing workflows. Matters because the choice affects ROI, architecture investment, and governance requirements.
both argue agent adoption requires structural redesign, not incremental layering, though Dubberly locates it at the level of the design discipline itself
-
Can AI agents truly operate above the loop at enterprise scale?
McKinsey proposes a radical organizational shift where AI agents handle end-to-end workflows with humans positioned for strategic oversight. This exploration examines whether that model reflects current practice or remains aspirational.
situates Dubberly's "agent design as core to service design" against McKinsey's enterprise-pillar reorganization
-
How should agent capabilities be organized into functional layers?
Explores whether agent systems can be understood as stacked layers—from basic chatbots through system prompts and RAG to hierarchical supervisors—and what design trade-offs this architecture creates.
the sibling note, describing the layered architecture Dubberly proposes for the agents this paradigm shift introduces
-
Has AI work moved designers upstream from screens?
Salesforce Design claims AI systems require designers to shift focus from creating user interfaces to architecting the invisible orchestration and semantic foundations that precede them. The question asks whether this represents a genuine and necessary change in design practice.
Evidence for A's paradigm shift: shows interaction design giving way to pre-screen scaffolding work, as Dubberly's agent-design paradigm predicts
-
Can AI become a design material for adaptive interfaces?
Can designers treat AI as a core material—like clay or steel—to build interfaces that reshape themselves at runtime based on user requests, rather than scripting predetermined responses?
Evidence for A: Sentient Design's 14 patterns instantiate treating AI/LLMs as a design material, Dubberly's claimed third paradigm
Related papers in this collection 8
Papers most semantically related to this note, ranked by cosine similarity in the embedding space.
- The Rise of Design for Agents
- 2025 in Review: Design Gives AI Meaning
- Designing For Agentic AI: Practical UX Patterns For Control, Consent, And Accountability
- Beyond Anthropomorphism: a Spectrum of Interface Metaphors for LLMs
- Designs for the frontier future
- Design Principles for Human-Agent Interaction
- A Framework of User Experience Principles for Human-AI Agent Interaction in the Workplace
- "When to Hand Off, When to Work Together": Understanding Concurrent Human-Agent Interaction in Shared Co-Creative Workspaces
Original note title
Dubberly argues design for agents will subsume interaction design and become core to service design