Cycle Time & Bottleneck Analysis

Overview

Cycle time is the time from when a developer makes their first commit on a change to when that pull request is merged. It is one of the most actionable levers for improving engineering delivery speed and maps closely to DORA's Lead Time for Changes metric.

Koalr's Cycle Time page breaks the full cycle into four stages, identifies which stage is the bottleneck, and shows trends at the org, team, and individual level.

Cycle time stages

First commit → PR opened → First review → Approved → Merged → Deployed
|←— coding time —→|←— pickup time —→|←— review time →|←— merge time →|←— deploy time →|

Stage	Definition	Healthy benchmark
Coding time	First commit to PR opened	< 2 days
Pickup time	PR opened to first review comment	< 4 hours
Review time	First comment to PR approval	< 8 hours
Deploy time	Merge to production deployment	< 1 hour
Total cycle time	First commit to PR merge	< 1 day (elite)

DORA classification

Tier	Lead time for changes
Elite	< 1 hour
High	1 day – 1 week
Medium	1 week – 1 month
Low	> 1 month

Koalr displays your org's current DORA tier alongside cycle time so you can see where you fall relative to industry benchmarks.

Dashboard sections

Organization summary KPIs

• Median cycle time — P50 across all PRs in the selected period
• P75 cycle time — 75th percentile (accounts for outliers better than average)
• DORA tier — Elite / High / Medium / Low based on median lead time
• Bottleneck stage — the stage consuming the largest share of total cycle time

Stage breakdown chart

Stacked bar chart showing the relative time spent in each stage:

• Identifies whether your bottleneck is in coding, review pickup, review depth, or deployment pipeline
• Filterable by team, repo, or date range

Cycle time trend

Line chart of median cycle time over the past 12 weeks. Allows you to correlate changes (team restructuring, new processes, CI improvements) with cycle time movement.

PR-level table

Every merged PR in the period with:

• Total cycle time
• Time in each stage
• Author, reviewer, repo
• Sort by total time or any individual stage

Bottleneck analysis

The Bottleneck Analysis section highlights which specific stage is inflating your cycle time most, with:

• The top 5 PRs contributing to each stage's inflation
• Root cause patterns (e.g., "review pickup > 8 hours" correlated with specific reviewers being overloaded)
• Team-level bottleneck comparison

Pickup time deep dive

Slow pickup time (PR opened → first review) is the most common bottleneck. Koalr shows:

• Average pickup time by reviewer — identify which reviewers are slowest to engage
• Pickup time by day of week — PRs opened on Fridays typically wait longest
• PRs without any review after 24h — stale PR alert

Review time deep dive

Long review time (first comment → approval) can indicate:

• Large PR size — bigger PRs take longer to review; see PR Size Distribution
• Reviewer overload — reviewers are spread across too many repos
• Context mismatch — reviewers unfamiliar with the changed files (see CODEOWNERS in GitHub integration)
• Back-and-forth — high comment count relative to PR size signals misalignment or lack of upfront design

Filtering

Use the controls at the top of the page to filter by:

• Date range — 7d / 14d / 30d / 90d (or custom)
• Team — compare teams against each other
• Repository — isolate specific repos
• PR size — filter by XS / S / M / L / XL buckets

Reducing cycle time

1. Reduce PR size — the single highest-leverage action; set team size targets (PR Size Distribution)
2. Enforce WIP limits — in-flight PRs compete for reviewer attention (WIP Limits)
3. Designate review windows — two daily review blocks reduce pickup time without constant interruptions
4. Automate deployment — manual deployment steps inflate deploy time; move to CD
5. Reduce context switching — fragmented developers review more slowly (Context Switching)

Relationship to other metrics

• DORA Metrics — cycle time is DORA's Lead Time for Changes (DORA Metrics)
• PR Size Distribution — smaller PRs have shorter cycle times (PR Size Distribution)
• WIP Limits — WIP accumulation slows review pickup (WIP Limits)
• Deploy Risk — high-risk PRs spend longer in review, inflating cycle time (Deploy Risk)