A business process can consistently produce the expected result and still take longer, require more effort, and consume more resources than necessary.
Customer orders get fulfilled. Invoices get processed. Service requests get completed.
But how efficiently does the work move from beginning to completion?
That’s a question business leaders should be asking.
Completing the work successfully doesn’t necessarily mean the process is performing efficiently.
Introducing the Measuring What Matters Series
Over the coming weeks, Process Clarity Insights™ will examine eight practical measurements that help business leaders understand how their processes actually perform.
We’ll explore:
- Total Process Cycle Time — How long does the entire process take?
- Waiting Time Between Departments — How long does work wait between activities?
- Handoff Readiness Rate — How often does work arrive complete and ready for processing?
- Return-for-Correction Rate — How frequently is work returned for correction?
- Clarification Request Frequency — How often must employees request additional information?
- Total Process Rework — How much work must be repeated or corrected?
- Customer Response or Fulfillment Time — How long do customers wait for the intended result?
- Total Effort Required — How much employee time does the process consume?
Not every business process requires all eight measurements. The objective is to select measures that provide meaningful insight into the performance of a particular workflow.
Each article will examine one or two related measurements, explain what they reveal, and identify questions leaders should consider when evaluating their processes.
Our guiding principle: Don’t measure only how much work gets done. Measure what it takes to get the work done.
Measurement 1: Total Process Cycle Time
Imagine a customer order that requires only 45 minutes of actual processing time.
Yet three days pass between receiving the order and completing it.
The order is fulfilled successfully.
But why did a process requiring less than an hour of actual work take three days?
This is where measuring total process cycle time becomes valuable.
Total process cycle time measures the elapsed time between the beginning and completion of a process.
It includes time spent performing activities and time spent waiting between them.
How to Calculate Total Process Cycle Time
The calculation is straightforward:
Total Process Cycle Time = Process Completion Time − Process Start Time
For example:
- Customer order received: Monday, 9:00 AM
- Customer order fulfilled: Thursday, 9:00 AM
- Total process cycle time: 72 elapsed hours
- Actual employee processing time: 45 minutes
The process took 72 hours to complete, even though employees spent only 45 minutes actively working on the order.
That difference deserves investigation.
It doesn’t automatically mean the remaining time was wasted. Some waiting may be necessary because of scheduling, customer requirements, or other legitimate constraints.
But without measuring the entire process, management may never recognize how much time passes between activities.
Where Does the Time Go?
Consider what might happen after Sales receives a customer order.
Sales completes the intake and forwards the information to Operations.
The order waits in a queue.
Operations discovers that additional information is needed.
The request returns to Sales for clarification.
Once the information is received, Operations schedules the work.
The order waits again before fulfillment begins.
None of these activities necessarily requires a significant amount of employee processing time.
But collectively, they can extend the total time required to complete the process.
The delay may not be caused by how slowly employees perform their activities. It may be caused by what happens between those activities.
That’s an important distinction.
What Should Business Leaders Investigate?
When total process cycle time is longer than expected, leaders should examine the actual workflow.
Where does work spend the most time waiting?
Are requests arriving with complete information?
Do activities require unnecessary approvals?
Does work move backward for correction?
Are responsibilities and handoffs clearly defined?
Are there legitimate scheduling or operational constraints that explain some of the elapsed time?
These questions help identify where improvement opportunities may exist.
The objective isn’t simply to push employees to work faster.
It’s to understand why the process takes as long as it does.
Process Mapping Makes the Delays Visible
A validated process map helps leaders understand the activities, decisions, handoffs, and alternate paths involved in completing the work.
It also helps identify where waiting occurs and where additional information or corrections may be required.
This is why it’s important to involve the people who perform the work, feed the process, and are impacted by it.
Their perspectives help establish what actually happens as work moves through the organization.
Once the process is understood, leaders can determine where cycle time should be measured and which conditions contribute to delays.
Measurement then provides a baseline for evaluating improvements.
The Real Opportunity
A process that requires 45 minutes of actual work but takes three days to complete isn’t necessarily a poorly performing process.
But the difference between processing time and total elapsed time should raise questions.
Some delays may be necessary.
Others may result from incomplete information, unclear handoffs, unnecessary approvals, or avoidable waiting.
Until those conditions are understood, improvement efforts may focus on making individual employees faster rather than making the overall process more efficient.
Don’t assume that employees need to work faster simply because the process takes too long.
First, understand where the time goes.
Because improving process performance begins with understanding how the work actually moves from start to finish.
Next in the Measuring What Matters series: Waiting Time Between Departments — examining where work sits idle and how those delays affect overall process performance.
Business Process Mapping: The Foundation of Operational Excellence
Process Mapping vs SOPs: What Growing Companies Get Wrong