The Theme of Resistance
|Written by Patrick Morley|
|Sunday, August 28 2005 19:00|
NOTE: Last week, we accidentally sent the ninth edition in our series on the major themes for implementing organizational change found in academic journals. Thank you for those that emailed us about the mistake. Here is the missing Weekly Briefing for the eighth edition. Next week will be the wrap up. We are looking for clues to answer the question, “Why do some men’s discipleship programs succeed while others languish or fail?” For now, I leave it to you to apply these general summaries to your men’s discipleship program. You can also apply the themes more broadly to change your business, your church, or even your family.
People resist what they don’t understand. People resist what they don’t like. People resist because, “We tried that before and it didn’t work.” People resist just to resist. People resist for many reasons. We will never successfully plant the flag for men’s discipleship ministry in our churches unless we a) understand the dynamics of resistance and b) proactively plan and deal in love with resisters.
The eighth theme in organizational change literature is handling resistance. A significant risk from a failed change initiative is the increased resistance it creates for future change initiatives (Beer et al., 1990). Identifying and dealing with sources of resistance must be an integral part of an organizational change program if it is to work. Here are the factors related to this theme I found in the literature.
Identify resistance. When implementing a continuous improvement program it was important to identify sources of resistance and develop a plan to address it (Beer, 2003). Resistance to change can come from individuals or groups within the organization, either negatively as protecting the existing way of doing things, or positively as loyalty to preserve the organization (Ansoff & McDonnell, 1990). Behavioral resistance pertains to how individuals resist change, while systemic resistance pertains to how the organization responds to the pressure created by the extra demands on its capacity (Ansoff & McDonnell). Removing resistance empowers people to act (Kotter, 1995). However, Argyris (1990) noted that management teams find it difficult to face how their organizations resist new programs and initiatives.
Process to deal with resistance. A continuous quality improvement program in Canadian hospitals found systemic resistance required the firm resolve and special skills of transformational leaders over many years (LeBrasseur, 2002). Ansoff and McDonnell (1990) proposed a flexible method for countering resistance that emphasized first building support, then making changes in phases (culture first, then competencies, finally strategy but only when the organization is ready), and controlling the resistance as the initiative is implemented.
In summary, handling resistance is a major theme in bringing about organizational change. Related factors include mechanisms to identify and processes to deal with behavioral and systemic resistance. The final theme of routinization will be explored in the next Weekly Briefing.
For the glory of Christ and no other reason,
Alexander, L. (1985). Sucessfully implementing strategic decisions. Long Range Plannning, (18)3, 91-97.
Ayas, K., & Zeniuk, N. (2001). Project-based learning: building communities of reflective practitioners. Management Learning, 32(1), 61-76.
Beer, M. (2003). Why total quality management programs do not persist: the role of management quality and implications for leading a TQM transformation. Decision Sciences, 34(4), 623-642.
Charan, R. & Colvin, G. (1999). Why CEOs fail. Fortune 139(12), pp. 68-75.
Freedman, M. (2003). The genius is in the implementation. Journal of Business Strategy, 24(2), 26-31.
Houston-Philpot, K. (2002). Leadership development partnerships at Dow Corning corporation. Journal of Organizational Excellence, 22(1), 13-27.
Johnson, K., Hays, C., Center, H., & Daley, C. (2004). Building capacity and sustainable prevention innovations: a sustainability planning model. Evaluation and Program Planning, 27(2), 135-149.
Kotter, J. P. (1995). Leading change. Boston: Harvard Business School Press.
Kotter, J. P. (1996). Leading change: why transformation efforts fail. Harvard Business Review, 73(2), 59-67.
Kotter, J. (1999). Ten observations. Executive Excellence, August, 1999, 15-16.
Kotter, J. P. (2001). What leaders really do. Harvard Business Review, 79(11), 85-96.
LeBrasseur, R., Whissell, R., & Ojha, A. (2002). Organisational learning, transformational leadership and implementation of continuous quality improvement in canadian hospitals. Australian Journal of Management, 27(2), 141-162.
Miller, D. (2002). Successful change leaders: what makes them? what do they do that is different? Journal of Change Management, 2(4), 359-368.
McNish, M. (2002). Guidelines for managing change: a study of their effects on the implementation of new information technology projects in organization. Journal of Change Management, 2(3), 201-211.
Okumus, F. (2003). A framework to implement strategies in organizations. Management Decision, 41(9), 871-882.
Repenning, N. P. (2002). A simulation-based approach to understanding the dynamics of innovation implementation. Organization Science: A Journal of the Institute of Management Sciences, 13(2), 109-127.
Zaleznik, A. (2004). Managers and leaders: are they different? Harvard Business Review, (82)1, 74-81.