Managing change in IT improvement initiatives.
Wednesday, February 1 2006
Over the last decade, many governments have sought out enterprise-wide financial and human resource systems (commonly known in the technology industry as "ERP" systems) with the expectation that these systems would reduce costs by improving inefficient business processes. Unfortunately, far too many of these governments have been disappointed when their multi-million dollar technology investments have not yielded the desired outcomes. In most cases, the problem lies not in the technology itself, but rather in the cultural and institutional norms of the organization. If these norms are resistant to organizational improvement efforts, as they often are, they will undermine any process improvement initiative, including ERR
Governments are beginning to understand that they must expand their improvement activities to address not only the business and technical components of their organization, but also the cultural components. To accomplish this, governments have begun to incorporate change management and other organizational development tools into their improvement strategies. These tools have proven instrumental in helping governments expose, understand, and resolve the cultural challenges that cause organizations to underperform and that contribute to the failure of ERP initiatives.
This article is an introduction to the discipline of change management. We begin by explaining the inherent human challenges that change management seeks to address. The author then discusses the origins of change management and summarizes the change management roles that are common on ERP projects. The article then turns to some of the common mistakes and assumptions that are made about change management. We then provide recommended tips to maximize change management in ERP projects.
OUR NATURAL AVERSION TO CHANGE
Human beings are creatures of habit. As such, our need to do things with consistency is more intense than our desire to do things well. Most people prefer to work in organizations with an established 'status quo." Even if the work environment is blatantly inefficient, we are more inclined to accept these inefficiencies and develop "workarounds" to compensate for them than to make the changes required to fix them. This is because our efforts to improve the organization may also result in changes in organizational and job stability. Because many of us depend on our jobs for stability in other aspects of our lives, few people are willing to risk disrupting that stability for the sake of organizational improvements.

