AI-first delivery bottlenecks
ThoughtWorks: AI coding tools create local speed gains but slow overall delivery without SDLC-wide orchestration Developer SummitTL;DW
- Imbalanced AI adoption—enhancing only developers while ignoring designers, product managers, security—creates upstream and downstream bottlenecks; Theory of Constraints shows optimizing one part of SDLC without cross-functional support actually slows overall delivery.
- AI coding agents expose the "lethal trifecta": access to sensitive information, susceptibility to malicious input via context poisoning, and ability to exfiltrate data—making your development environment a new attack surface.
- GitClear 2023-2024 data shows code refactoring declining, code churn rising, and code added accelerating with AI—indicating increased technical debt, rework, and debugging burden despite higher code generation velocity.
- Token spend scales uncontrollably: power users burning $20/developer/day ($400+/month) versus initial $20/month plans; rogue AI usage and unmonitored model deployments create compliance and cost visibility crises.
- Value stream mapping—identifying friction points across your entire path-to-production from ideation to production maintenance—is the only way to justify ROI and adopt AI strategically rather than chasing shiny tools.
- Effective coding agents require mature engineering practices: strong CI/CD, comprehensive test harness, fast feedback loops. AI amplifies both good and bad practices indiscriminately; poor fundamentals become worse with AI.
- Build an agentic delivery platform applying platform thinking: standardized channels (IDE, terminal, dev portal), reusable agentic capabilities, static context (coding guidelines, reference architectures), dynamic context (domain knowledge packs), and control plane governance for token spend and security guardrails.
- Measure AI productivity across three dimensions—human attitudes (developer satisfaction, debugging ease), system behavior (build time, test runtime, MTTR), and activity metrics (velocity, coverage)—not single metrics like LOC or code churn alone.
- DORA 2025 shows teams with quality internal platforms and value stream mapping achieve large increases in AI adoption; rework rate and deployment frequency are leading indicators of successful AI scaling, not code generation speed.
- Get people aligned through four levers: basic AI literacy for all, champions and communities of practice, use case-driven adoption (not tool-driven), and an organizational AI playbook capturing what works and what doesn't.
TL;DW
- Imbalanced AI adoption—enhancing only developers while ignoring designers, product managers, security—creates upstream and downstream bottlenecks; Theory of Constraints shows optimizing one part of SDLC without cross-functional support actually slows overall delivery.
- AI coding agents expose the "lethal trifecta": access to sensitive information, susceptibility to malicious input via context poisoning, and ability to exfiltrate data—making your development environment a new attack surface.
- GitClear 2023-2024 data shows code refactoring declining, code churn rising, and code added accelerating with AI—indicating increased technical debt, rework, and debugging burden despite higher code generation velocity.
- Token spend scales uncontrollably: power users burning $20/developer/day ($400+/month) versus initial $20/month plans; rogue AI usage and unmonitored model deployments create compliance and cost visibility crises.
- Value stream mapping—identifying friction points across your entire path-to-production from ideation to production maintenance—is the only way to justify ROI and adopt AI strategically rather than chasing shiny tools.
- Effective coding agents require mature engineering practices: strong CI/CD, comprehensive test harness, fast feedback loops. AI amplifies both good and bad practices indiscriminately; poor fundamentals become worse with AI.
- Build an agentic delivery platform applying platform thinking: standardized channels (IDE, terminal, dev portal), reusable agentic capabilities, static context (coding guidelines, reference architectures), dynamic context (domain knowledge packs), and control plane governance for token spend and security guardrails.
- Measure AI productivity across three dimensions—human attitudes (developer satisfaction, debugging ease), system behavior (build time, test runtime, MTTR), and activity metrics (velocity, coverage)—not single metrics like LOC or code churn alone.
- DORA 2025 shows teams with quality internal platforms and value stream mapping achieve large increases in AI adoption; rework rate and deployment frequency are leading indicators of successful AI scaling, not code generation speed.
- Get people aligned through four levers: basic AI literacy for all, champions and communities of practice, use case-driven adoption (not tool-driven), and an organizational AI playbook capturing what works and what doesn't.
Vanya Sharma, ThoughtWorks India head of tech, identifies three compounding risks: workflow fragmentation that accelerates individual output without system throughput, a 'lethal trifecta' security exposure in agentic coding tools, and rising code churn despite faster generation. Proposes value stream mapping and platform-layer governance as remedies.