TRV-2026-2042Certified recordPeer-reviewed

AI adoption and employees' physical and cognitive ergonomic outcomes in the information technology sector: The mediating roles of trust in ai and workload

BackgroundThe rapid adoption of artificial intelligence (AI) in the information technology (IT) reshaping the work design, with significant consequences for employee well-being and ergonomics. While AI enhances efficiency through task automation, its influence on workload dynamics and ergonomic consequences remains not sufficiently understood, particularly in emerging economy contexts.ObjectiveGrounded in the Job Demands-Resources (JD-R) framework and informed by Sociotechnical Systems Theory, this study investi…

Labor · Good Space — documented gain · certified 2026-10-20 · v1 · article view · machine-readable

Current reading — gain

Among IT professionals in India, greater AI adoption is associated with higher trust in AI and lower workload, which in turn is linked to less physical discomfort and cognitive fatigue.

What this doesn’t fix

The study frames AI as simultaneously a job resource and a source of new job demands, so the ergonomic benefits depend on trust and workload rather than following automatically from adoption.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-2042, v1: “AI adoption and employees' physical and cognitive ergonomic outcomes in the information technology sector: The mediating roles of trust in ai and workload.” Truvace, 2026-10-20. /record/TRV-2026-2042 (accessed at citation time). sha256 f30b40b5d045cb15…

Calibration history

Every change to this record since certification, in the open. None yet — the reading has held since it entered the record.

  1. Certifiedv1f30b40b5d045…

    Certified into the record

Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-2042 and hash it yourself — for example shasum -a 256 on the saved canonical field. The result must equal content_hash, and each version’s text ends with prev:followed by the prior version’s hash (version 1 chains to 64 zeros). If a single character of any version had been altered since certification, the chain would not reproduce.