Discussions of the change management project


Problem:

The information contain discussions of a change management project that went well and one that did not go well from two different learners. It also listed the factors that lead to the success or failure of the project.

Please give comments for both of these discussions pertain to the following:

When responding to others, seek clarification, share your personal experiences that relate to their experience, and provide feedback on their posts. In addition, consider providing suggestions for how others can improve their change management processes and call out themes that emerge throughout the discussion.

Case Scenario 1:

In modern businesses the old adage “the only constant is change” is more relevant now than ever before. Kotter (1996) suggests that faced with increased competition a trend toward organizational transformation will continue for the foreseeable future (p. 66).  This trend will is exacerbated by the recent economic downturn and frantic search for revenue and cost reductions.

As with so many others my organization has been following this trend for the past few years with decidedly mixed results at best.  Two specific projects with very different outcomes immediately come to mind: a multi-divisional reorganization, and an attempted division of labor which failed miserably. Rather than lead with a negative I have chosen to review the reorganization prior to the failed reclassification of labor.

Nearly a year ago I was asked to participate in a complete reorganization of three separate divisions at my firm. At the time sales where sluggish in all three businesses and concern was mounting organization wide about the status of our company.  As a result of this perception and external threat, thus conditions for change were optimal. In accordance with Kotter’s (1996) eight stage change process in that crisis was evident to all parties (p. 21).  Pending disaster makes for strange bedfellows. Because of the sense of urgency a leadership or guiding coalition was created without a great deal of resistance. Interestingly enough, even the most ardent of enemies where able to put down their swords for the greater good. Fortunately the reorganization is approximately 95% completed at this time; collectively we are at 160% revenue versus last fiscal year.  Two of the three merged companies are enjoying greater than double digit growth over the same period.

Failure is only failure if nothing is learned from the experience. Several years back it was decided (in some dark room, by no doubt ill-intentioned villains), that a new hybrid support position was necessary. Functionally the concept was to create an escalation point that was to represent customer perspectives to the factory in Japan.  Not an all together bad concept, however, no one bothered to tell the people who already performed that function this was going to happen. Clearly a sense of urgency was not created, if there was a guiding coalition they were either afraid to reveal themselves, or simply did not care enough to engage. Regardless, these poor individuals did not stand a chance within two years all were terminated and the entire program scrapped in favor of “the way it was”.  Having been a manager at the time, I paid a great deal of attention to this process and have never forgotten the value of communicating effectively since.   

Reference:

Kotter, J. P. (1996). Leading change. Boston, Mass.: Harvard Business School Press.

Case Scenario 2:

The reality of today’s business environment is not only that change is a constant, but also the rate at which this change is occurring is building momentum, with no clear sign of slowing. Within this environment, the need for business and corporations to change is no longer in question, with each company wading into the waters of implementing change efforts in a variety of form and fashion. What is amazing is the amount of failed change efforts, being that so many efforts are put in place. Kotter (1996) identifies eight key reasons for the failure of these change efforts, the first two being failure to address complacency and the lack of a powerful guiding coalition. This post will address first a successful change project, and then a change project that suffered failure, both of which will highlight the importance of these two factors.

One change project that has proven successful (to this point) has been the restructuring and combination of two district offices into one larger reporting office. This change has been successful for a variety of reasons including the buy-in and support from senior management as well as the logical sequence through which the change occurred. This reorganization was announced 2 months prior to the actual change date which providing a time frame by which to prepare as well as a drop-dead date to start. This eliminated the complacency that can creep in when these changes remain left as unaddressed rumors. Even though not all names had been announced, the overall reporting structure as well as new roles and responsibilities were clearly communicated to all involved, helping to ease the resistance to this change by providing a vision for the future. One key factor in the success of the change is what was left alone. While the reporting structure and some middle management were shuffled, the day to day operations of both offices were left pretty well intact, which has benefited the continuity of operations as well as continued customer support of the highest level. While some managers lost more important or prestigious titles, each one has presented a unified support of this change, creating a powerful coalition and influencing their direct reports in buying into this change as well (Kotter, 1996). The combination of eliminating the complacency and a unified and powerful guiding coalition, along with the clearly defined and planned sequencing of this change process has provided for a relatively smooth transition and has put in place the framework to anchor this change into the culture of these offices (Kotter, 1996).

A change project that did not go well is evidenced in the creation of a new position within our office to fill a need as voiced by several employees. While the need for the position was indeed correct, and the sense of urgency to create the position was in place, those involved placed the proverbial cart before the horse. As described by Collins (2001), management had the right people on the bus; however, they were in the wrong seat. This one mistake led to a two-year experiment gone wrong, and the unfortunate termination of a valuable employee, who had simply been placed in the wrong role. The implementation of the new role operated just fine, and was indeed warranted, however, by rushing through the creation of the coalition and selecting the wrong individual to fill the role, the position created little change in the way of any noticeable or needed improvements. While urgency was in place to create the new role, change because of this creation was slow do to the acceptance of the status quo as adequate. In this example, sequencing played a huge role in the overall failure of this change effort, although the process never actually made it passed the guiding coalition before results were expected.

References:

Collins, J. (2001). Good to great: Why some companies make the leap... and others don't. New York, New York: HarperCollins.

Kotter, J. P. (1996). Leading change. Boston, Massachusetts: Harvard Business School Press.

Solution Preview :

Prepared by a verified Expert
Other Management: Discussions of the change management project
Reference No:- TGS01784871

Now Priced at $25 (50% Discount)

Recommended (99%)

Rated (4.3/5)