---
title: "Faster Developers Don’t Make a Faster Team"
description: "Discovery calls with engineering organizations reveal that widespread use of AI agents has not translated into faster team delivery. Individual developers gain speed, but three structural bottlenecks stall team-level progress. Teams lack shared prompts, rules, and configurations, forcing every agent to start cold and re-explain conventions. Code review processes designed for human-paced change become the new constraint, with some teams measuring increased pull request time. Automating routine work like library upgrades creates its own operational burden, as teams struggle to maintain and distribute automation pipelines across projects. Without shared infrastructure, coordination breaks down and the gap between proficient users and the rest widens."
---

# Faster Developers Don’t Make a Faster Team

[Jetbrains](https://yomu.fyi/company/jetbrains) · Gleb Malkov · Oct 7, 2026

**Type:** Problem & solution

## Summary

Discovery calls with engineering organizations reveal that widespread use of AI agents has not translated into faster team delivery. Individual developers gain speed, but three structural bottlenecks stall team-level progress. Teams lack shared prompts, rules, and configurations, forcing every agent to start cold and re-explain conventions. Code review processes designed for human-paced change become the new constraint, with some teams measuring increased pull request time. Automating routine work like library upgrades creates its own operational burden, as teams struggle to maintain and distribute automation pipelines across projects. Without shared infrastructure, coordination breaks down and the gap between proficient users and the rest widens.

## Context

Engineering organizations from small agencies to large consultancies report that while individual developers become much faster using AI agents, team-level delivery does not improve proportionally. Three recurring bottlenecks are identified: shared agent knowledge is absent or fragile, code review processes become the new bottleneck, and operational maintenance of automations creates additional burden. These problems persist even when every developer has access to capable agents.

## Takeaways

- Knowledge about effective agent usage is not shared systematically; it spreads through personal configs, Slack threads, and morning conversations rather than team standards.
- Code review processes become the bottleneck when agents produce code faster than review cycles, and low confidence in output quality can actually increase pull request time.
- Automating tasks like library upgrades or documentation updates creates ongoing maintenance work for pipelines, and distributing updates across multiple projects remains unsolved.

## FAQ

### Why doesn't faster implementation mean faster team delivery?

Review processes designed for human-paced change become the bottleneck when agents produce code much faster. Teams report that pull request time can actually increase because low confidence in AI output leads human reviewers to check everything more thoroughly.

### What prevents teams from scaling individual agent productivity?

Team-level gains stall because knowledge about how to work with agents lives in personal configs, Slack threads, and wikis rather than shared standards. No systematic sharing process exists, so output quality depends on who is prompting rather than team decisions.

### What operational problems arise from automating with agents?

Teams that build automated pipelines (e.g., agents in Docker containers reacting to webhooks) face ongoing maintenance costs. Distributing updates across multiple projects becomes difficult, and without dedicated infrastructure or clear ownership, the automation itself becomes a new operational burden.

**Tags:** [AI Agents](https://yomu.fyi/topic/ai-agents), [Code Review](https://yomu.fyi/topic/code-review), [Developer Experience](https://yomu.fyi/topic/developer-experience), [Engineering Management](https://yomu.fyi/topic/engineering-management), [JetBrains](https://yomu.fyi/topic/jetbrains)

- Source: [Jetbrains](https://blog.jetbrains.com/air/2026/10/faster-developers-don-t-make-a-faster-team)
- Source URL: https://blog.jetbrains.com/air/2026/10/faster-developers-don-t-make-a-faster-team
- Ingested by Yomu: 2026-10-07T15:00:10.021Z

[Read original post](https://blog.jetbrains.com/air/2026/10/faster-developers-don-t-make-a-faster-team)