68/100

Moderate evidence

GainPublished recordScienceGood Space

Augmentation or automation? A dual-path model of GenAI usage motivations and employee creativity

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

Purpose Generative artificial intelligence (GenAI) can both enhance and constrain employee creativity, yet the mechanisms underlying these divergent effects remain unclear. This study examines how augmentation and automation motivations for GenAI usage shape employee creativity through distinct knowledge-processing mechanisms. Design/methodology/approach Drawing on dual-process theory and self-regulation theory, we distinguish augmentation and automation motivations for GenAI usage and propose distinct cognitive…

The gain

A multi-wave, multi-source field survey and scenario experiment found that employees who used generative AI to augment their own thinking were more creative, through better integration of knowledge.

What this doesn’t fix

The authors note that augmentation and automation motivations may coexist and vary across tasks and use episodes, and that other individual differences and work contexts remain unexamined.

Sources

1 on file
  1. Internet Researchdoi:10.1108/intr-07-2025-1110
    Peer-reviewed2026-11-12

Cite this record

v1

Truvace Impact Record TRV-2026-2900, v1: “Augmentation or automation? A dual-path model of GenAI usage motivations and employee creativity.” Truvace, 2026-11-14. /record/TRV-2026-2900 (accessed on the day you copy it). sha256 83d178d41783e867…

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

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