Little’s Law is one of the most powerful and universal formulas in operations and queueing systems. It links three core performance measures: average inventory (or number in system), throughput rate, and waiting time. This page explains how to apply Little’s Law correctly across service systems, manufacturing, supply chains, and project workflows, with multiple numerical examples.

1. The Formula

Little’s Law states:

\[ L = \lambda W \]

• \(L\) = average number of items/customers in the system
• \(\lambda\) = average throughput rate
• \(W\) = average time an item/customer spends in the system

It applies to any stable system where average inflow equals average outflow.

2. When Little’s Law Applies

Little’s Law works when:

• The system is stable (long‑run inflow = outflow).
• Measurements are long‑run averages.
• Units are consistent (e.g., customers/hour and hours).

It does not require any assumptions about distributions, arrival patterns, or service times.

3. How to Use Little’s Law

3.1 Solve for average time in system

\[ W = \frac{L}{\lambda} \]

3.2 Solve for average inventory or number in system

\[ L = \lambda W \]

3.3 Solve for throughput rate

\[ \lambda = \frac{L}{W} \]

4. Numerical Examples

Example 1 — Call Center

• Average calls in system = 12
• Throughput = 4 calls per minute

\[ W = \frac{12}{4} = 3 \text{ minutes} \]

Example 2 — Manufacturing Line

• Throughput = 200 units/day
• Average flow time = 4 days

\[ L = 200 \cdot 4 = 800 \text{ units of WIP} \]

Example 3 — Hospital Emergency Department

• Average patients in system = 45
• Average time in system = 6 hours

\[ \lambda = \frac{45}{6} = 7.5 \text{ patients/hour} \]

5. Practical Uses

• Estimating waiting times without simulation.
• Calculating WIP in manufacturing systems.
• Determining staffing needs in service operations.
• Evaluating bottlenecks and flow constraints.
• Setting inventory and throughput targets.

6. Common Mistakes

• Mixing units (e.g., customers/hour with minutes).
• Applying Little’s Law to unstable systems.
• Using short‑term snapshots instead of long‑run averages.