A flow calculation needs the same population and time boundary
A fictional service team records an average of forty requests in progress and completes ten requests per working day over a stable observation interval. Its agreed boundary runs from accepted request to completed delivery. Another team reports only active handling minutes and proposes comparing that number directly with the first team’s implied elapsed lead time. The supplied figures are a simplified average model, not a promise about each request or an official capacity assessment. This written exercise changes no staffing or queue policy. The learner should use consistent population, units and flow boundaries, identify the difference between average elapsed time and active work, and explain why the observed averages do not by themselves prove a particular cause of delay.
1. What average lead time follows in this supplied stable model?
Read the worked answer
Little’s Law gives average WIP divided by throughput:40requests/(10requests per working day)=4working days within the defined boundary. It is not a guaranteed duration for each individual request.
2. Why is active handling time not directly interchangeable?
Read the worked answer
It excludes relevant waiting that belongs to the defined elapsed boundary. Establish consistent populations, start/finish events, units and observation conditions before comparing or drawing an improvement conclusion.