--- title: "AI Slop Produced by a Human Is a Yellow Flag" url: "https://atlan.com/context-and-chaos/issue/ai-slop-is-a-yellow-flag/" description: "Adoption numbers tell you people are using AI. They don't tell you if the company is getting more capable. Four rebuilds, one decision rule, and the case for organizational metabolism." keywords: "Enterprise AI, AI Strategy, AI Adoption, Organizational Design, AI Agents" --- > Atlan is hosting Context Conference, bringing together the leaders and builders at the frontier of giving AI the context it needs to understand their business. It runs online on October 28, 2026, from 11:00 AM to 2:00 PM ET. Atlan co-founder Prukalpa Sankar opens and closes the day. Leaders from AstraZeneca, BNY and Verizon share why they invest in context and what they get from it. Registrants get early access to The AI Context Gap, a new study from MIT Technology Review Insights. Register: https://atlan.com/context-conference/ A Context & Chaos deep dive by Prukalpa Sankar (Co-founder & Co-CEO, Atlan), published July 30, 2026 (11 min read). Adoption numbers tell you people are using AI; they don't tell you if the company is getting more capable. The essay argues that the durable advantage is organizational metabolism, drawing on Atlan's own rebuild around AI. Originally published at https://atlan.com/frontier/essays/becoming-a-frontier-company-in-the-open/. **"AI slop produced by a human is a yellow flag. Sometimes it's worse than not using AI at all."** The author sent that to Atlan's team a year earlier, as more work arrived as polished AI-generated artifacts: enablement docs became interactive websites, ideas became prototypes in hours, tabs upon tabs of things that looked finished. Much of it went unused or was discarded soon after. The cost of making something fell without raising the odds it would matter, and low-value output became context for the next person, or the next model, to build on. Slop produced more slop. The word *human* is the point: a model generated the artifact, but a human chose the problem, accepted the quality, and decided it deserved other people's attention. Not using AI might make one person slower; using it without judgment can make the whole organization slower. What judgment is to a single artifact, organizational metabolism is to a company: the thing that decides whether a new capability becomes a better outcome, or just more output. ## The adoption trap - Atlan tracks licenses provisioned, weekly active users, tokens consumed, agents created, hours supposedly saved and artifacts shipped; investors say it is in the top 1% of AI adopters. Those numbers measure usage, not whether the company is getting more capable. - An enablement site matters only if it changes how the field sells; an agent only if it improves a consequential decision; a campaign only if it earns attention and trust. - When creation was expensive, polish signaled commitment and effort was a natural brake. AI removed the brake, instincts haven't caught up, and the result is "AI output theatre". ## So what makes a company frontier? The durable advantage is organizational metabolism. AI is a foundational capability to redesign work around, not just a tool to adopt. Atlan rebuilt its customer success team's AI architecture four times in one year, rebuilding each time it hit a wall instead of patching: 1. A prompt-based setup. 2. Agents and humans working together through an explicit org chart. 3. A single proactive system living inside the team's chat. 4. In progress: one system with a shared brain, an interface where the team manages tasks and gives feedback, and self-learning loops that improve every time a human corrects them. No regret: each rebuild reimagined the work. Models, tools and today's frontier workflows will change; the durable advantage is how quickly you notice a new possibility, test it against reality, absorb what you learn, and change how you work. ## Change the outcome, not just the output Frontier companies get more ambitious, not just more efficient. Ten times the emails, slides or code confuses production with capability. The better question: "If today's capabilities had always existed, would we have designed this task, role, or team at all?" Example: an Atlan marketer built a personalized web experience that uses intent signals to infer a visitor's company, pulls the context Atlan already has about that account, and generates the experience as the visitor arrives. It is not pre-generating a hundred landing-page variants; it changes the unit of work from producing pages to assembling an experience around a person's context. Still an experiment, not a proven growth engine; open questions include where personalization becomes inaccurate, invasive or untrustworthy, and what review and stopping rules it needs. ## The organization has to absorb the change Knowledge work split outcomes across specialist functions connected by handoffs, which created scale and protected expertise but fragmented ownership and made moving context a job of its own. AI gives one person capabilities that once lived across functions (a marketer can build, a PM can prototype, an operator can create internal software), so every handoff has to re-earn its cost. Some boundaries stay: independent review for high-stakes claims, deep expertise for deep technical work, accountable owners for privacy, security and brand risk. **The decision rule being tested:** remove a handoff when it exists mainly to transport context; preserve independence when it exists to challenge judgment, control risk, or contribute scarce expertise. The structure under test is small cross-functional pods. Early sign: at Atlan's marketing retreat the author mostly heard gratitude, and that the team couldn't believe they'd ever worked the old way. ## Is the real frontier human? The more powerful AI becomes, the more the operator matters. Given the same model, one person produces ten acceptable versions of an existing asset; another asks whether the asset should exist and attempts an outcome once beyond an individual's reach. Judgment decides what's worth doing; taste decides whether it's any good. Experts have to keep consenting to become beginners. Atlan uses a simple grid, human skills against AI leverage, to think about where human impact comes from. Roles and professional identities will shift, but fear cannot be the operating principle; organizations must create room for learning, make changing expectations explicit, and help people build new skills. The human frontier is whether a company can increase machine leverage without diminishing human agency. ## Writing it down, in the open Open questions nobody has a finished playbook for: - What happens to the role of the manager? - How should AI-native work be measured? - What does a 100x outcome look like without becoming a 100x productivity treadmill? - Which kinds of expertise matter more, and which handoffs disappear? Many companies writing openly about AI-native work were born in the AI era; most companies have existing customers, roles, systems and identities and must transform without losing them. Atlan sits between those worlds: rebuilding itself around AI while building technology for large enterprises doing the same. Social media turns AI transformation into a highlight reel; Atlan will be "the laboratory, not the hero of every story." The frontier company will be the one that can responsibly shorten the distance between a new capability and a better outcome, and keep changing its form without losing its purpose. **Five-minute test:** take the last AI-generated artifact your team shipped and ask who chose the problem, who accepted the quality, and who decided it deserved other people's attention. If no one can answer, you've found your slop. ## Atlan Frontier Labs Launched the same week: the build log documenting Atlan's rebuild in public ("real numbers, real failures, human gates"), at [Becoming Frontier](https://atlan.com/frontier/). Essays linked from the page: - [We rebuilt marketing around 300 shared skills](https://atlan.com/frontier/essays/we-rebuilt-marketing-around-it/), by Surendran Balachandran - [An agent watches every page on our website, because we ship faster than we can watch](https://atlan.com/frontier/essays/one-agent-never-stops-working/), by Dubem & Kushagra - [We turned our revenue intelligence from one analyst into a fleet of agents](https://atlan.com/frontier/essays/from-one-analyst-to-a-fleet-of-agents/), by Mohammed Fadil Readers who built something with AI that made their team meaningfully better are invited to submit it for the build log. ## About the author Prukalpa Sankar is Co-founder and Co-CEO of Atlan and the founding author of Context & Chaos. She writes about context engineering, AI readiness, and the organizational infrastructure enterprises need to make AI actually work. [LinkedIn](https://www.linkedin.com/in/prukalpa/). ## Related reads - [I Got Long](https://atlan.com/context-and-chaos/issue/i-got-long/) (July 2026) - [The GitHub for Context Doesn't Exist Yet](https://atlan.com/context-and-chaos/issue/the-github-for-context-doesnt-exist-yet/) (July 2026) - [If Intelligence Is Abundant, What Is the Moat?](https://atlan.com/context-and-chaos/issue/if-intelligence-is-abundant-what-is-the-moat/) (May 2026) - [Your Team Isn't Afraid of AI. They're Afraid of Being Wrong.](https://atlan.com/context-and-chaos/issue/your-team-isnt-afraid-of-ai-theyre-afraid-of-being-wrong-about-ai/) (April 2026) Context & Chaos is Atlan's community newsletter on context engineering, governance, architecture and discovery. Browse all articles at https://atlan.com/context-and-chaos/ or pitch a piece at https://atlan.com/context-and-chaos/contribute/.