Truace
Subscribe
68/100

Moderate evidence

ProblemPublished recordLaborProblem Space

Full story
More
Export record JSONEmailLinkedInX

When AI supervises humans: how AI management triggers self-objectification and undermines proactive behavior

Truvace record
TRV-2026-2547raw data (JSON)
Version
v1Published
First published
Evidence type
Controlled or validated comparison
Sources
1 sourcePeer-reviewed
sha256
93d755bcf4b3…check it

Purpose The integration of artificial intelligence (AI) into daily operations and management has become increasingly prevalent within the hospitality industry. However, the impact of transitioning managerial roles from humans to AI on hotel employees’ cognition and work behavior remains an unresolved issue. This paper aims to examine the relationship between AI management and proactive work behavior by identifying self-objectification as a mediator and AI identity as a moderator. Design/methodology/approach This…

The problem

In two scenario experiments with 328 hotel employees, those managed by AI were only half as likely to engage in proactive work behavior as those managed by humans.

What this doesn’t fix

The findings come from two scenario-based experiments rather than observation of hotel employees working under real AI managers.

Sources

1 on file
  1. International Journal of Contemporary Hospitality Managementdoi:10.1108/ijchm-11-2025-1679
    Peer-reviewed2026-07-28

Cite this record

v1

Truvace Impact Record TRV-2026-2547, v1: “When AI supervises humans: how AI management triggers self-objectification and undermines proactive behavior.” Truvace, 2026-11-12. /record/TRV-2026-2547 (accessed on the day you copy it). sha256 93d755bcf4b378e0…

Change history

1 version

Every change made to this record since it was first published, and why. Nothing has changed since it went up.

  1. Publishedv193d755bcf4b3…

    Certified into the record

Check this record hasn’t been altered

Check this record hasn’t been altered
How to check it yourself, without trusting this page

Download any version from /api/record/TRV-2026-2547 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.