The problem with bad AI-generated work ('slop') isn't just poor writing. It's that subtle inaccuracies or context loss can derail meetings and create long, energy-wasting debates. This cognitive overload makes it difficult for teams to sense-make and ultimately costs more in human time than it saves.

The trend of 'vibe coding'—casually using prompts to generate code without rigor—is creating low-quality, unmaintainable software. The AI engineering community has reached its limit with this approach and is actively searching for a new development paradigm that marries AI's speed with traditional engineering's craft and reliability.

Product managers should leverage AI to get 80% of the way on tasks like competitive analysis, but must apply their own intellect for the final 20%. Fully abdicating responsibility to AI can lead to factual errors and hallucinations that, if used to build a product, result in costly rework and strategic missteps.

Product leaders must personally engage with AI development. Direct experience reveals unique, non-human failure modes. Unlike a human developer who learns from mistakes, an AI can cheerfully and repeatedly make the same error—a critical insight for managing AI projects and team workflow.

Simply instructing engineers to "build AI" is ineffective. Leaders must develop hands-on proficiency with no-code tools to understand AI's capabilities and limitations. This direct experience provides the necessary context to guide technical teams, make bolder decisions, and avoid being misled.

Top-performing engineering teams are evolving from hands-on coding to a managerial role. Their primary job is to define tasks, kick off multiple AI agents in parallel, review plans, and approve the final output, rather than implementing the details 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.

Borrowing from classic management theory, the most effective way to use AI agents is to fix problems at the earliest 'lowest value stage'. This means rigorously reviewing the agent's proposed plan *before* it writes any code, preventing costly rework later on.

Companies racing to add AI features while ignoring core product principles—like solving a real problem for a defined market—are creating a wave of failed products, dubbed "AI slop" by product coach Teresa Torres.