Record a consistent sample before the build and repeat it after launch. Separate time doing the work from time waiting. Track corrections and missing information so faster completion does not hide lower quality.
Define the work and the observation window
Name the workflow, its trigger, completion condition, responsible owner, and included applications. Choose a period that represents normal work and note unusual conditions.
A request must have the same start and finish definition in both samples. Compare similar work types and disclose any change in volume, staffing, scope, or seasonal demand.
Record the baseline
For each request, capture the start, finish, active minutes, waiting time, corrections, missing information, and final state. Record source evidence instead of relying only on estimates.
Summarize the sample size, typical task time, total correction effort, and the number of requests missing an owner or completion evidence. Keep the raw sample available to the people reviewing the result.
Agree on the comparison
Specify the target measure, acceptance criteria, observation period after launch, and who signs off. A system can pass technical checks while the operating result still needs improvement.
Use the worksheet headings below in your own spreadsheet. Do not enter private business or customer records into this public page.
| Record | Measure |
|---|---|
| Request ID and work type | Compare similar tasks |
| Start, finish, and owner | Completion time and responsibility |
| Active minutes and waiting time | Effort versus delay |
| Corrections and missing information | Rework and completeness |
| Completion evidence and exception | Verified result and unresolved work |