Home  ›  Articles

Adoption and Change

Why AI Projects Fail: Start With the Work and the People

Most AI projects fail for reasons inside the organization: the wrong problem, a broken process, no owner and too little say for the people who will use the tool. Fix those before you add another AI tool.

Shannon Phillips

October 30, 2026

Stacks of paper files and full in-trays on a desk beside a laptop
A team reviewing printed charts and reports around a meeting table

Innovation Readiness Assessment

A staff survey that shows, department by department, where work stalls.

Assess Your Organization

Key takeaways

Most AI projects fail for reasons in the organization, not in the model.

AI makes a working system faster and a broken one more confusing.

Name the problem without the word AI before you choose a tool.

Ask the people who do the work first. They decide whether a tool is used.

Judge an AI project by what changed in the work at 30 and 90 days.

Why AI Projects Fail: What the Research Shows

Team Collaboration Icon

Definition

AI project failure

An AI project fails when it is abandoned, never reaches daily use, or reaches daily use without changing a result the organization can measure.

93%

of Canadian business leaders surveyed said their organizations use AI in some form, up from 61% a year earlier

2%

said their organizations are seeing a return on their generative AI investments

AI Does Not Fix a Broken Process

Key idea

AI does not fix a broken operating model. Without a working system underneath, you are not transforming it. You are digitizing confusion.

The Five Causes Behind Most AI Project Failures

In practice. Before approving an AI project, ask for the problem in one sentence that does not use the word AI. If no one can write it, the project is starting from the tool.

Before AI, Start With Your People

Instead of

Choose a tool, then look for a use

Ask whether teams are using AI tools

Pilot with the most enthusiastic team

Count licences and logins

Try this

Start from a problem people name in their own work

Ask whether the organization is ready

Pilot with a team that will live with the result

Count what changed in the work

A leader talking with a small team standing in a circle, laptops closed

The people who do the work know where a tool would help.

What to Fix Before You Add Another AI Tool

1

Name the problem in plain words

Write one sentence: who has the problem, what it costs today in hours, errors or delays, and how you will know it is solved. Leave the word AI out of it.

2

Fix the process before you speed it up

Map the work as it is done today, remove the steps nobody needs and agree who owns the result. Then decide where a tool would help.

3

Ask the people who will use it

Bring three to five people who do the work into the choice. Ask where their time goes, what they would hand to a tool and what they would never trust a tool to do.

4

Measure before you change anything

Record how long the work takes and what it costs now. Without a baseline, nobody can show later what the tool changed. Count time before money: hours saved show first.

5

Test small, with the team that will keep it

Try the tool on one real task for a few weeks, with one owner, in the team that will use it every day. A test that works only for enthusiasts says little about everyone else.

6

Check use and results at 30 and 90 days

Agree the dates in advance. Look at whether people use the tool when no one is checking and what changed in the work. Then scale it, change it or stop it.

How to Tell Whether Your Organization Is Ready for AI

Before an AI project

The problem is written in one sentence without the word AI.

The process the tool will support has an owner and works without it.

People who do the work helped choose the tool.

There is a baseline for the time and cost of the work today.

The first test is small enough to finish in weeks.

Dates are set to check use and results at 30 and 90 days.

In the Age of AI, People Still Do the Work That Matters

Innovation Readiness Assessment

Measure Innovation Readiness in Every Department

Staff across every department assess process, people, projects and performance. Leadership receives a department-by-department view of where work stalls, with a prioritized 30- and 90-day action plan.

Frequently Asked Questions

Why do AI projects fail?

What is the AI project failure rate?

Why do AI pilots fail to scale?

What is the human side of AI adoption?

How do you prepare employees for AI?

How do you know if your organization is ready for AI?

Limited-time Q4 offer

Innovation Process Certification at 50% Off

Your team can build this on a real problem in our two-day Innovation Process Certification, for up to 10 people. Alberta organizations that book by 30 November pay half our medium business price.

About the author

Shannon Phillips, Co-Founder of Unbounded Thinking

Shannon Phillips

Co-Founder and Innovation Strategist

Designs structured innovation systems for enterprise organizations and helps leadership teams set priorities that reflect how the organization operates.

Start With a Free Individual Snapshot

The free Innovation Readiness Snapshot gives one person’s view of the same four areas in about five minutes, with a private summary of your results at the end.