Managing the Digital Firm, Seventh Canadian Edition
Section 13.1, “Systems as Planned Organizational Change”
This section discusses different ways to manage organizational change. It begins with
Figure 13-1 that illustrates four common forms of organizational change and the
risk/reward of each one. From simple automation to the more drastic paradigm shift, each
one requires careful management of the effects these changes have on people. Business
process redesign (BPR) has taken on a negative reputation over the years, mostly because
“Section 13.2, Overview of Systems Development”
This section breaks down the systems development process into six separate activities:
system analysis, system design, programming, testing, conversion, and production and
maintenance. Specific information requirements must be established at the beginning of
the system analysis phase. Otherwise, you may be building a system that doesn’t solve an
organization’s problem. Faulty requirements analysis is a leading cause of systems failure
and high systems development costs. Another major cause of system failure is attributed
to insufficient user involvement in the design effort. Too many times system analysis and
design are left up to the IT staff instead of involving users throughout the system
development process. What’s most important to remember is that the changes introduced
into the organization will be the most problematic to manage. People don’t like change
and will sometimes do what they can to prevent it.