Moderate evidence
Published recordLaborThe Trace
More
Affiliation or alienation? How does AI awareness affect employees’ interaction with co-workers
- Truvace record
- TRV-2026-2524raw data (JSON)
- Version
- v1Published
- First published
- Evidence type
- Survey
- Sources
- 1 sourcePeer-reviewed
- sha256
- f566d8c07e2a…check it
Purpose The purpose of this study is to address this research gap by shifting attention from the individual consequences of AI awareness to its interpersonal implications. While workplaces value interactions between co-workers, research on artificial intelligence (AI) awareness has focused on its impact on employees themselves, to the detriment of its impact on interactions among colleagues. Through a longitudinal tracking study and based on social information processing (SIP) theory and the social affiliation l…
52Gain side
How the two sides scoreClose call
51Problem side
The gain
In a three-wave study of 298 employees in China, greater AI awareness increased workers' need for affiliation with colleagues, which in turn promoted helping behaviour.
The problem
In the same study of 298 employees in China, AI awareness also reduced helping behaviour through a second pathway, workers' sense of alienation from colleagues.
A fixed formula sets both scores from the evidence and its sources. Reader votes don’t move them.
What the scores mean
G is the gain side, out of 100. It goes up when the gain is specific, when it measurably helped people and when the sources behind it are strong.
P is the problem side, out of 100. It goes up when the problem is specific, when it measurably hurt people and when the sources behind it are strong.
What this doesn’t fix
The model was tested on three waves of data from 298 participants in China, so the findings reflect a single national sample.
Sources
1 on file- Chinese Management Studiesdoi:10.1108/cms-06-2025-0621
Cite this record
v1Truvace Impact Record TRV-2026-2524, v1: “Affiliation or alienation? How does AI awareness affect employees’ interaction with co-workers.” Truvace, 2026-11-12. /record/TRV-2026-2524 (accessed on the day you copy it). sha256 f566d8c07e2ab93c…
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-2524 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.
ace