The slowest step can hold up the whole system
The slowest step can hold up the whole system
At a company, three people prepare proposals quickly, but every proposal has to be approved by one overworked colleague. Management asks the proposal writers to work even faster. The number of documents waiting for approval grows, and customers don’t get their results any sooner. Work has sped up where the system didn’t have a problem. The efficiency of a whole process is often limited by a specific bottleneck.
On your process map, look for where tasks pile up, wait the longest, or often come back for corrections. Find out whether the cause is insufficient capacity, unclear rules, missing information, or an unnecessary check. Adding another person isn’t always the best solution. It may help to separate routine cases from exceptions, or to prepare complete information before approval.
But don’t pressure the approver to put speed ahead of safety. If a check is important for legal, financial, or safety reasons, any simplification must preserve its purpose. First, try reducing the number of incomplete submissions. If faulty tasks stop coming back, capacity may be freed up without anyone working longer hours.
When something is delayed next time, don’t just ask, “Who’s working slowly?” Ask, “Where does the result have to wait the longest, and why?” Look at the total time from the request to completion. That’s the difference between putting pressure on individuals and improving the flow of work for everyone.