Skip to main content

Why AI projects fail

Usually not because the model was weak — but because ownership was.

Night office meeting around a conference table beside a whiteboard of abstract process boxes
Your trail
Reading tools
Publication record
Author
Thierry Gilgen
Edition
1
Published
2026-07-15
AI assistance
Not recorded
Editorial review
Not recorded
Structured source record
No structured sources recorded. Inline citations are separate.
Edition change
Baseline recorded from existing publication
SHA-256
81b2ae26ef288ba67747c2fb5c4156912790b5c8adb4dcb2f55e8a7447d4536e

A checksum identifies the recorded text and metadata. It does not certify the truth of a claim or the contents of external links.

Thierry Gilgen. Why AI projects fail. Edition 1. 2026-07-15. https://www.thierry-gilgen-ict.ch/field-notes/why-ai-projects-fail

Edition history

Thierry Gilgen. Why AI projects fail. Edition 1. 2026-07-15. https://www.thierry-gilgen-ict.ch/field-notes/why-ai-projects-fail

When an artificial-intelligence project fails, the model often receives the blame.

It hallucinated.

It misunderstood the prompt.

It was too expensive.

It was not sufficiently accurate.

Sometimes those criticisms are correct. Models have limitations, and those limitations matter.

But many AI projects fail long before model quality becomes the decisive problem.

They fail because nobody truly owns the system.

The innovation team owns the experiment.

IT owns the infrastructure.

Legal owns the policy.

Security owns the restrictions.

A business unit owns the budget.

A consultancy owns the presentation.

A vendor owns the model.

And nobody owns the operational outcome.

This fragmentation is easy to ignore during a pilot. A small group can manually repair bad inputs, explain strange results, adjust prompts, and guide selected users through the process.

Then the project enters production.

Who monitors quality?

Who decides when the system is wrong?

Who approves changes?

Who responds when a provider alters its model?

Who owns the data pipeline?

Who understands the cost per completed business task?

Who has the authority to stop the system?

Who is accountable when humans begin trusting it too much?

Without clear answers, the project is not a system. It is a collection of unresolved responsibilities held together by enthusiasm.

AI introduces uncertainty into environments that organisations have traditionally tried to make deterministic. That does not make AI unusable. It makes operational ownership more important.

A serious AI product needs more than a model and an interface.

It needs defined decision rights, evaluation criteria, escalation paths, auditability, monitoring, cost controls, security boundaries, feedback loops, and an owner with both responsibility and authority.

It also needs an exit plan.

Can the organisation replace the provider?

Can it retrieve its data?

Can it reconstruct important outputs?

Can it continue operating if the preferred model becomes unavailable, unaffordable, or unsuitable?

These questions are not secondary governance concerns. They are part of the product.

A strong model can improve a well-owned system.

It cannot compensate for an organisation that has outsourced responsibility without noticing.

AI projects usually do not fail because intelligence was missing from the model.

They fail because ownership was missing from the organisation.

Read what comes next

Receive Thierry’s newsletter through Substack, or follow new Library volumes in your feed reader.

Leave a note in the margin

Your submission is stored privately until reviewed or deleted. Only an edited, accepted note can appear publicly. Do not include confidential information. Attribution is optional.