All insights
EngineeringProcess5 min read
Why your CI is the bottleneck
Slow CI quietly compresses your team's whole iteration loop. Most engineering organizations under-invest in it by an order of magnitude.
Your team's iteration cadence is bounded by how long CI takes. If CI takes 20 minutes, that's the smallest unit of work anyone can actually verify quickly. Everything else is paced to that — code review, deployment, hotfix cycle, on-call response.
Why most teams under-invest
CI is plumbing. Improving it doesn't ship features. The CI team usually has no clear customer with budget authority. Engineers complain about it constantly but nobody schedules the work to fix it. Six months later, CI takes 45 minutes and the team is paying for it in lost iteration speed they don't even notice anymore.
What to do
- Track CI time as a P0 metric, with leadership visibility.
- Budget engineering time for CI improvements every quarter.
- Make the goal explicit (e.g., 5 minutes p50, 10 p95) and defend it.
- When CI slips past goal, the next sprint includes fixing it — not next quarter.
CI speed is the metabolism of your engineering team. Most teams don't measure it.