aceModerate evidence
Published recordLaborProblem Space
More
How workplace AI feedback shapes AI dependency: A randomized controlled trial on the moderating role of workplace social support among Japanese office workers
- Truvace record
- TRV-2026-2566raw data (JSON)
- Version
- v1Published
- First published
- Evidence type
- Randomized controlled trial
- Sources
- 1 sourcePeer-reviewed
- sha256
- 36e84e44fec1…check it
AI dependency—habitual, automatic AI use accompanied by diminished autonomy—is a growing concern in the workplace, yet the conditions under which it develops remain poorly understood. Two competing pathways have been proposed. Users with limited social support from colleagues may compensate for this deficit by depending on AI (the compensatory pathway ), or users with abundant support may be better positioned to leverage AI interaction, thereby fostering dependency (the enhancement pathway ). To test these pathw…
The problem
In a randomized trial of 294 Japanese office workers, positive chatbot feedback increased AI dependency one week later regardless of workplace support, and negative feedback did so among workers with abundant social support.
What this doesn’t fix
The outcome was short-term and self-reported, the analysis was exploratory and not preregistered, the key interaction was modest in size, and the crowdsourced Japanese sample limits generalizability.
Sources
1 on file- Computers in Human Behavior: Artificial Humansdoi:10.1016/j.chbah.2026.100365
Cite this record
v1Truvace Impact Record TRV-2026-2566, v1: “How workplace AI feedback shapes AI dependency: A randomized controlled trial on the moderating role of workplace social support among Japanese office workers.” Truvace, 2026-11-12. /record/TRV-2026-2566 (accessed on the day you copy it). sha256 36e84e44fec16d86…
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-2566 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.