How to work out why your AI investment isn't paying off

What it looks like

Your team uses AI regularly, and almost nobody could say what it is supposed to improve. Effort goes in without an agreed target, so there is no way to tell a good week from a bad one.

How to tell

Both of these are true:

• AI tools are part of normal work across the team, not a pilot running with a few volunteers.

• If you asked five people what AI is meant to improve this quarter, you would get five different answers, or none.

What to do first

Pick one business outcome AI is meant to move this quarter and write it somewhere the team sees it. If it cannot be said without the word AI, it is not the outcome yet.

What it looks like

Use is widespread and each person has worked out their own way of doing it. Nothing anyone has learned survives them leaving, and the same problem gets solved several times over in different corners of the team.

How to tell

Both of these are true:

• AI is in regular use across the team.

• There is no shared place where a way of working with it has been written down, and no routine where people show each other what they do.

What to do first

Ask the few people already doing this well to show the others what they actually do, inside real work rather than in a deck. Record it once so it outlasts them.

What it looks like

More is being produced and the work itself is not better. That is the point where AI starts costing more attention than it returns, because somebody still has to read all of it.

How to tell

Both of these are true:

• Output has clearly gone up since the team started using AI.

• Asked whether the work is better and not only faster, you would hesitate. Review takes as long as it used to, or longer.

What to do first

Agree what good looks like for one piece of work before it goes near an AI model, then judge what comes back against that rather than against how fast it arrived.

What it looks like

Workflows have genuinely been rebuilt, and the time that frees goes back into the same workload. The hard part is done and the return is being handed back.

How to tell

Both of these are true:

• Real steps have been removed or rebuilt, so at least one piece of work is genuinely done differently now.

• Nobody decided in advance where the freed hours would go, and the days feel the same as they did before.

What to do first

Decide where the next block of freed time goes before it arrives, and protect it. Time nobody has claimed is always reabsorbed by whatever is loudest.

What it looks like

The team is expected to use AI without both the skill and the room to build it. One of those can be bought quickly. Having neither is why capable people stall at the obvious uses.

How to tell

Both of these are true:

• Using AI is an expectation in the team, whether it was stated or just assumed.

• There is no time set aside to get better at it and no real training beyond a tool demo, so people are learning it in the gaps.

What to do first

Work out which of the two you are actually short of and fix only that one. If it is skill, an hour on real work beats a course. If it is time, take something away.

What it looks like

AI is being used heavily on top of workflows that have not changed shape. The tool is absorbing the friction the process should have lost.

How to tell

Both of these are true:

• Individuals use AI heavily inside their own tasks.

• The steps, handoffs, and approvals around those tasks are the same ones you had before AI arrived.

What to do first

Take one workflow and ask what it would look like if it had been designed with AI in it from the start, then change the steps rather than the tool.

What it looks like

There is an agreed answer to what AI is for, and almost nobody is acting on it. The thinking is ahead of the practice, which is the easier of the two problems to have.

How to tell

Both of these are true:

• You could state in one sentence what AI is meant to improve here, and colleagues would say the same thing.

• Day to day, use is thin, and it sits outside the work that matters most.

What to do first

Start with the people closest to the outcome you have already agreed, not the whole team. A small group using it deliberately will teach you more than everyone using it lightly.

What it looks like

Nobody has tracked where the freed time goes. Until somebody does, whether this is paying is a matter of opinion, and opinion is what gets budgets cut.

How to tell

This one shows up on a single observation:

• There is no record anywhere of what the hours AI freed up were spent on. If someone asked you to show the return this quarter, you would be reaching for an argument rather than a record.

What to do first

Take one team and one month and write down what the freed time was actually spent on. This needs one honest record, not a system.

What it looks like

The people are capable and the work has not been allowed to change around them. Capability with no permission to redesign anything turns into private workarounds.

How to tell

Both of these are true:

• There are people who are good at this and have the time to use it well.

• Nobody has the authority to change how a piece of work is done, so the improvements stay inside personal habits and never reach the process.

What to do first

Give one capable person explicit permission to change how a piece of work is done, and find out what they do with it.

What it looks like

This is early across the board rather than stuck in one place. That is a cheaper position than it looks, because nothing has to be undone first.

How to tell

All three of these are true:

• Use is light across the team.

• There is no agreed answer to what AI is meant to improve.

• No workflow has been rebuilt around AI yet.

What to do first

Choose one task somebody does every week and rebuild that one around AI. The first one tells you what the rest will cost, which is worth more than starting everywhere.