Why does the system usage differ between organizational units? - a case study in a knowledge-intensive project organization

0Citations
Citations of this article
11Readers
Mendeley users who have this article in their library.
Get full text

Abstract

This paper seeks to examine how a case company exploits new staffing procedures and enterprise system (ES) functionalities in order to improve allocation and control of project resources. The paper relies on qualitative data collected through an in-depth case study in a large European high-tech company over a period of one and a half years. In order to understand the system usage in the case company the paper employs institutional theory and Orton and Weick’s concept of coupling. By combining the concept of coupling with the elements of system usage - work assignment, user, and system -, the paper explains why system usage differs between organizational units. Findings show how the use of new ES functionalities is influenced by features of organizational unit, features of work assignment, individual characteristics as well as target customer. The paper also recommends selective system use in a knowledge-intensive project organization.

Cite

CITATION STYLE

APA

Mattila, M. (2015). Why does the system usage differ between organizational units? - a case study in a knowledge-intensive project organization. Lecture Notes in Business Information Processing, 198, 95–110. https://doi.org/10.1007/978-3-319-17587-4_6

Register to see more suggestions

Mendeley helps you to discover research relevant for your work.

Already have an account?

Save time finding and organizing research with Mendeley

Sign up for free