Moderate evidence
Published recordLaborGood Space
More
Large Language Model-Based Artificial Intelligence as a Relational Leader? Effects of Leadership Style and Stress on Artificial Intelligence Leadership
- Truvace record
- TRV-2026-2574raw data (JSON)
- Version
- v1Published
- First published
- Evidence type
- Controlled or validated comparison
- Sources
- 1 sourcePeer-reviewed
- sha256
- a0becb022942…check it
This study provides an initial investigation into the objective performance, subjective perceptions, and neural correlates of relational leadership behaviors demonstrated by large language model (LLM)-powered artificial intelligence (AI) leaders in the workplace. A 2 × 2 × 2 mixed-design experiment was conducted, with leadership style (relational versus non-relational) and supervisor type (human versus AI) as between-subjects variables, and stress level (high versus low) as a within-subjects variable. Eighty-two…
The gain
In an experiment with 82 university students, an AI supervisor that used relational leadership behaviors improved workplace well-being, self-perceptions and leadership ratings, and most perceptions were similar to those under a human supervisor.
What this doesn’t fix
The authors describe the work as an initial investigation using 82 university students in a simulated automotive inspection task, so the findings come from a small, non-workplace sample.
Sources
1 on file- Journal of Leadership & Organizational Studiesdoi:10.1177/15480518261458468
Cite this record
v1Truvace Impact Record TRV-2026-2574, v1: “Large Language Model-Based Artificial Intelligence as a Relational Leader? Effects of Leadership Style and Stress on Artificial Intelligence Leadership.” Truvace, 2026-11-12. /record/TRV-2026-2574 (accessed on the day you copy it). sha256 a0becb022942e955…
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-2574 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