# Individual Agent Adoption Does Not Become Team Capability by Aggregation ## Claim Giving each developer an agent doesn't create organizational capability when prompting, review, and learning remain private individual practices. <!-- atomicity: 1 idea ✓ --> ## Scope & conditions - Applies to team rollouts measured through licenses, usage, or agent-generated pull requests. - Team capability requires shared review, reusable practices, and outcome measures. - Individual experimentation can precede shared practice, but it is not evidence that the transition occurred. ## Evidence [[3. Resources/Readwise/Articles/AI-coding Agents Kill Team Collaboration]] reports concentrated participation and self-review across 25,264 agent-generated pull requests, with only one in eight workflows involving multiple humans. ## Links - [[Code Review Is a Human Knowledge-Transfer Ritual Not Just a Quality Gate]] — supports: self-review removes the shared learning channel. - [[AI Activity Metrics Measure Tool Throughput Not Engineering Value]] — applies-in: agent usage counts cannot establish team outcomes. - [[Human Review Capacity Sets the Agent WIP Limit]] — extends: private adoption also hides the review capacity needed at team scale. - [[3. Resources/MOCs/AI & the Future of Knowledge Work MOC]] — applies-in: the MOC lists this note under Synthesis additions (2026-08-11 — team capability).