GB740 Unit 6 Seminar Reflection Example

What Keeps a Change Alive After the Sponsor Moves On: A Unit 6 Seminar Reflection on Sustaining Change

[Student Name]

Purdue University Global

GB740: Organizational Development

Unit 6 Seminar Reflection

[Instructor Name]

[Date]

The claims center case discussed in the seminar, Tallis Engineering and its people are composite and illustrative; the sources cited are real.

What I Believed Before the Session

What I wrote in my notebook the evening before the session reads: "Sustainability depends on sponsor commitment. If the COO stays visibly attached to the resourcing changes for two years, they will hold." I had built my plan for Tallis Engineering around that idea. The chief operating officer would chair the new resourcing forum for its first year, open each quarterly review with the multi-office margin figures and mention the changes at every all-staff meeting. I thought of his visible attention as the engine of the change.

I had reasons for that belief. In my own experience, initiatives at Tallis had died when executives stopped mentioning them, and the most successful change I had seen, a safety program introduced after a site incident in 2021, had been carried by a regional director who talked about it constantly. It seemed obvious that the resourcing changes would need the same kind of champion. I had even drafted a calendar of the chief operating officer's appearances: the forum's first meeting, each quarterly review, the annual leadership retreat. What I had not asked was what would happen to the safety program when that director retired, which happened last spring. I still do not know whether it survived him.

The Case as We Discussed It

The case described a claims center of about 180 adjusters where a site director had replaced supervisor-assigned work with self-managing teams. Teams of eight allocated their own claims, set their own schedules and met each morning to review the queue. For a year, cycle times fell and turnover dropped. Then the site director was promoted to a regional role. Her successor did not reverse anything. He simply did not attend the morning meetings. Within a few months, supervisors had begun assigning difficult claims directly again, because adjusters asked them to and it was faster. Team meetings thinned, then stopped. Fourteen months after her promotion, the center worked as it had before, and nobody had broken a rule, because the arrangements had never been written into any.

The Question That Moved Me

I said during the discussion that the problem was the successor's lack of commitment. A classmate, Ruth, asked a different question: what in the claims center's budget, pay structure or performance measures had changed when the teams were created? I did not know, and the case said nothing. Our instructor pointed out that the silence was the answer. The teams had been sustained by the site director's attention and by nothing else. Supervisors were still evaluated on the same measures as before, adjusters were still paid the same way and the budget still funded supervisors to assign work. When her attention left, everything that remained pulled back toward the old way.

Walton (1975), writing about early work innovations that failed to spread or last, found much the same pattern: experiments that succeeded locally often reverted when the champion left, especially when the surrounding systems of pay, supervision and measurement had not changed to support them. Buchanan et al. (2005) reached a similar conclusion in a much later review, listing the organizational factors that sustain change and noting how often sustainability is assumed rather than designed.

A change held up only by a leader's attention lasts exactly as long as the attention does.

What This Means for Tallis

Looking at my plan with Ruth's question in mind, I saw that most of it relied on the chief operating officer. The shared margin credit, the resourcing forum and the lower utilization target would all exist on paper, but nothing in the plan made them hard to undo. A new chief operating officer could stop attending the forum, and office leaders would drift back to trading favors, just as supervisors drifted back to assigning claims. Cummings and Worley (2019) call the missing step institutionalization, the point at which a change is carried by the organization's ordinary structures and routines rather than by the people who introduced it, and my plan had skipped it.

So I have changed the plan in three ways. First, shared margin credit will be written into the office leaders' bonus plan, which is approved annually by the board, rather than announced as a policy. Reversing it would require a board decision. Second, the resourcing forum will have a written charter, its own line in the operations budget for a coordinator's time, and a rule that unfilled requests over ten days are reported to the executive team automatically. Third, the project manager utilization target will be changed in the human resources system that generates performance reviews, so that the old target cannot quietly return.

The Counterargument I Kept

Not everyone in the seminar agreed. One classmate argued that writing changes into pay and budget too early can lock in a design before anyone knows whether it works. That seems right to me, and I have not fully answered it. My response is to write the changes into the systems but schedule a review of each at twelve months, with the evaluation data from Unit 9. A change that is hard to undo by neglect can still be undone by evidence, and that is the kind of permanence I want.

References

Buchanan, D., Fitzgerald, L., Ketley, D., Gollop, R., Jones, J. L., Lamont, S. S., Neath, A., & Whitby, E. (2005). No going back: A review of the literature on sustaining organizational change. International Journal of Management Reviews, 7(3), 189-205. https://doi.org/10.1111/j.1468-2370.2005.00111.x

Cummings, T. G., & Worley, C. G. (2019). Organization development and change (11th ed.). Cengage.

Walton, R. E. (1975). The diffusion of new work structures: Explaining why success didn't take. Organizational Dynamics, 3(3), 3-22. https://doi.org/10.1016/0090-2616(75)90027-3