Cited by 437ERP Systems Implementation and ImpactJob Satisfaction and Organizational BehaviorEmployer Branding and e-HRM

Job Characteristics and Job Satisfaction: Understanding the Role of Enterprise Resource Planning System Implementation1

Morris, Michael G., Venkatesh, Viswanath·2010·MIS Quarterly

Abstract

Little research has examined the impacts of enterprise resource planning (ERP) systems implementation on job satisfaction. Based on a 12-month study of 2,794 employees in a telecommunications firm, we found that ERP system implementation moderated the relationships between three job characteristics (skill variety, autonomy, and feedback) and job satisfaction. Our findings highlight the key role that ERP system implementation can have in altering well-established relationships in the context of technology-enabled organizational change situations. This work also extends research on technology diffusion by moving beyond a focus on technology-centric outcomes, such as system use, to understanding broader job outcomes.

Integrity signals

Registry

Crossref · 10.2307/20721418

Cites

9 of 9 references verified0 citation errors · 0 not checkable

Statistics

Recomputing p-values needs the paper’s full text.

Claims the paper makes

This paper’s full text isn’t openly available, so its claims and self-check weren’t run. The registry and citation checks still apply.

Claims other papers make about this one

Each is checked against this paper’s own text: does it say what the citing paper says it does?

  • ES implementations comprise an extensive redesign of business processes and the deployment of new software to support the new business processes.

    “ES implementations comprise two main parts—an extensive redesign of business processes and the deployment of new software to support the new business processes (Morris and Venkatesh 2010; Robey et al. 2002).”
  • ES implementations fundamentally change the nature of tasks, workflows and therefore employees' jobs.

    “ES implementations fundamentally change the nature of tasks, workflows and therefore, by extension, employees' jobs (Davenport et al. 1996; Morris and Venkatesh 2010).”

Cites

Flagged first, then by citations

Cited by

Sorted by citations

Authors
Morris, M. G., & Venkatesh, V.
Affiliations
  • University of Virginia (US)
  • University of Arkansas at Fayetteville (US)
Venue
MIS Quarterly
Publisher
MIS Quarterly
Published
2010-03-01
Volume
34
Issue
1
Pages
143-161
ISSN
  • 0276-7783 (ISSN-L)
  • 2162-9730
OpenAlex
W1595444319
Cited by
437
References
9
Citations by year
2026: 12 · 2025: 24 · 2024: 19 · 2023: 24 · 2022: 50 · 2021: 40 · 2020: 43 · 2019: 35 · 2018: 23 · 2017: 26 · 2016: 26 · 2015: 35 · 2014: 19 · 2013: 20 · 2012: 22
FWCI
38.68
Type
journal article
Language
en
Open access
closed
Locations
MIS Quarterly (publishedVersion)
Topics
  • Social Sciences › Business, Management and Accounting › Management Information Systems › ERP Systems Implementation and Impact
  • Social Sciences › Business, Management and Accounting › Organizational Behavior and Human Resource Management › Job Satisfaction and Organizational Behavior
  • Social Sciences › Business, Management and Accounting › Organizational Behavior and Human Resource Management › Employer Branding and e-HRM
Keywords
enterprise resource planning, ERP implementation, job characteristics, job satisfaction, skill variety, employee autonomy, feedback, moderating effect, technology diffusion, organizational change, telecommunications company employees

About these checks

Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.

Statistics and arithmetic are recomputed, not judged.

Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.

What counts as a claim ›How we measure confidence ›How we check this ›

Are you an author, or do you see a problem with this page? Request a review