TruaceTracing the truth around AITuesday, July 21, 2026
TRV-2026-0400Certified recordPeer-reviewed

From pilots to decision systems: embedding generative AI into strategic decision-making through a socio-technical and governance lens

Generative AI (GAI) promises superior analytics and agility in strategy work, yet organisations struggle to move beyond pilots towards routinised decision inputs. This study investigates how GAI becomes embedded in strategic decision-making (SDM) through a qualitative single-case analysis of a global multi-brand group, based on 27 semi-structured executive interviews triangulated with internal documents and industry reports. Structured inductive coding yields a process model identifying enablers, leadership-driv…

Policy · P Space — documented harm · certified 2026-07-20 · v1 · article view · machine-readable

Current reading — problem

Organizations attempting to embed generative AI into strategic decision-making struggle to move beyond pilots due to hallucination risks, prompt-engineering deficiencies, data readiness gaps, and privacy or IP concerns.

What this doesn’t fix

Findings derive from a qualitative single-case analysis of one global multi-brand group, limiting generalizability beyond that organizational context.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-0400, v1: “From pilots to decision systems: embedding generative AI into strategic decision-making through a socio-technical and governance lens.” Truvace, 2026-07-20. /record/TRV-2026-0400 (accessed at citation time). sha256 e98911e58af2412a

Calibration history

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

  1. Certifiedv1e98911e58af2

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