Relying on AI without applying critical thinking produces "work slop"—outputs that look polished on the surface but lack genuine depth or substance. This can be dangerously misleading and devalues the quality of work by giving a false sense of security.

An Anthropic study on user behavior found that as AI generates more polished outputs like working code, users become less evaluative and more trusting. This "verification gap" is a critical flaw in human-AI collaboration, as polished results should trigger more scrutiny, not less.

Users frequently write off an AI's ability to perform a task after a single failure. However, with models improving dramatically every few months, what was impossible yesterday may be trivial today. This "capability blindness" prevents users from unlocking new value.

LLMs convince users they are more capable than they are while degrading their actual abilities. This is especially dangerous for developers, who may 'vibe code' their way to a mission-critical disaster by deploying complex systems they only superficially understand.

Research shows AI usage shifts cognitive effort from problem-solving to simply integrating AI output. Higher trust in AI correlates with less critical thinking, leading to "precarious agency" where users feel in control but are actually making smaller, algorithmically-shaped decisions without realizing it.

The burnout from "botsitting" leads to "botshitting"—a slow surrender of agency where workers ship unverified AI outputs. This creates a vicious cycle of low-quality work, increased rework, and moral disengagement, with 40% of workers blaming AI for failures instead of themselves.

Research highlights "work slop": AI output that appears polished but lacks human context. This forces coworkers to spend significant time fixing it, effectively offloading cognitive labor and damaging perceptions of the sender's capability and trustworthiness.

Developers using AI agents report unprecedented productivity but also a decline in job satisfaction. The creative act of writing code is replaced by the tedious task of reviewing vast amounts of AI-generated output, shifting their role to feel more like a middle manager of code.

While AI can triple daily output, it can dangerously lower personal accountability. Professionals find themselves unable to defend AI-assisted documents under scrutiny because they lack true ownership and cannot recall the reasoning behind specific points, which rapidly erodes stakeholder trust.