aceModerate evidence
Published recordLaborGood Space
More
AI ‐Enabled Performance Feedback Design: The Effects of Anthropomorphic AI Feedback Source, Feedback Valence and Emotional Arousal on Employee Advice‐Taking Behaviour
- Truvace record
- TRV-2026-2696raw data (JSON)
- Version
- v1Published
- First published
- Evidence type
- Controlled or validated comparison
- Sources
- 1 sourcePeer-reviewed
- sha256
- effd5ce8644c…check it
ABSTRACT Companies are increasingly using artificial intelligence (AI) to provide employees with performance feedback, but its efficacy is inconsistent. Drawing upon the theories of mind perception and feedback intervention, we examine the effects of anthropomorphic AI feedback source and feedback valence in conveying performance feedback on employees' advice‐taking behaviours. We conducted a 2 × 2 experiment in which we manipulated anthropomorphic AI feedback source (more versus less) and examined how feedback…
The gain
In a 2×2 experiment using skin-conductance sensors during a production task, employees who got positive feedback from a more human-like AI showed higher emotional arousal and took more advice afterward than those who got it from a less human-like AI.
What this doesn’t fix
The human-like AI advantage appeared only for positive feedback; under negative feedback, arousal and advice-taking did not differ between the AI types.
Sources
1 on file- Accounting & Financedoi:10.1111/acfi.70228
Cite this record
v1Truvace Impact Record TRV-2026-2696, v1: “AI ‐Enabled Performance Feedback Design: The Effects of Anthropomorphic AI Feedback Source, Feedback Valence and Emotional Arousal on Employee Advice‐Taking Behaviour.” Truvace, 2026-11-12. /record/TRV-2026-2696 (accessed on the day you copy it). sha256 effd5ce8644cb886…
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-2696 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.