Google Research Finds AI Speeds Work but Halts Junior Judgment Growth
A 90-day field trial conducted by Google Research and the National Bureau of Economic Research reveals that while AI accelerates task output, it fails to improve unassisted junior judgment. Senior practitioners gained substantial unassisted skill, while juniors stagnated.

Why it matters
Tech leads must enforce unassisted code reviews and debugging drills to prevent junior engineers from falling into passive AI-dependency traps.
TL;DR
- 01AI assistance boosts immediate output quality by 0.38 SD but acts as an exoskeleton rather than a learning vehicle for juniors.
- 02Senior professionals successfully internalize mental models from AI, outperforming unassisted controls by 0.45 SD.
- 03Overreliance on AI promotes a 'diagnose-without-execute' mindset, preventing novices from learning hands-on structural refactoring.
Key facts
- Study Cohort
- 133 patent attorneys across 11 legal firms
- Assisted Quality Gain
- +0.34 SD at 10 days; +0.38 SD at 90 days
- Drafting Speed Gain
- 18 minutes faster for juniors (control baseline 124 minutes)
- Unassisted Senior Gain
- +0.45 SD outperformance over control group
- Unassisted Junior Gain
- 0 SD average improvement (bifurcated score distribution)
The 90-Day Field Experiment on Assisted Work
Published in collaboration with the National Bureau of Economic Research, researchers David Autor and Tanya Rodchenko examined 133 professionals across 11 firms over 90 days using an unreleased Google Labs tool (now part of Gemini Notebook). Assisted drafting tasks demonstrated persistent speed and consistency improvements: drafting scores rose by 0.34 standard deviations at 10 days and 0.38 standard deviations at 90 days. Junior practitioners cut drafting time by 18 minutes compared to the 124-minute control baseline.
The Unassisted Redlining Collapse in Junior Judgment
At 90 days, participants performed an unassisted redlining task without AI support, graded across enforceability, accuracy, strategic ambiguity, completeness, and clarity. While seniors demonstrated a 0.45 standard deviation gain over control seniors, juniors exhibited no average skill gain. Instead, junior distribution bifurcated: the volume of very low scores increased, mediocre scores dropped, and excellent scores remained flat.
The Diagnose-Without-Execute Trap
Qualitative analysis identified distinct junior failure modes. Juniors spent disproportionate time sequentially editing low-stakes introductory sections and swapping surface synonyms. Crucially, when detecting serious errors, juniors adopted a 'diagnose-without-execute' approach—leaving advisory comments rather than implementing structural corrections, a fundamental deficit that 90 days of continuous AI rewriting failed to remediate.
What to do today
- Require junior developers to perform code reviews and root-cause bug isolation without LLM tools.
- Audit team engineering workflows to catch diagnose-without-execute patterns during PR reviews.