AWWA JAW31489

Too often, organizations implement automated computerized systems from the top down and concentrate on technical issues to the exclusion of human factors. Frequently such systems fail because the people most directly involved with them during the workday find them impractical or resent not having been involved in planning. To prevent this from happening, the authors propose that organizations select from within their ranks a "system champion" who is familiar with the process being automated and who can serve as a focal point for preliminary organizationwide communication and for project planning. This article describes the characteristics of such a system champion and the support he or she needs from the organization. It suggests that organizational issues must be addressed as an integral part of systems projects. Includes figure.