GM541 Unit 9 Zone Rollout Sequencing Plan Example

Never Two Zones in the Dip at Once: A Unit 9 Sequencing and Sustaining Plan for Sensor-Driven Service

[Student Name]

Purdue University Global

GM541: Organizational Transformation and Change Leadership

Unit 9 Sequencing and Sustaining Plan

[Instructor Name]

[Date]

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

Forecasting the Dip

The pilot zone's record gives the plan its forecast. In the first month after conversion, repeat callbacks held near the old baseline of about 8 percent of calls. In months two through four they rose to about 9.5 percent, roughly 18 percent above baseline, and case uptime slipped from 99.4 to 99.0 percent. Technicians were learning stores they had not worked before, and the alert thresholds were still being tuned for older equipment. By month five, callbacks had fallen to about 7 percent and uptime had recovered to 99.5 percent, both better than before.

Michael Fullan describes this pattern as an implementation dip: performance and confidence fall when people first use a new approach, because they are learning new skills and meanings, before rising above the old level if the change is sustained (Fullan, 2001). The plan treats the dip as expected, not as evidence of failure. The danger is not the dip itself but two zones being in it at once, which would stretch the monitoring room and field supervisors while customers in both zones see weaker service.

Sequencing the Remaining Zones

East zone first. It has the newest equipment, with about 70 percent of systems on electronic controllers that the sensors read well, and three of its four largest customers have already signed uptime contracts. Its dip should be shallow.

South zone second. Mixed equipment and a field supervisor who helped design the pilot's alert review board.

West zone third. Mostly rural stores with long drive times, where fewer scheduled visits saves the most travel but where a missed alert costs the most time to fix.

Downtown zone last. The oldest equipment, with many mechanical systems the sensors read poorly, and the most senior crews, several of whom were affected by the central dispatch failure. By the time downtown converts, thresholds for older equipment will have been calibrated in three zones, and senior technicians from those zones can help.

Each zone begins only when the previous one has cleared its dip, defined as two consecutive months with repeat callbacks at or below the pre-conversion baseline. At the pilot's pace, that means roughly five months between zones and a full conversion in about two years.

The order puts the zones most likely to succeed first, so that each later zone, and especially downtown, can learn from what worked before it starts.

The Decision Rule

Before any zone converts, the executive team agrees on what it will do if the numbers turn bad. Writing the rule down in advance prevents a difficult month from producing either panic or denial.

If a zone's repeat callbacks remain above 125 percent of its baseline for more than four months, or if case uptime falls below 98.8 percent for two consecutive months, the next zone's conversion is paused and a review is convened within two weeks. The review includes the zone supervisor, the union steward, the monitoring room lead and two technicians from the zone. It may recommend adjusting thresholds, adding temporary staff, slowing the schedule or, in the worst case, returning the zone to scheduled visits while problems are fixed. The executive sponsor commits not to cancel the program on a single bad month inside the expected dip.

Sustaining the Change

Change tends to stick when it becomes part of ordinary routine and stops depending on a project team's attention (Weick & Quinn, 1999). Each mechanism that keeps the new model in place has an owner.

Alert review boards. Owned by each zone's field supervisor, meeting monthly to review disputed alerts and change thresholds.

The decision log. Owned by the project lead until conversion is complete, then by the director of service operations.

Zone experts for older equipment. Owned by the senior technician named in each zone, with time set aside for threshold reviews and training.

Uptime reporting to customers. Owned by the account managers, with quarterly reports for every customer drawn from the monitoring room's data.

Revised on-call pay. Owned by human resources and the union local, with a review after each zone's first six months.

Recognition. The annual technician award moves from fewest callbacks to fewest hours of warm cases on a technician's assigned stores, owned by the director of service operations.

Avoiding Early Victory

John Kotter warned against declaring victory too soon (Kotter, 1995), and Ardent made that mistake with central dispatch, celebrating response times after eight weeks. This plan reports progress to the board only after each zone has cleared its dip, and the first full report comes after the east zone's fifth month, not its first.

Limits

The forecast rests on one pilot zone. The dip in other zones may be deeper or longer, especially downtown, and the decision rule's thresholds may need revising after the east zone converts.

References

Fullan, M. (2001). Leading in a culture of change. Jossey-Bass.

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

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