What breaks first after an AI system is deployed: the model, the data, or the operation?
Summary
This article discusses the challenges of operational drift in deployed AI systems, questioning whether model quality, data, or business processes break first after deployment.
Similar Articles
The hardest part of deploying AI in real businesses isn’t the model, it’s who owns “is this still true?”
This article discusses how AI deployments in businesses often fail not due to model quality but because of the lack of ownership for keeping the model's knowledge current as the world changes, highlighting the challenge of 'silent drift' and the need for ongoing operational maintenance.
Most AI agent failures are organizational design failures, not model failures
The article argues that AI agent failures in production are often due to poor organizational design and undefined responsibility boundaries rather than model limitations. It proposes a maturity model distinguishing between AI assistants, automation, and AI employees to guide task ownership.
What actually breaks when you ship AI agents for real service businesses (a year in)
A year-long reflection on the hard parts of shipping AI agents for real service businesses, highlighting that infrastructure and edge cases matter more than the AI layer.
What broke first when you went from one AI agent to several?
A discussion on the operational challenges that arise when scaling from one AI agent to multiple, including context handoff, auth permissions, duplicated work, and cost tracking.
Something I keep seeing with AI projects that nobody talks about openly
This article highlights that many AI agent projects fail in production not because of model quality, but because teams launch without clearly defining what constitutes failure, missing critical edge cases that lead to confident incorrect outputs.