Time-to-First-Move Distribution

Most backlog discussions focus on why work doesn't finish on time. This visual asks an earlier question: why does it take so long for work to start? The time between a ticket being created and someone first picking it up is invisible in most reports — but it is often where a large chunk of total cycle time is lost.

A long right tail in this distribution — many tickets waiting 3, 7, or more days before anyone acts on them — is a sign that the team's intake process is not working: tickets are created but not triaged, prioritized, or assigned quickly enough to keep the queue from growing.

What you can conclude

• A median first-move time above 48 hours suggests that ticket intake is not being triaged fast enough — issues are sitting unassigned longer than they should.
• A long tail (P90 significantly higher than the median) indicates that a subset of tickets are being systematically ignored — likely low-priority issues that never get picked up.
• A tight, left-skewed distribution (most tickets picked up within 24 hours) indicates a well-functioning backlog process with regular grooming and clear ownership.
• When the 168h+ bucket is close in size to the 0–24h bucket, the team has a bimodal intake pattern — some tickets are picked up immediately while others are systematically ignored. This is more concerning than a uniformly slow intake.

How this chart works

Histogram showing the distribution of time (in hours) from issue creation to first status transition out of To Do or Backlog. Buckets: 0–24h, 24–48h, 48–72h, 72–168h (3–7 days), 168h+ (7+ days). The 0–24h bucket is shown in teal (fast intake) and the 168h+ bucket in coral (problematic delay). Each bar is labeled with its percentage of total tickets. Median and P90 badges are shown above the chart.

When the 168h+ bucket exceeds 20% of all tickets, a coral long-tail alert banner is shown.

Use the project and date filters to compare intake responsiveness across teams or periods.