Lifsys / field note 01
printf 'thought -> action\n'
← BACK TO RESEARCH

01 / RESEARCH NOTE

Why AI projects fail

Move the operating result, workflow, and evidence boundary ahead of model selection.

PRIMARY-SOURCE CONTEXT / NOT LIFSYS PERFORMANCE OR ORIGINAL RESEARCH

PUBLISHER
RAND
YEAR
2024
EVIDENCE BOUNDARY
This is an estimate cited in RAND's 2024 exploratory analysis. RAND interviewed 65 experienced AI practitioners. Projects that only used pretrained language models through prompt engineering were outside the report's scope.
ESTIMATE + STUDY FRAMERAND / 2024
>80%ESTIMATED AI PROJECT FAILURE RATEESTIMATE CITED BY RAND
STUDY FRAME65

EXPERIENCED DATA SCIENTISTS + ENGINEERS

INDUSTRY INTERVIEWS
50
ACADEMIC INTERVIEWS
15
FIVE LEADING ROOT CAUSESUNRANKED
WRONG PROBLEM OR WORKFLOW
INSUFFICIENT DATA
TECHNOLOGY BEFORE PROBLEM
INSUFFICIENT INFRASTRUCTURE
PROBLEM BEYOND AI LIMITS
BOUNDARY / ESTIMATE AND STUDY FRAME REPORTED BY RAND, NOT A LIFSYS RESULT

PRIMARY-SOURCE FINDING

What the source establishes.

RAND reports that, by some estimates, more than 80 percent of AI projects fail.

This is an estimate cited in RAND's 2024 exploratory analysis. RAND interviewed 65 experienced AI practitioners. Projects that only used pretrained language models through prompt engineering were outside the report's scope.

LIFSYS ENGINEERING INTERPRETATION

Why the evidence matters.

Failure risk often starts before model selection. An unclear operating result, the wrong success measure, weak data, missing infrastructure, or poor workflow fit can make a technically capable model irrelevant to operations.

BUSINESS RELEVANCE

A prototype can work in isolation and still fail when it solves the wrong problem or cannot enter the real workflow.

DECISION IMPLICATION

The operating decision it changes.

Do not authorize a model build from a use-case slogan. Authorize a bounded integration test only after the result, decision owner, data boundary, and rollback path are visible.

OBSERVABLE ENGAGEMENT ARTIFACT

AI PROJECT ADMISSION RECORD / result statement, decision owner, workflow boundary, data readiness, success and failure measures, rollback path.

APPLY THE NOTE

Bring the evidence into the real system.

The first session bounds the result, constraints, and next engineering decision. It does not guarantee an implementation or outcome.

BOOK A WORKING SESSION