Pull requests slow teams, catch few bugs
PR workflows are a trust-mismatch mechanism borrowed from open source; research shows less than 15% of review comments find bugs, while code waits 86-99% of lead time in queues.
May 27, 2026
Summary
Most teams justify PRs as bug-catching, but academic research and DORA data show they're expensive waiting mechanisms that fragment team velocity. Trunk-based development with TDD correlates with 50% faster delivery.
Why it matters
Most teams justify PRs as bug-catching, but academic research and DORA data show they're expensive waiting mechanisms that fragment team velocity. Trunk-based development with TDD correlates with 50% faster delivery.
Implementation verdict
Replace blocking async PRs with continuous integration + TDD + synchronous review during development (pairing/Ship-Show-Ask). Requires trust in team competence and mature test automation. Gradual transition viable: optimize PRs → Ship/Show/Ask → trunk-based. Worth starting now if your team ships multiple times daily.
Sources
- 1.Less than 15% of review comments relate directly to bugs
- 2.code spends 86-99% of its lead time waiting
- 3.DORA research across 36,000+ professionals shows trunk-based development correlates with dramatically higher software delivery performance
- 4.Code Reviews Do Not Find Bugs: How the Current Code Review Best Practice Slows Us Down
- 5.Pull requests are designed to make it easier to accept contributions from the outside world, from untrusted people we do not know about
Dev Signal
Get briefs like this in your inbox — free, 3x a week.
100+ sources compressed into one 4-minute read. Ranked, cited, implementation-ready.