aceModerate evidence
Published recordLaborProblem Space
More
Augment or replace? AI implementation and employee job insecurity
- Truvace record
- TRV-2026-2606raw data (JSON)
- Version
- v1Published
- First published
- Evidence type
- Controlled or validated comparison
- Sources
- 1 sourcePeer-reviewed
- sha256
- 9879fd80e773…check it
Purpose This research aims to investigate how front-of-house artificial intelligence (AI) implementation (human replacement vs human augmentation) affects job insecurity among tourism and hospitality employees. Design/methodology/approach Three scenario-based experiments were conducted with hospitality and tourism employees from the United States and the United Kingdom. Data were collected via Prolific. ANOVA and PROCESS modeling were adopted to analyze the data. Findings The results demonstrate that AI implemen…
The problem
In three scenario-based experiments with US and UK hospitality and tourism employees, front-of-house AI increased job insecurity, and replacing staff produced more insecurity than augmenting them.
What this doesn’t fix
The findings come from scenario-based experiments with online participants recruited via Prolific, rather than from observation of workers whose employers have actually introduced AI.
Sources
1 on file- International Journal of Contemporary Hospitality Managementdoi:10.1108/ijchm-08-2025-1290
Cite this record
v1Truvace Impact Record TRV-2026-2606, v1: “Augment or replace? AI implementation and employee job insecurity.” Truvace, 2026-11-12. /record/TRV-2026-2606 (accessed on the day you copy it). sha256 9879fd80e77352b6…
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-2606 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.