aceModerate evidence
Published recordLaborProblem Space
More
The indirect effect of artificial intelligence awareness on counterproductive work behavior: A meta-analytic study
- Truvace record
- TRV-2026-2703raw data (JSON)
- Version
- v1Published
- First published
- Evidence type
- Systematic review or meta-analysis
- Sources
- 1 sourcePeer-reviewed
- sha256
- 0182b75022a0…check it
BackgroundAs artificial intelligence (AI) becomes increasingly integrated into the workplace, an important question concerns how employees respond when technological change is perceived as threatening rather than beneficial. Prior studies have examined several mechanisms linking AI awareness to employee attitudes and behaviors, but these mechanisms are often studied separately, limiting understanding of the broader psychological process underlying adverse employee reactions.ObjectiveThis study examines the media…
The problem
A meta-analysis of 45 studies with 16,140 participants found that greater awareness of AI at work was positively linked to job insecurity and counterproductive work behavior, including a substantial direct effect on that behavior.
What this doesn’t fix
The sequential path through job insecurity and psychological contract breach was only modest, and a substantial direct effect remained, so the mediators explain only part of the link.
Sources
1 on file- WORK: A Journal of Prevention, Assessment & Rehabilitationdoi:10.1177/10519815261492674
Cite this record
v1Truvace Impact Record TRV-2026-2703, v1: “The indirect effect of artificial intelligence awareness on counterproductive work behavior: A meta-analytic study.” Truvace, 2026-11-12. /record/TRV-2026-2703 (accessed on the day you copy it). sha256 0182b75022a03004…
Change history
1 versionEvery change made to this record since it was first published, and why. Nothing has changed since it went up.
Certified into the record
Check this record hasn’t been altered
How to check it yourself, without trusting this page
Download any version from /api/record/TRV-2026-2703 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.