50/100

Moderate evidence

GainPublished recordLaborGood Space

From AI adaptation to innovation: how leader AI crafting shapes employee innovative behavior

Truvace record
TRV-2026-2677raw data (JSON)
Version
v1Published
First published
Evidence type
Survey
Sources
1 sourcePeer-reviewed
sha256
d880652ae7dc…check it

As artificial intelligence reshapes work, organizations face the challenge of helping employees move beyond routine technological adaptation toward innovation. Although prior research has shown that leader AI crafting facilitates employees' adaptation to AI, whether and how it promotes employees' innovative behavior remains unclear. Drawing on social cognitive theory, this study examines how leader AI crafting relates to employees' innovative behavior through AI self-efficacy and when this relationship becomes s…

The gain

In a two-wave survey of 294 full-time employees who use AI at work, leader AI crafting was associated with higher innovative behavior (b = 0.45), partly through greater AI self-efficacy.

What this doesn’t fix

AI self-efficacy and innovative behavior were measured in the same wave, innovation was self-reported, and the sample came mainly from internet technology firms in three eastern Chinese cities, limiting causal and general conclusions.

Sources

1 on file
  1. Frontiers in Psychologydoi:10.3389/fpsyg.2026.1847344
    Peer-reviewed2026-07-09

Cite this record

v1

Truvace Impact Record TRV-2026-2677, v1: “From AI adaptation to innovation: how leader AI crafting shapes employee innovative behavior.” Truvace, 2026-11-12. /record/TRV-2026-2677 (accessed on the day you copy it). sha256 d880652ae7dc0d25…

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. Publishedv1d880652ae7dc…

    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-2677 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.