Organizational implementation : the design in use of information systems / Morten Hertzum.
Material type:
Item type | Current library | Call number | Status | Date due | Barcode |
---|---|---|---|---|---|
![]() |
Indian Institute of Technology Delhi - Central Library | Available |
Mode of access: World Wide Web.
System requirements: Adobe Acrobat Reader.
Part of: Synthesis digital library of engineering and computer science.
Includes bibliographical references (pages 91-107).
1. Introduction -- 1.1. Organizational implementation -- 1.2. System view on organizational implementation -- 1.3. Practice view on organizational implementation -- 1.4. Chapter outline
2. The context and rationale : organizational change -- 2.1. Organizational change is sociotechnical -- 2.2. Episodic vs. Continuous change -- 2.3. Single-loop vs. Double-loop learning -- 2.4. Bureaucratic vs. Organic organizations
3. Technology adoption : boosters and barriers -- 3.1. Adoption at the management and user levels -- 3.2. Boosters of adoption -- 3.3. Barriers to adoption
4. Implementing information systems : three phases -- 5. Preparations : planning the implementation -- 5.1. Standardization or localization? -- 5.2. User participation -- 5.3. Effects specification -- 5.4. User training, system configuration, task procedures, and incentives -- 5.5. Pilot implementation -- 5.6. Champions
6. Going live : the initial, planned change -- 6.1. Big bang or incremental implementation? -- 6.2. Data migration -- 6.3. Precautions against errors -- 6.4. Productivity dip -- 6.5. Exported problems -- 6.6. Super users
7. Continuing design during use : the long, improvisational process -- 7.1. Design before use or design in use? -- 7.2. Following up on effects realization -- 7.3. Workarounds -- 7.4. Continual support for implementation activities -- 7.5. Tinkerers
8. The larger picture and the local needs -- 8.1. Systems with infrastructural properties -- 8.2. Generification : vendors involving clients in system evolution -- 8.3. User perceptions of organizational implementation -- 8.4. Competences needed locally in the implementation teamnetwork embedding.
Abstract freely available; full-text restricted to subscribers or individual document purchasers.
Compendex
INSPEC
Google scholar
Google book search
Information systems are part and parcel of organizations. Yet, organizations often struggle to realize the benefits that motivate their introduction of these systems. To derive benefit from a new information system, it must be integrated into the structures and processes of the organization. That is, the system must be organizationally implemented. This book is about organizational implementation, which requires thorough preparations but also continues long after the system has gone live: (1) During the preparations, the implementation is planned. This phase includes specifying the effects pursued with the system, adapting the system and organization to each other, and obtaining buy-in for the planned change. (2) At go-live, the system is put to operational use and the associated organizational changes take effect. This phase is about insisting on the planned change even though go-live is normally hectic and accompanied by a productivity dip. (3) During continued use after go-live, implementation continues as design in use. This phase is long and improvisational. It includes following up on effects realization, but it is just as much about embracing the opportunities that emerge from using the system. Apart from covering the three phases of organizational implementation, the book inserts implementation in an organizational-change context and discusses barriers to implementation as well as boosters of implementation. The book concludes with an outlook to larger-scale issues beyond the implementation of one system in one organization and with an overview of the competences needed in the implementation team, which runs the organizational implementation.
Also available in print.
Title from PDF title page (viewed on April 2, 2021).
There are no comments on this title.