Botsitting: The Work Draining AI Gains

What It Covers

A Glean and Work AI Institute report on "bot sitting" reveals that workers spend 6.4 hours weekly managing AI outputs, nearly offsetting the 11 hours AI saves them. The episode examines why individual AI productivity gains rarely translate to organizational performance improvements, and what the 13% of high-performing organizations do differently.

Key Questions Answered

• •Bot Sitting Breakdown: Workers spend 6.4 hours weekly on bot sitting tasks: 2.3 hours feeding AI context, 2.2 hours supervising outputs, and 1.7 hours debugging errors. Every 10% increase in time spent feeding AI context correlates with a 25% higher likelihood of worker burnout, making context management the highest-fatigue AI activity.
• •Tool Sprawl Tax: Workers using multiple AI tools are 35% more likely to report frequent bot sitting. Currently, 60% of workers rerun the same prompt across multiple tools because the first output was insufficient. Consolidating to fewer AI tools directly reduces the coordination overhead that erodes productivity gains from automation.
• •Peer Adoption Multiplier: When a direct manager uses AI, employees become 2.4 times more likely to adopt it. A direct teammate's adoption raises that to 3.2 times. Cross-functional teammates drive the highest adoption rate at 5.6 times, because their workflows survive contact with real organizational messiness rather than idealized processes.
• •Transformative Organization Markers: The 13% of organizations reporting significant AI-driven performance gains share three practices: measuring output quality over vanity metrics, giving 71% of employees visibility into their own AI usage data (versus 40% at underperforming orgs), and reviewing AI governance policy regularly at a 93% rate versus 55% elsewhere.
• •Cognitive Offloading Risk: As AI trust increases, workers progressively stop understanding outputs, then stop interrogating them, then stop feeling responsible for them. Heavy AI users are 3.4 times more likely than light users to blame the tool when outputs fail. High achievers counter this by treating bot sitting as a learning mechanism rather than a maintenance burden.