Timedora

Assessing Process Performance

How to define a process performance gap and measure results against customer needs using clear, consistent baseline data.

Define the Gap and Measure What Matters

Define the gap before seeking causes

First specify the process boundary, who its customer is, what output is expected, and how actual performance falls short. A useful problem statement says what is happening, where and when it happens, and how large the gap is—without assuming why. For example: “During April, 18% of complete applications took more than five business days to approve; the target is under 5%.” This describes a measurable gap, not its cause.

Choose and define relevant measures

Select measures that reflect customer requirements and intended results. is elapsed time, including waiting; is the time for a particular step or repeated unit. Other useful measures include throughput (completed outputs per time period), WIP (started but unfinished work), first-pass yield (correct outputs completed without rework), defect or error rate (outputs failing a defined requirement), and on-time completion (outputs finished by the agreed deadline).

Define each measure’s unit, start and end points, data source, collection interval, and denominator. For a rate or proportion, the denominator specifies which cases are counted. Before changing the process, collect a using these definitions. Compare results over time and across meaningful categories, such as work type, shift, or location. Overall averages can hide variation; one application type, for instance, may account for most delays. Use patterns to guide investigation, not to presume a cause.

Judge changes by end-to-end results. Making one step faster is not a genuine improvement if it reduces quality, safety, or customer value elsewhere in the process.

  • : Work that has started but is not yet complete.