Checking, approving and confirming an order takes just twenty minutes of work in total, yet the customer waits days for a response. This does not necessarily mean employees are working slowly. Often, the task is sitting idle: in a shared inbox, on an approver’s list or between two departments, with no clearly assigned owner for the next step.
One important insight in business process optimization is that working faster and achieving shorter turnaround times are not the same thing. Reducing waiting times is primarily about improving the connections between steps. When fine-tuning processes that have already been mapped, it is therefore essential to examine handoff points, queues and decision rules.
1. Examine total turnaround time, not just working time
Processing time shows how much time is actually spent working on a case. Turnaround time is the time elapsed between a defined start and end point. The latter also includes waiting: even when no one is working on a task, the customer’s clock is still ticking.
Let’s look at an illustrative example that is not based on measured company data. Active processing time for a simple order breaks down as follows:
- The order administrator spends five minutes checking the order details.
- Finance spends five minutes reviewing the payment terms.
- The warehouse spends five minutes checking whether the order can be fulfilled.
- The order administrator spends five minutes preparing the confirmation.
If Finance does not pick up the case until the next day, and the warehouse is notified only after Finance responds, twenty minutes of work can stretch over several days. Making the initial check one minute faster will do little to help.
First, identify where the case is stalled and why. Insufficient capacity, missing data, unclear responsibilities and deliberately delayed batch processing each require a different solution.
2. Make task handoffs a clear change of status
“I sent it by email” does not necessarily mean a task has been handed over effectively. The recipient may be on leave, the deadline may be unclear or a required attachment may be missing. The sender considers their part complete, while the next step cannot even begin.
A well-designed handoff answers four questions:
- Who is next? Assign a clear owner or use rule-based task allocation, with cover arrangements in place.
- What do they need to do? The task and its expected outcome must be clear.
- What do they need to work with? Data and documents must be available and linked to the case.
- When must they take action? The deadline and how it is calculated must be known.
In the order example, completing the data check should trigger the next task. The order administrator should not have to work out separately who to notify. If mandatory data is missing, the case should not move forward as an order ready for processing. Instead, it should enter a separate status for collecting missing information, with its own assigned owner.
When designing processes with xFLOWer, defining the sequence of activities is therefore not enough: the handoff conditions must also be specified. A notification alone does not assign responsibility. When a task enters a shared list, it must also be clear who will pick it up and when.
3. Smaller batches can reduce time spent in queues
Many companies routinely forward orders once a day and handle approvals within a designated time window. This may be a convenient way to organize work, but it builds waiting time into the process. A case arriving after a processing cycle sits idle until the next one, even if all the necessary data is available.
Smaller batches mean waiting for fewer cases to accumulate. There is no need to start processing every order individually straight away: a first step could be to try smaller, more frequent processing cycles. Urgent and standard cases can follow different routes, provided the priority criteria are clear.
However, the change may also come at a cost. If each check requires costly preparation, excessively small batches can increase the workload. And if checking capacity consistently falls short of incoming work, forwarding cases more frequently will not eliminate the bottleneck on its own.
Batch size should be set by considering both turnaround time and the effort involved. The goal is not constant interruption, but the elimination of unnecessary waiting.
4. Run genuinely independent tasks in parallel
Process diagrams often place tasks in sequence even when there is no real dependency between them. For an order, for example, reviewing payment terms and checking stock availability can often start from the same verified dataset.
With sequential execution, waiting in one branch delays the start of the other. With parallel execution, both checks can progress at the same time, and the process moves forward once all the required results are available. This can reduce elapsed time without necessarily changing the total amount of work involved.
Checking and execution are not the same
Checking stock is not the same as reserving it, just as assessing whether goods can be shipped does not mean dispatching them. For an order that may be rejected, starting an irreversible or costly operation before the financial decision can be risky.
- Only start tasks together if they do not require each other's results.
- Define which results are required to proceed.
- Establish how to handle rejections, order changes and conflicting results.
Reducing waiting times here does not mean removing controls. The aim is to ensure that necessary checks do not wait for one another simply out of habit.
5. Escalation also requires decision-making authority
A deadline alone will not move a case forward. That requires a predefined intervention. Escalation determines who is notified when a deadline is approaching or has been missed, and what action they can take.
It is useful to distinguish between three separate events:
- Reminder: the person responsible is notified of the approaching deadline.
- Operational intervention: the coordinator or deputy can reassign the task, change its priority or clarify the obstacle.
- Management escalation: the capacity or business conflict is referred to a manager with decision-making authority.
At each level, the trigger condition, recipient and expected action must be documented. “Send another email” is not enough if no one has the authority to reorganize the work. Too many alerts, however, create notification noise, so the level of escalation should match the case's risk and agreed deadline.
Calculating deadlines is also a business rule: do we use working hours or calendar hours? What happens on weekends, when someone is covering for a colleague, or while waiting for the customer? Even when an internal deadline is justifiably paused, the total customer-facing turnaround time should remain visible.
6. Measure whether cases really spend less time waiting
Establish a baseline before making changes. At a minimum, you need timestamps for receipt, readiness for processing, task start and closure. Total turnaround time alone does not reveal which handoff point caused the delay.
A few well-defined metrics are enough to track the impact:
- Total turnaround time: from receipt to confirmation.
- Handoff waiting time: from the moment the next task is ready for processing until work actually begins.
- Overdue open cases: reveal the outstanding backlog.
- Requests for missing information and rework: indicate whether faster processing is compromising quality.
Alongside the average, it is worth monitoring the median and trends in slower cases. When making comparisons, account for case types, incoming volumes and available capacity. Start by testing on a clearly defined subset of orders; this makes it easier to identify side effects and make adjustments if needed.
In summary: a twenty-minute task translates into a case with a shorter turnaround time when the next person responsible is clearly identified, we avoid waiting for unnecessarily large batches, independent checks run in parallel, and delays trigger meaningful intervention.
Where do orders wait in your process? Discuss fine-tuning your existing operations with the xFLOWer team: select a critical handoff point and define the rules, responsibilities and measurement approach for improving it.
This article is part of our comprehensive guide: Business Process Optimization: A Complete Guide to Improving Existing Workflows
xFLOWer.ai
Design the process behind this article – for free!
AI reads the processes hidden in this article; open any of them in xFLOWer.ai with one click.
