aceModerate evidence
Published recordLaborProblem Space
More
How Employee–AI Collaboration Influences Coworkers’ Helping Behaviour: An Attribution Theory Perspective
- Truvace record
- TRV-2026-2576raw data (JSON)
- Version
- v1Published
- First published
- Evidence type
- Survey
- Sources
- 1 sourcePeer-reviewed
- sha256
- 610527a96138…check it
As artificial intelligence (AI) is increasingly integrated into the workplace, employee-AI collaboration is evolving from a personal productivity tool to a social cue that coworkers can observe and interpret. Existing research has largely emphasised the performance and well-being effects of employee-AI collaboration; however, few studies have revealed, from the observer's perspective, its potential negative spillover mechanisms on coworkers' helping behaviour. Based on attribution theory, this study constructs a…
The problem
In a two-wave survey of 375 coworker evaluations in Chinese firms, the more coworkers saw a colleague as collaborating with AI, the less help they gave that colleague (r = -0.530), partly because they read it as laziness or avoiding responsibility.
What this doesn’t fix
Study 1 is correlational and rests on coworkers' perceptions of a colleague's AI use rather than usage logs or actual collaboration frequency, and its participants were from firms in Chinese regions such as Hubei and Jiangsu.
Sources
1 on file- Behavioral Sciencesdoi:10.3390/bs16060985
Cite this record
v1Truvace Impact Record TRV-2026-2576, v1: “How Employee–AI Collaboration Influences Coworkers’ Helping Behaviour: An Attribution Theory Perspective.” Truvace, 2026-11-12. /record/TRV-2026-2576 (accessed on the day you copy it). sha256 610527a96138f582…
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-2576 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.