Cycle Time vs Throughput

Two flow metrics from queueing theory, applied to delivery teams. Cycle time measures how long each item takes. Throughput measures how many items finish per period. Linked by Little's Law.

Last updated: 2026-04-01

Overview

Cycle Time

Per Item

The time from when work starts on an item to when it's done. Measured in days, per-item. Cycle time tells you how long a customer or stakeholder waits once work begins.

Best for tracking individual flow efficiency, identifying bottlenecks, and predicting how long a single piece of work will take.

Throughput

Per Period

The number of items completed per period: per week, per sprint, per month. Throughput tells you how much the system delivers. Higher is better, all else equal.

Best for forecasting how much a team can deliver in a quarter and for spotting capacity changes.

Formula comparison

Cycle Time

Cycle time = Time completed - Time started

Average cycle time gives the typical wait. The 85th percentile gives a realistic upper bound for forecasts.

Throughput

Throughput = Number of items completed in a period

Connected to cycle time via Little's Law: Average WIP = Throughput x Cycle Time. Reducing WIP without reducing throughput necessarily reduces cycle time.

Side-by-side comparison

Criteria	Cycle Time	Throughput
Unit	Days per item	Items per period
Question it answers	How long will this take?	How much can we deliver?
Best for	Per-item predictability	Capacity forecasting
Connected by	Little's Law	Little's Law
Affected by WIP	Yes. More WIP, longer cycle time	Indirectly. Throughput caps at the slowest stage
Healthy benchmark	85th percentile under 2 weeks for software features	Trending stable or up at constant scope
Common pitfall	Reporting only the average	Splitting items to inflate the count
Pairs with	Lead time, WIP	Velocity, cumulative flow

When to use each

Choose Cycle Time when

You're optimizing for predictability per item
A stakeholder asks "how long will this one take"
You suspect WIP is hurting flow
You want to identify which stages of work cause the most wait
You're improving customer delivery promises

Choose Throughput when

You're forecasting quarterly capacity
You're sizing how much a new initiative will displace
You want to know if the team is delivering more or less over time
You're comparing capacity across teams
You're modeling a release date based on items remaining

Pros and cons

Cycle Time

Pros

Per-item, so it answers "how long" for any specific work
Surfaces bottlenecks in specific stages
Pairs with cumulative flow diagrams to show queue buildup

Cons

Distribution matters. Reporting only the average hides outliers
Sensitive to scope. A vague item with a long cycle time isn't always a flow problem
Doesn't tell you total team capacity

Throughput

Pros

Easy to count. Items done per week
Stable for forecasting if the team and scope are stable
Pairs cleanly with story-point velocity if you're using it

Cons

Can be gamed by splitting items smaller without finishing more value
Doesn't tell you per-item wait
A high throughput with high cycle time means a backlog is piling up

Try both calculators

Score your own data with both frameworks. Compare results and pick the one that fits your team.

Cycle Time Calculator Velocity Calculator

Frequently asked questions

What's the difference between cycle time and lead time?

Lead time starts when a request is made. Cycle time starts when work begins on it. Lead time includes the queue. Cycle time only includes active work. For customer-facing promises, lead time is what matters. For team flow, cycle time is more actionable.

Should I track both, or just one?

Both. They constrain each other through Little's Law. Tracking only throughput hides bottlenecks. Tracking only cycle time hides whether the team is delivering volume. The honest dashboard has both, plus WIP.

What's a good cycle time?

Depends on the type of work. For software, 85th percentile cycle time under 2 weeks is healthy for feature work. Bug fixes should be measured in days, not weeks. The point isn't the absolute number. It's whether cycle time is stable or trending down with the same scope.

Does throughput equal velocity?

Roughly, but not exactly. Velocity is a story-point-based volume metric. Throughput is item-count-based. Both measure team output per period. Throughput is harder to game because every item counts as 1, regardless of estimated points.

How does WIP affect cycle time?

Directly, through Little's Law. If you double the WIP without changing throughput, you double the average cycle time. This is why kanban systems use explicit WIP limits. The math is unavoidable: more work in flight means longer waits.

Back to calculators