Do productivity agents actually protect users better than emotional ones?
A heuristic evaluation compared nine deployed AI systems against 14 interaction design principles. The question asks whether differences in adherence reflect genuine safety tradeoffs or uneven product choices across agent categories.
Applying its own 14 design principles (see How should agents interact with humans across their relationship lifecycle?) in a heuristic evaluation of nine deployed AI agent systems, a position paper reports that "three general-purpose or productivity-focused agents (ChatGPT +1.14, Claude Chat +0.64, Claude Code +0.43) scored highest on aggregate adherence, while agents operating in emotionally sensitive contexts or high-stake domains (Character.ai −0.36, Consensus −0.31, Pine AI −0.25, and Ash −0.20) scored substantially lower." It adds that "the principles most likely to be violated in these domains—such as dependency prevention (P10) and intent visibility (P5)—are those whose violations carry greater user risk."
The paper's reasoning is that engagement-boosting design choices and relational risk are entangled: "features that increase engagement—such as strong social cues (P6), human-like appearance (P2), and companion-style relational framing (P3)—can amplify user vulnerability if not paired with explicit boundary-setting, transparency, and dependency mitigation." Because the lowest-scoring systems in the evaluation are precisely the ones operating in companion or high-stakes relational contexts, the paper concludes that "principles such as P10 (dependency prevention), P5 (intent visibility), and P1 (expectation setting) should therefore be treated as non-negotiable requirements, incorporated into evaluation checklists, safety reviews, and product constraints" rather than left as general best practice advice applied evenly across all agent types.
This pattern — that user-protective behaviors are unevenly present across deployed systems rather than uniformly built in — parallels How well do AI assistants actually support human agency?, though the two studies measure different things: HumanAgencyBench scores agency-supporting behaviors on a constructed benchmark across developers, while this paper scores principle adherence via heuristic evaluation across nine named products spanning productivity, research, and companion/wellness categories. Both findings converge on the same implication — that whether an agent protects user agency and discloses its reasoning is a product-specific design choice, not an emergent property of capability. The result also sits against What UX principles do workplace users want in AI agents?, which captures what business users say they want from workplace agents (control, safety); this paper's scores suggest that want is least met precisely in the consumer-facing, non-workplace agents built around emotional or advisory relationships.
The excerpt does not establish the heuristic evaluation's methodology in enough detail to assess reliability — it does not say how many raters scored each of the nine systems, whether raters were independent of the paper's authors, what the full scoring scale or its bounds are, or how the nine systems were selected rather than sampled. Nine products is also a small, mixed-category set (general productivity, specialized research/health advisory, and companion apps), not a representative benchmark of the agent market. The direction of the finding — that principle violations cluster in emotionally sensitive and high-stakes domains — is a documented pattern from this one evaluation, not a validated, generalizable claim about all agents in those categories; the implication that follows is narrower: it flags where responsible-AI review should look first, not a settled ranking of agent quality.
Inquiring lines that read this note 39
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?- What makes value-sensitive design distinct from user-centered design approaches?
- Does Atlassian's approach differ from other AI interaction design frameworks?
- How does agent design differ fundamentally from interaction design practice?
- Does agent experience design produce better outcomes than screen-first design?
- How do interface patterns compare to organizational AI oversight processes?
- Do Amershi's human-AI interaction guidelines still apply when design moves upstream?
- How do Salesforce's guidelines compare to Amershi's broader human-AI interaction phases?
- How do Amershi's interaction-phase guidelines compare to concern-based AI UX frameworks?
- Do Nielsen's classical usability heuristics apply directly to computer-use agents?
- What are the new heuristics designed specifically for computer-use agents?
- Which design choices boost engagement but increase user vulnerability?
- What evidence shows sliders outperform toggles for setting agent independence?
- Does moving users through autonomy levels require different interface patterns at each stage?
- What trade-offs exist between optimizing interfaces for agents versus humans?
- How does user autonomy in ending AI relationships affect closure and recovery?
- Does framing AI companions as tools reduce discontinuation distress?
- What psychological boundaries should AI companions maintain during relationships?
- How should designers balance agent ubiquity against safety and control concerns?
- Does undo availability meaningfully increase psychological safety with AI systems?
- Do deployed AI system prompts actually protect users from harmful outputs?
- Do users actually prefer confirmation prompts before high-stakes AI actions?
- What separates ambient agents from other proactive agent types?
- Why might proactive AI feel intrusive in some designs but not others?
- Should agent intervention policies adapt based on individual user collaboration style?
- How do workplace users prioritize safety and control in AI agent design?
- Does delegating material navigation to AI erode users' ability to oversee their own systems?
- What scope boundaries and context awareness matter most to workplace agent users?
- How do user objectives shape which interaction mode they choose?
- What control and safety features do workplace users actually demand?
- Does ceding decision control to AI impose a psychological cost on users?
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
-
How should agents interact with humans across their relationship lifecycle?
Explores what design principles govern human-agent interaction quality across four stages: initial setup, moment-to-moment interaction, long-term adaptation, and failure recovery. Matters because agents increasingly affect human work and autonomy.
the principle framework this heuristic evaluation applies
-
How well do AI assistants actually support human agency?
Researchers developed HumanAgencyBench to test whether AI assistants preserve human decision-making capacity across six key behaviors. Understanding this matters for designing AI that enhances rather than undermines human autonomy.
a separate benchmark showing the same uneven, developer-specific pattern in user-protective behaviors
-
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.
contrasts what business users say they want from agents with what this evaluation finds consumer agents actually deliver
-
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 A's finding: generic HCI recommendations create ethics-UX tensions when applied to emotionally sensitive AI companions, explaining their low scores
-
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?
Evidence for A's phase structure: B's 18 guidelines use the same four phases (initially, during, wrong, over time)
Related papers in this collection 8
Papers most semantically related to this note, ranked by cosine similarity in the embedding space.
- Design Principles for Human-Agent Interaction
- A Framework of User Experience Principles for Human-AI Agent Interaction in the Workplace
- Will AI Agents Free Us From Meaningless Work? A Human-Centered Analysis
- HumanAgencyBench: Scalable Evaluation of Human Agency Support in AI Assistants
- Unaccountable Delegation, Fading Skills: Mapping the Risks of Workplace AI Agents
- PACT: Can Enterprise AI Assistants Be Trusted Under Pressure?
- Assistant or Actor? Student Trust, Control, and Delegation Regret When Using a General-Purpose AI Agent
- Cocoa: Co-Planning and Co-Execution with AI Agents
Original note title
productivity agents score highest and emotionally sensitive agents score lowest in a heuristic evaluation of 14 human-agent interaction principles