GM541 Unit 3 Central Dispatch Failure Case Example

The Week Central Dispatch Lost Its Senior Technicians: A Unit 3 Failed Transformation Case

[Student Name]

Purdue University Global

GM541: Organizational Transformation and Change Leadership

Unit 3 Failed Transformation Case

[Instructor Name]

[Date]

The refrigeration service firm, its people, its stores and every date and figure are composite and illustrative; the frameworks and studies cited are real.

What Central Dispatch Was Meant to Do

Before the change, each of Ardent Cold Service's 140 technicians owned a route of stores. When a store called about a problem, the call went to that store's technician, who often knew the equipment from years of visits. The system worked when technicians were available and failed when they were not: callbacks waited for one particular person, sometimes for hours.

Central dispatch was designed to fix that. A single desk with six dispatchers would receive every call and route it to the nearest qualified technician, using a scheduling engine that tracked locations and skills. Response times would fall, and no store would wait for one person.

The Timeline

Weeks 1 to 8. Central dispatch launched across all three states at once. Average response time fell from about four hours to under three in the first two months, and executives reported the change as a success at the quarterly meeting.

Weeks 9 to 22. Response times held, but repeat visits rose. Technicians sent to unfamiliar stores often fixed the immediate fault without knowing the history of the equipment. Repeat callbacks within seven days rose from about 8 percent of calls to about 14 percent.

Week 23. Leadership made the decision this case turns on. To make dispatch work, it ended route ownership formally: technicians would no longer have assigned stores, and callback overtime, which senior technicians had earned for after-hours calls to their own routes, would be distributed by the scheduling engine to whoever was nearest.

Weeks 24 to 34. Four of the firm's twelve most senior technicians left. Two took early retirement, and two joined a competitor that still worked on routes. Each had more than twenty years on the same stores.

Week 41. On a Saturday night, the walk-in cooler and seafood case at a large supermarket downtown stopped holding temperature. A technician from another zone, sent by dispatch, spent five hours tracing a fault in an older compressor rack. The store's former route technician, one of the four who had left, had fixed the same fault twice before by replacing a worn contactor that looked sound. The store discarded about $38,000 of product, and its chain began asking competitors for bids.

Weeks 42 to 60. Repeat callbacks remained high. Field supervisors began quietly sending calls back to the technicians who knew the stores. By week 60, more than half of calls were being rerouted around the scheduling engine.

Week 61. Central dispatch was switched off without an announcement. Dispatchers were reassigned to scheduling preventive maintenance.

The effort did not fail when dispatch launched; it failed in week 23, when leadership removed the route ownership that held its most experienced technicians, and the knowledge left with them.

Three Candidate Causes

Cause 1: the scheduling engine. The software routed by distance and listed skills, not by knowledge of specific equipment. That weakness was real, and it explains the rise in repeat callbacks in weeks 9 to 22. But repeat callbacks were manageable until week 23; the engine's weakness became costly only when the people who could compensate for it left.

Cause 2: customer complaints. Store managers complained about unfamiliar technicians. But complaints were frequent under the old system too, when callbacks waited for one person, and complaints alone did not lead executives to abandon dispatch.

Cause 3: the loss of senior technicians after week 23. The departures followed the decision directly, and the week 41 failure, which cost a major customer relationship, traces to knowledge that left with them. After the departures, supervisors began rerouting calls, which effectively reversed dispatch before leadership did.

The case keeps the third cause. The first two contributed, but neither would have ended the effort without the third.

Active Inertia

Donald Sull describes active inertia as an organization's tendency to respond to disruption by doing more of what worked before, more intensively (Sull, 1999). Ardent's leadership showed a version of it. When repeat callbacks rose, it responded by pushing harder on the model that was causing them, removing route ownership so dispatch could assign anyone anywhere. The firm accelerated the logic of central dispatch instead of asking what route ownership had been providing.

John Kotter's account of why transformations fail includes declaring victory too soon (Kotter, 1995). Ardent declared success after eight weeks, on response time alone, before the repeat-callback cost appeared.

What Route Ownership Had Been Providing

Route ownership was not only a scheduling arrangement. It held knowledge of specific equipment in specific stores, it gave senior technicians a reason to stay and it gave store managers someone accountable. Central dispatch was designed to improve the first of those functions, availability, and it took away the others without replacing them.

Why Nobody Saw It at the Time

The week 23 decision looked sensible from headquarters. Dispatch could not assign the nearest technician if technicians still owned routes, and callback overtime concentrated on a few senior people looked like an inefficiency. The cost was invisible in the measures leadership watched. Response time stayed low through the departures, because the remaining technicians covered the calls. Repeat callbacks were tracked by the service quality team, whose monthly report went to a director, not to the executive sponsors. And the departures themselves were recorded as ordinary turnover, two retirements and two resignations, rather than as a consequence of the change. Nobody connected the four exits to the week 23 memo until an exit interview, months later, mentioned it directly.

Implications for the Second Attempt

Ardent is now attempting a second, more ambitious change: sensor-driven service with uptime contracts. The failure of central dispatch offers three lessons. First, equipment knowledge must be captured before roles change, not after the people who hold it leave. Second, the new model must give senior technicians a reason to stay, such as roles as zone experts who review alerts for the equipment they know. Third, success should be measured on repeat failures and customer retention, not on response time alone. Organizational change research suggests that the most durable changes adapt to what an organization already does well rather than overriding it (Weick & Quinn, 1999), and route knowledge is what Ardent did well.

Conclusion

Central dispatch failed because of a single decision in week 23 that removed route ownership and lost four senior technicians, whose knowledge the scheduling engine could not replace. The week 41 failure at a downtown supermarket made the cost visible. The second attempt must treat that knowledge as the asset the change depends on.

References

Kotter, J. P. (1995). Leading change: Why transformation efforts fail. Harvard Business Review, 73(2), 59-67.

Sull, D. N. (1999). Why good companies go bad. Harvard Business Review, 77(4), 42-52.

Weick, K. E., & Quinn, R. E. (1999). Organizational change and development. Annual Review of Psychology, 50, 361-386. https://doi.org/10.1146/annurev.psych.50.1.361