7 Metrics to Accelerate Delivery without Damaging Culture
summary
Data from ~900k analyzed PRs shows the bottleneck is review flow not coding: PRs sit idle (many >24–48h) and delays compound, while small PRs get merged fast. Tools built include a Slack fast lane notifier for tiny changes (<=5 lines, one file), a Worker B Chrome extension that posts PRs with estimated review time and signals when review starts, and a repo YAML to route PRs (auto-merge docs, multi-review for large diffs). Recommendation: keep PRs <150 changes and surface pickup/merge signals for faster delivery.
AI-written summary · about
chapters (6)
- 0:00Start
- 4:18Cycle Time
- 8:20Transition Time
- 9:48Distraction Time
- 15:00What Is the Priority
- 26:46Fastlane
related talks
29mBreaking the PR Review Bottleneck
06m50 Haunting Shades of PR Dark Matter
38mHow to Optimize Non-Coding Time
57mAsync Code Reviews Are Choking Your Company’s Throughput
15mHow to Merge Your PR in 10 Seconds? Have You Tried Mob Code Review?
56mAsync Code Reviews Are Choking Your Throughput
14m50 shades of PR dark matter
26mA State of Continuous Merge: The Secret to More Productive Dev Teams