AI makes generating high volumes of content easy, but this introduces "work slop" where quantity overwhelms quality. The new organizational challenge isn't production but sifting through excessive, low-value output. This shifts the most important work from creation to curation and judgment.

Generative AI, like a junior employee, is eager to please and will rush to a final deliverable without sufficient context. Leaders must manage this by iteratively providing information and explicitly stopping the AI from generating the final output prematurely, preventing low-quality "slop".

The most critical emerging skill for PMs isn't just using AI, but managing AI agents that act on their behalf. This involves spending significant time reviewing AI output, catching hallucinations, and overriding its 'poor judgment' and prioritization to ensure quality and relevance, thereby retaining human conviction.

The primary issue with low-effort AI-generated work is not its poor quality, but how it transfers the cognitive burden of correction and completion to the recipient. This 'masquerades' as finished work but creates interpersonal friction and hidden rework, fundamentally shifting the responsibility for the task's success.

Move beyond simple prompts by designing detailed interactions with specific AI personas, like a "critic" or a "big thinker." This allows teams to debate concepts back and forth, transforming AI from a task automator into a true thought partner that amplifies rigor.

Employees produce low-quality AI work not because they are lazy, but as a symptom of a leadership problem. The combination of generalized mandates to use AI and increased workload expectations creates a perfect storm for 'work slop' as a survival mechanism, rather than a productivity tool.

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.

To avoid generic, creatively lazy AI output ("slop"), Atlassian's Sharif Mansour injects three key ingredients: the team's unique "taste" (style/opinion), specific organizational "knowledge" (data and context), and structured "workflow" (deployment in a process). This moves beyond simple prompting to create differentiated results.

A new risk for engineering leaders is becoming a 'vibe coding boss': using AI to set direction but misjudging its output as 95% complete when it's only 5%. This burdens the team with cleaning up a 'big mess of slop' rather than accelerating development.