Skip to content

Blog

AI helps teams build waste faster unless they fix the root causes

Teams use the speed of AI agents to ship more features instead of better ones. Four problems teams claim to solve with AI are symptoms of root causes AI does not fix.

Written by

Organization and roles

Published: 23 December 2025 Updated: 2 min read

Paul Graham: “The source code of the median app was already slop before LLMs.”

AI can be game-changing. It can help teams build better products faster, but only if we are solving the right problems.

Faster output feeds feature bloat

AI agents ship code much faster. Teams are more efficient than ever.

Yet most teams use that efficiency to build more features. Not better features, and not the features customers actually need. The vicious cycle of feature bloat just spins faster.

The uncomfortable truth: most features create zero value. AI does not fix this. Without intentional change, AI only helps you build waste faster.

Four wrong problems we are “solving” with AI

“We need more features faster”

The real problem: most features create zero value. AI should free time for validation and testing. Instead, teams use it for more output, not better outcomes.

“Developers don’t know enough”

The real problem: companies don’t invest in training. The answer is investing in people’s growth, not replacing them with AI.

“Code quality is too low”

The real problem: AI learned from the poor code we are trying to escape. Feed AI slop and you get slop. Fix quality standards first.

“Requirements are unclear”

The real problem: for 30 years there was no time to clarify requirements for humans. Now it is suddenly fine to invest time documenting them for AI?

The pattern behind all four

An efficiency-driven culture. Nobody questions feature value. Zero investment in training. Poor quality standards. Unclear requirements.

AI can accelerate progress or accelerate dysfunction. The difference is whether you fix the root causes first. Using AI without fixing these issues is like running faster in the wrong direction.

Fix the root causes, then apply AI

Fix the root causes first, then apply AI to amplify the improvements:

  1. Question feature value. Use the freed time for validation, not for more features.
  2. Invest in training. Upskill your people, don’t replace them.
  3. Improve quality standards. Then use AI within those standards.
  4. Clarify requirements. For humans first, then AI can help keep them current.

AI multiplies what you already have. Fix the foundation, then multiply it.

AI can help teams build better products with less waste, but only if you use the efficiency gains to question what to build, validate features, and invest in your people.

Are you using AI to build more, or to build better?

Further reading

  1. The gap between AI-fast developers and AI-slow companies Individual developers report large gains with AI while whole companies report 5 to 15%. The gap is a management problem: companies added tools without reorganizing how they work. 1 min readShort post
  2. AI makes a feature factory faster, not better Automating the system you already have makes teams more efficient at building things nobody needs. The difference lies in where you invest the time AI saves: validation or more features. 2 min readShort post
  3. Agents finished the portal, then it waited in a queue An agent-built portal was ready to ship and waited on a gateway, a firewall rule, a certificate and QA. A factory shortens the build, and only a self-service platform shortens the wait around it. 1 min readShort post

All 15 posts on Organization and roles

ClientsCase study: A large DIY retailer in Germany

Test the constraint in your system

The Factory Readiness Assessment connects this research to your value stream, your data, and the next decision.

Training on this topic: Agentic Engineering for Engineering and Product Leaders
See the assessment

Want to check one team first? The self-check: twelve yes or no questions, three minutes, instant result, no account. Take the self-check