Slow Service Isn’t a Capacity Problem

More capacity is the wrong fix for poor customer satisfaction and broken process flow.

When Jack Hu joined the University of Georgia as Provost, he embarked on a traditional listening tour. The complaint he heard most consistently from the deans was not about budget or strategy, but about the sheer time it took to hire faculty. From securing final position approval to the new employee’s first day of work, the cycle time stretched into months on end. This delay was generating frustration across every college and school, becoming a significant drain on competitiveness.

Given my ERP background, Jack asked me for help. I tasked a student to diagram the process end-to-end, and the resulting diagram revealed 32 swimlanes of handoffs. Each handoff often resulted in defects, causing significant rework loops. The analysis revealed that activity time accounted for a tiny fraction of the overall queue time. Jack took action to eliminate handoffs, eliminate steps, and delegate authority to speed the process, with some success. In today’s Dispatch, I discuss what I believe is a near-universal truth: that most customer service problems are rooted in poor process flow, lack of structural discipline, and excessive queue time, not constrained capacity.

The big picture

The most fundamental threat to customer trust for any service unit is not poor quality work, it is the wait. Leaders across student affairs, facilities, business services, and IT must reckon with the same destructive outcome: a request is submitted, it languishes untouched for days in a queue, and when the task is finally completed, even if the actual activity took just two hours, the customer perceives a four-day failure. The distinction between activity time (when work is being done) and queue time (when work is sitting idle) is irrelevant; the delay entirely shapes perception.

This slow flow kills customer satisfaction. When work sits, it goes stale and quickly becomes frustrating, leading to dissatisfaction and possible escalation. This systemic friction is rarely due to incompetence or a lack of capacity; it is a direct result of organizational structure. In higher education, complex governance and a culture that normalizes caution have created processes where aging queues are accepted as the cost of doing business. Most institutions envision premium, high-quality service experiences, but their underlying internal processes are built on outdated, clunky methods. The work itself is sound, but the process does not flow, and that silence, those black holes of momentum, destroy credibility. The queue time is the killer.

Why Queue Time Destroys Institutional Trust

Waiting creates anxiety; it feels like a loss of control. If someone waits long enough, they may escalate the situation. Escalation feels like enforced accountability, but it is usually a sign that the underlying process has already failed. Once escalations become routine, politics takes over. Priorities shift based on noise, not business strategy.

This leads to a pernicious cycle:

• Misdiagnosis: Leaders attribute staff burnout and high queue times to a shortage of resources, focusing on hiring rather than fixing the system.

• The Constraint: Typically not labor, but an unpredictable flow from political queue jumping and the abandonment of first-in, first-out (FIFO) discipline.

• Blocked Capacity: A ten-person team may look overwhelmed. But if five of those ten people are blocked by unnecessary handoffs, unclear ownership, or persistent defects, the system is not short on capacity; it is short on clarity and discipline.

This structural lack of clarity creates an environment prone to friction, where the process is optimized for risk avoidance rather than efficient resolution. Without a single, clearly defined owner for the end-to-end process, every handoff creates the opportunity for defects. Staff default to caution: they wait for more data or seek unnecessary approvals. This creates a “no” oriented system that provides multiple safe opportunities for employees to pause, deflect responsibility, or simply queue the work. The system is designed for bureaucratic coverage, not for speed or customer value.

The Hidden Costs of Poor Flow

The main culprits creating these stagnant queues are organizational: excessive handoffs, non-value-adding activity, and the corrosive effect of queue jumping.

• The Proliferation of Handoffs: Every handoff requires another person to pick up, understand, and act, often within their own existing queue, resulting in another delay for the customer. As work traverses unit and cultural boundaries, defects often result. The drive for “thoroughness” can result in adding extra approvals, leading to more rework and slower service. The problem is rooted in fragmented ownership. As processes are divided across departments, no single unit owns the flow from beginning to end. The customer sees the entire journey; the units only see their lane. In that critical gap, quality degrades and institutional trust decays.

• Non-Value Work Creeps In: Universities are burdened by legacy processes inherited from a world of paper. When these old habits migrate to digital systems, they create significant friction. Many steps and approvals remain simply because their necessity was forgotten; removing them now feels risky. Leaders often respond to service breakdowns by adding more checks and forms, which increases the feeling of oversight but rarely improves outcomes. These additions increase handoffs and multiply the likelihood that work sits, untouched and aging, because the next person must act on a non-value-adding task.

• The Corruption of Queue Jumping: Queue jumping will create responsiveness for the politically powerful few at the expense of predictability for everyone else. When a system is full of exceptions driven by politics, everyone loses control of their workload. The queue loses integrity because first-in, first-out principles are abandoned. Once that happens, work priorities become unstable, leading to widespread demoralization among staff trying to run a solid, fair process.

The Discipline of Fixing Flow: Lean Six Sigma and DMAIC

Fixing this problem requires a sustained, analytical focus, often best approached using a framework like DMAIC: Define, Measure, Analyze, Improve, Control to eliminate wastes (lean the process) and reduce defects (applying six sigma principles).

• Define and Measure: Start by collecting data on customer satisfaction and measuring the queue. Service leaders must shift their dashboard metrics away from simple request counts and close rates to focus on:

  • Queue Aging: The average time a request sits before work begins.

  • Work in Progress (WIP): The total number of tasks actively in the system. Lower WIP usually correlates with faster cycle time and fewer defects.

  • Cycle Time: The total time from request to completion.

The data will be uncomfortable at first. It will show that most delays are structural, not capacity-related. They will show that teams need fewer tasks in flight and fewer handoffs, not more people. Once you can visualize the end-to-end queue, you can fix it.

• Analyze and Improve: Use this data to isolate defects, non-value-adding handoffs, and unnecessary activity. The goal is to enforce three core disciplines:

  • Simplify to Eliminate: Map processes from start to finish. Remove every step that can not change the outcome. Many approvals exist only to confirm something known. Removing them shortens cycle time and reduces rework.

  • Reduce Handoffs: Enforce a single, clear owner for each end-to-end process. This owner must eliminate handoffs to avoid kicking work around, and they must be empowered to engage stakeholders to facilitate process completion or to consider process improvement opportunities, driving simplification.

  • Protect the Queue: Get the political support to guard the first-in, first-out principle. Where necessary, the cycle times for activities should be equalized to prevent a single bottleneck from crippling the entire flow.

The solution is not to eliminate high-touch service, but to provide it. To handle the politics, create a small, highly skilled unit whose job is to handle one-off requests, political heat, and messy problems. This preserves the flow of the main operation and turns politics into data, revealing where the system is truly breaking down.

The final word

When executive leaders respond to long queue delays by immediately throwing more capacity at the problem, they are choosing the path of least resistance. They are validating less mature management approaches that have allowed disorganized flow, excessive defects, and destructive queue jumping to become the norm. Worse, they are actively demoralizing the more mature managers who run solid, data-driven business processes but must now compete for capacity with their less mature peers.

A strategic service leader must require the hard work of work simplification rather than rewarding inertia with capacity. Customers perceive exceptional value when it is tied to speed and predictability; slow, opaque service delivery drives dissatisfaction regardless of the final work product. Service credibility depends on flow. Service that moves builds confidence. Service that waits erodes trust, even if the work is excellent.

Queue time is the killer, flow is the cure.