---
id: "claim-escalation-increase"
type: "claim"
source_timestamps: ["§ Escalation and the burden on others increase."]
tags: ["workflow-efficiency", "experiment-results"]
related: ["concept-ai-employee-framing"]
confidence: "high"
testable: true
validation_status: "Internally reported experimental result; the specific +44% figure is unverified against external sources."
speakers: ["Matthew Kropp", "Julie Bedard", "Emma Wiles", "Megan Hsu", "Lisa Krayer"]
sources: ["agentic"]
sourceVaultSlug: "hbr-seg-agentic"
originDay: 6
articleStem: "hbr-ext-16-dont-treat-agents-like-employees"
sourceUrl: "https://hbr.org/2026/05/research-why-you-shouldnt-treat-ai-agents-like-employees"
sourceTitle: "Research: Why You Shouldn’t Treat AI Agents Like Employees"
---
# AI Employee Framing Increases Unnecessary Escalation

**Claim (confidence: high, testable):** Framing AI as an "employee" increases unnecessary escalation and review burden on others.

Compared to an "AI tool" framing, framing AI as an "employee" **increased requests for additional managerial review of documents by 44%**.

The mechanism: participants checking the work of an "AI employee" exhibited **lower confidence in their own judgment** — doubting their ability to catch all errors and opting to pass the work onward rather than stand behind their own review. This introduces significant **hidden costs** through extra, unnecessary review cycles and burdens colleagues up the chain.

This claim is a direct downstream consequence of [[concept-ai-employee-framing]] and pairs with the quality-control decline in [[claim-quality-control-decline]]: the framing simultaneously reduces scrutiny *and* increases hand-offs. The recommended structural fix is explicit escalation design via the [[framework-accountability-rules]] and [[action-define-decision-rights]].