![Journal of the Association for Information Systems](/assets/md5images/7d0f2e2cee35f7ed26a4ee6adaf8ae90.jpg)
Abstract
Identifying causal relationships is an important aspect of scientific inquiry. Causal relationships help us to infer, predict, and plan. This research investigates the causal relationships between two constructs, perceived enjoyment (PE) and perceived ease of use (PEOU), within the nomological net of user technology acceptance. PE has been theorized and empirically validated as either an antecedent or a consequence of PEOU. We believe that there are two reasons that account for this ambiguity the conceptual coupling of PE and PEOU and the limitations of covariance-based statistical methods. Accordingly, we approach this inconsistency by providing more theoretical reasoning and employing an alternative statistical method, namely Cohen's path analysis. Specifically, as suggested by previous research on the difference between utilitarian and hedonic systems, we propose the conditional dominance of causal directions. Empirical results from two studies using different technologies and user samples support the theoretical claim that the PE?PEOU causal direction outweighs the PEOU?PE direction for utilitarian systems. There are both theoretical and the methodical contributions of this research. The approach applied in this research can be generalized to study causal relationships between conceptually coupled variables, which otherwise may be overlooked by confirmatory methods. We encourage researchers to pay attention to causal directions in addition to causal connectedness.
Recommended Citation
Sun, Heshan and Zhang, Ping
(2006)
"Causal Relationships between Perceived Enjoyment and Perceived Ease of Use: An Alternative Approach,"
Journal of the Association for Information Systems, 7(9), .
DOI: 10.17705/1jais.00100
Available at:
https://aisel.aisnet.org/jais/vol7/iss9/24
DOI
10.17705/1jais.00100
When commenting on articles, please be friendly, welcoming, respectful and abide by the AIS eLibrary Discussion Thread Code of Conduct posted here.