---
id: "question-detecting-ai-content"
type: "open-question"
source_title: "Don't Let AI Slop Muck Up Your Company's Processes"
source_url: "https://hbr.org/2026/06/dont-let-ai-slop-muck-up-your-companys-processes"
source_timestamps: ["§ How to Deal with Knowledge Decay?", "¶20"]
tags: ["ai-detection", "governance"]
related: ["claim-policing-ai-impossible"]
resolutionPath: "Development of highly accurate, cryptographically secure watermarking for AI outputs, or a complete shift away from evaluating unstructured text in favor of verifiable structured data."
sources: ["execution"]
sourceVaultSlug: "hbr-seg-execution"
originDay: 8
articleStem: "hbr-sig-54-ai-slop-processes"
sourceUrl: "https://hbr.org/2026/06/dont-let-ai-slop-muck-up-your-companys-processes"
sourceTitle: "Don’t Let AI Slop Muck Up Your Company’s Processes"
---
# How can organizations accurately detect AI content?

**Open question.** The authors state that policing AI usage is virtually impossible because workers conceal it ([[claim-policing-ai-impossible]]). If policing is impossible, how can organizations effectively enforce the provenance tracking of unstructured data ([[action-track-provenance]]) or validate human value-add ([[concept-knowledge-validation]]) without reliable detection mechanisms?

**Possible resolution path.** Highly accurate, cryptographically secure watermarking for AI outputs — or a complete shift away from evaluating unstructured text in favor of verifiable structured data ([[action-restrict-unstructured-inputs]]).

The enrichment overlay adds a partial answer: NIST's toolbox of acceptable-use policies, disclosure requirements, synthetic-content labeling, and whistleblower protections offers imperfect-but-real partial control, suggesting the problem is difficult rather than hopeless.