How should AI systems be designed across different interaction phases?
Can a small set of general guidelines help practitioners design better AI-infused products across different moments—initial setup, active use, error handling, and long-term adaptation?
Amershi, Weld, Vorvoreanu, Fourney, Nushi and colleagues at Microsoft Research (CHI 2019) synthesize "over 150 AI-related design recommendations collected from academic and industry sources into a set of 18 generally applicable design guidelines for human-AI interaction." The 18 guidelines are grouped into four categories "based on when during the user's interaction they applied": "Initially" (Guideline 1 and 2), "During interaction" (Guidelines 3 through 6), "When wrong" (Guidelines 7 through 11), and "Over time" (Guidelines 12 through 18). The set was "validated through multiple rounds of evaluation including a user study with 49 design practitioners who tested the guidelines against 20 popular AI-infused products," with guidelines applied or reviewed across "10 product categories" in total.
The authors describe a three-source, multi-phase consolidation. In Phase 1 they gathered candidate guidelines from an internal/external industry review, public articles and editorials, and scholarly HCI papers, arriving at "168 potential AI design guidelines." Three team members affinity-diagrammed these into 35 concepts, then filtered out concepts judged "too vague to design for directly (e.g., 'build trust'), too specific to a particular AI scenario (e.g., 'establish that the bot is not human'), or not AI specific (e.g., 'display output effectively')," leaving 20 guidelines. In Phase 2, a modified heuristic evaluation had 11 team members inspect 13 AI-infused products (email filtering, navigation, e-commerce recommendations, photo organization, a design-assistance feature, a research-assistance feature, a news feed, web and image search) over one-hour sessions looking for applications and violations of each guideline. That round surfaced ambiguity between Guideline 9 ("allow efficient correction") and Guideline 17 ("allow coarse controls") — several evaluators mistook instance-level corrections for global settings — so the authors reworded Guideline 17 to explicitly say "global."
Against the newer notes nearest this one, this paper is the generic, interface-level ancestor they build on or react to. How should AI interfaces handle the shift from doing to supervising? extends the same project — guidelines for designing the interaction surface between a person and an AI system — into agentic territory where plans are negotiated rather than just corrected. What UX principles do workplace users want in AI agents? is a narrower, 2026 descendant of the same consolidation method (recommendations distilled into a numbered principle set, then validated with practitioners) aimed specifically at workplace agents rather than AI-infused systems in general. And Does granting agents more autonomy undermine human oversight? reads, from this paper's vantage point, like a report on exactly the failure modes several of these guidelines were meant to forestall — efficient correction, conveying the consequences of automated actions, and controllable levels of autonomy.
The excerpt available here covers the paper's abstract, introduction, related work, method, discussion, and limitations — it does not include Table 1's actual text for the 18 guidelines, so their individual wording is not established in this note. The authors themselves flag that the guidelines may not transfer well to systems without a graphical interface (voice assistants, activity trackers) or to high-risk, highly regulated domains (semi-autonomous vehicles, robot-assisted surgery, financial systems), and they note an open, unresolved tension between guidelines — conveying the consequences of a system's actions (Guideline 16) can work against letting the system actively learn from user behavior (Guideline 13) — that they say needs further research rather than claiming to have solved. The implication is that this 2019 guideline set should be read as a generic, GUI-oriented baseline that predates today's agentic LLM systems; later agent-specific frameworks are better read as filling gaps this paper itself named than as replacing it.
Inquiring lines that read this note 3
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 should control and autonomy be allocated in human-AI collaboration?Related concepts in this collection 4
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
-
How should AI interfaces handle the shift from doing to supervising?
Nielsen explores what UI architecture allows users to oversee AI work rather than perform it themselves. This matters because intent-based systems fundamentally change the user's role from operator to supervisor.
extends the same interface-guideline project into agentic systems where plans are negotiated, not just corrected
-
What UX principles do workplace users want in AI agents?
A multi-method study asked business users what design principles matter most for human-AI collaboration at work. The findings prioritize oversight and reliability over convenience.
a narrower, 2026 descendant of the same recommendation-distillation method, aimed at workplace agents specifically
-
Does granting agents more autonomy undermine human oversight?
Explores whether the design of autonomous AI systems—by giving agents greater independence—actually weakens the human overseer's ability to catch problems. Matters because oversight is a key safeguard against AI failures.
documents the erosion of oversight and correction capacities these guidelines were designed to protect
-
Why don't design recommendations transfer cleanly to AI companions?
This research explores why design guidance from adjacent fields like trustworthy AI fails to apply straightforwardly to AI companions. It asks whether ethics and UX can be treated separately or must be negotiated together for each design choice.
Qualifies Amershi's guidelines: borrowed cross-domain recommendations create ethical-UX tensions when applied specifically to AI companion design
Related papers in this collection 8
Papers most semantically related to this note, ranked by cosine similarity in the embedding space.
- Guidelines for Human-AI Interaction
- Large Language Models for User Interest Journeys
- A Framework of User Experience Principles for Human-AI Agent Interaction in the Workplace
- Cyborgs, Centaurs and Self-Automators: The Three Modes of Human-GenAI Knowledge Work and Their Implications for Skilling and the Future of Expertise
- Assistance or Disruption? Exploring and Evaluating the Design and Trade-offs of Proactive AI Programming Support
- Keeping an Eye on AI: A Framework for Effective Human Oversight of AI Systems
- Understanding the Design Taxonomy of AI-Mediated Interpersonal Communication Experiences in HCI: A Scoping Analysis
- Human-Centered Artificial Intelligence: Reliable, Safe & Trustworthy
Original note title
Amershi and colleagues' 18 guidelines for human-AI interaction are organized by phase — initially, during interaction, when wrong, over time