aceModerate evidence
Published recordLaborGood Space
More
Thriving with AI: How Employee AI Readiness Translates into Sustainable Work Behavior Through Service Innovation in Hospitality and Tourism Industry
- Truvace record
- TRV-2026-2645raw data (JSON)
- Version
- v1Published
- First published
- Evidence type
- Survey
- Sources
- 1 sourcePeer-reviewed
- sha256
- bd8dca53bb6d…check it
Artificial intelligence is fundamentally reshaping work in hospitality and tourism, yet limited research has examined how employees’ AI readiness is associated with psychological and behavioral outcomes with sustainability implications. Drawing on Conservation of Resources Theory, this study investigates the relationships between employee AI readiness, digital thriving at work, service innovation behavior, and sustainable work behavior, with particular attention to the mediating roles of digital thriving and ser…
The gain
In a survey of 482 employees at five-star hotels and travel agencies, higher AI readiness went with more digital thriving and service innovation, and the model explained 74% of the variance in sustainable work behavior.
What this doesn’t fix
The study used a cross-sectional design and self-reported data, so it cannot establish causation and needs longitudinal, multi-source testing across other contexts.
Sources
1 on file- Societiesdoi:10.3390/soc16100329
Cite this record
v1Truvace Impact Record TRV-2026-2645, v1: “Thriving with AI: How Employee AI Readiness Translates into Sustainable Work Behavior Through Service Innovation in Hospitality and Tourism Industry.” Truvace, 2026-11-12. /record/TRV-2026-2645 (accessed on the day you copy it). sha256 bd8dca53bb6db858…
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-2645 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.