Executive Summary

AI makes tasks faster, but faster tasks do not always create faster business outcomes. Most delays happen in approvals, queues, rework, and handoffs rather than in the work itself. AI process redesign focuses on removing those delays before automating the task. That is where AI creates measurable business value instead of just saving individual time.

Everyone says AI saves time. Fewer people ask which time it saves.

That distinction matters because most organisations measure productivity at the task level while customers experience performance at the process level. AI can write, classify, summarise, and respond in seconds, yet a customer request can still spend days sitting between teams, waiting for an approval, or returning for a correction. The work became faster, but the outcome did not.

Everyone says AI saves time. Fewer people ask which time it saves. 

That distinction matters because most organisations measure productivity at the task level while customers experience performance at the process level. AI can write, classify, summarise, and respond in seconds, yet a customer request can still spend days sitting between teams, waiting for an approval, or returning for a correction. The work became faster, but the outcome did not. 

This is the mistake many AI projects make. They optimise the visible work without redesigning the invisible waiting around it. The result is impressive demonstrations, enthusiastic teams, and dashboards showing minutes saved, while the number the business actually cares about, cycle time, turnaround time, or customer response time, barely moves. AI process redesign begins by measuring both clocks before deciding where AI belongs.

This is the mistake many AI projects make. They optimise the visible work without redesigning the invisible waiting around it. The result is impressive demonstrations, enthusiastic teams, and dashboards showing minutes saved, while the number the business actually cares about, cycle time, turnaround time, or customer response time, barely moves. AI process redesign begins by measuring both clocks before deciding where AI belongs.

The Time Came Back. Nobody Was Told What to Do With It.

The Time Came Back. Nobody Was Told What to Do With It.

BCG's fourth annual AI at Work survey, published 3 June 2026 from 11,749 workers across 14 markets, found that 42% of frontline employees who use AI regularly save at least a full working day every week. Frontline means white-collar staff without managerial responsibility; regular means daily or several times a week. It is self-reported, so treat it as direction rather than measurement.  

BCG's fourth annual AI at Work survey, published 3 June 2026 from 11,749 workers across 14 markets, found that 42% of frontline employees who use AI regularly save at least a full working day every week. Frontline means white-collar staff without managerial responsibility; regular means daily or several times a week. It is self-reported, so treat it as direction rather than measurement. 

The same survey found that 66% of the people saving that time get limited or no guidance on what to do with it.

The hours came out of the tasks and went nowhere, because nobody redesigned the process the tasks sit inside. A saving that is never re-planned at the level of the process is a personal result, not a business one.

An hour saved by everyone and planned by no one leaves the organisation exactly where it was.

The same survey found that 66% of the people saving that time get limited or no guidance on what to do with it.  

The hours came out of the tasks and went nowhere, because nobody redesigned the process the tasks sit inside. A saving that is never re-planned at the level of the process is a personal result, not a business one.

An hour saved by everyone and planned by no one leaves the organisation exactly where it was.

Every Process Runs on Two Clocks

The first clock is touch time: the minutes somebody spends working on it. The second is elapsed time: request to result, waiting included.

 Automation shortens the first clock, which in most processes is the smaller number by a wide margin. The gap between the two is where the days live, and four things usually account for it:  

Every Process Runs on Two Clocks

The first clock is touch time: the minutes somebody spends working on it. The second is elapsed time: request to result, waiting included.

Automation shortens the first clock, which in most processes is the smaller number by a wide margin. The gap between the two is where the days live, and four things usually account for it:

Where the wait comes from Four sources · one process
01 Back of the line

A handoff

The item joins a queue behind everything already at the next desk.

Waits on Other people’s work
02 Batched

An approval

Somebody signs weekly or in batches, so items wait on a calendar, not on a decision.

Waits on The gate opening
03 Sent back

A rework loop

One wrong field sends the item back to the bottom of the queue.

Waits on A whole second pass
04 Blocked

A dependency

Nothing moves until something arrives from elsewhere, and nobody is measured on when it does.

Waits on Nobody in particular

None of the four is typing. All four are structure: who does what, in what order, with whose approval, and by when. That is what workflow means, and why a faster typist fixes none of them. McKinsey put it plainly in August, describing the organisations getting a return as those that "fundamentally redesign workflows that are enabled by AI rather than insert AI into existing ones."

None of the four is typing. All four are structure: who does what, in what order, with whose approval, and by when. That is what workflow means, and why a faster typist fixes none of them. McKinsey put it plainly in August, describing the organisations getting a return as those that "fundamentally redesign workflows that are enabled by AI rather than insert AI into existing ones."  

A Faster Broken Process Is Not a Neutral Outcome

Automating a bad process, the saying goes, only makes the badness happen faster. That is close, and the precision matters, because it is the whole difference between automation and AI process redesign. Speeding up a step is harmless when that step is the constraint, and harmful when it feeds a constrained one, because you are then filling a queue faster than it drains.  

A Faster Broken Process Is Not a Neutral Outcome

Automating a bad process, the saying goes, only makes the badness happen faster. That is close, and the precision matters, because it is the whole difference between automation and AI process redesign. Speeding up a step is harmless when that step is the constraint, and harmful when it feeds a constrained one, because you are then filling a queue faster than it drains. 

The invoice automation did not save four hours a week. It moved them into the approval queue, where they stopped being work and became waiting. Waiting is invisible in a way work is not. No timesheet shows it, no dashboard counts it, and it belongs to the customer. That is why the project was reported as a success while the number did not move.

The invoice automation did not save four hours a week. It moved them into the approval queue, where they stopped being work and became waiting. Waiting is invisible in a way work is not. No timesheet shows it, no dashboard counts it, and it belongs to the customer. That is why the project was reported as a success while the number did not move. 

Where AI Process Redesign Actually Starts

Once you can see the gap, the redesign has somewhere to go. In our own Align sessions the argument worth having is almost never about which tool to buy, but about which of these three a team will change. 

Where AI Process Redesign Actually Starts

Once you can see the gap, the redesign has somewhere to go. In our own Align sessions the argument worth having is almost never about which tool to buy, but about which of these three a team will change.

The subtraction

The handoff you can delete

Every handoff costs a queue. Some exist only because the second desk was checking something the first can now be shown. Move that check upstream and the handoff goes rather than gets faster.

A handoff that survives should be there because somebody decided it should be.

Delete it, don’t speed it up 01 / 03
The rhythm

The approval you can re-time

Most approval delay is not decision time, it is batching. A weekly sign-off adds half a week to everything, however fast the approver thinks. Change the rhythm instead: daily, or on a threshold with a spot check.

The question is not whether the approver is fast, but how often the gate opens.

Cadence beats speed 02 / 03
The loop

The rework loop you can close

A one-in-five return rate does not add 20% to elapsed time. It adds a whole second pass to a fifth of the volume, at the back of the queue. This is the loop AI is genuinely good at closing, by catching the missing field at entry rather than at review.

Fixing an error where it is made is a redesign; fixing it faster where it is found is not.

Catch it at entry, not at review 03 / 03

This is the work the Align stage of our AI Success Workshop is built around. Vision Academy helps organisations answer three questions in order, how to start, how to implement and how to succeed. This post is about the first. Teams bring their own candidate processes and score them on the AI Impact Matrix, impact against feasibility, until the room can repeat one prioritised list back without arguing. It sits one level below the three decisions a leader cannot delegate: that post asked who decides, this one what they are looking at.

This is the work the Align stage of our AI Success Workshop is built around. Vision Academy helps organisations answer three questions in order, how to start, how to implement and how to succeed. This post is about the first. Teams bring their own candidate processes and score them on the AI Impact Matrix, impact against feasibility, until the room can repeat one prioritised list back without arguing. It sits one level below the three decisions a leader cannot delegate: that post asked who decides, this one what they are looking at.  

Run Both Clocks on One Process This Week 

Twenty minutes, no budget, no vendor. Take the process your AI project is aimed at.

Run Both Clocks on One Process This Week  

Twenty minutes, no budget, no vendor. Take the process your AI project is aimed at.

The four-line audit Four steps · one afternoon
01 01Touch time

Write down the touch time.

The minutes people actually spend on one item, end to end. Ask the people who do the work, not the people who own it. The two answers differ, and the first is right.

02 02Elapsed time

Write down the elapsed time.

Pull the last twenty items, measure request to result in calendar hours, and take the median.

03 03The gap

Subtract, and mark where the difference sits.

The gap is the waiting, and it is never spread evenly. Name the two places holding most of it.

04 04The test

Check what your AI project shortens.

If it shortens only the touch time, and the touch time is the small number, you have a productivity project.

Fine thing to buy. Fund it as one.

Two numbers before any budget

If the gap is small, you have a good automation candidate. If it is large, the tool was never going to be the thing that moved the number, and you have saved yourself a pilot that everyone except the customer would have called a success. 

If the gap is small, you have a good automation candidate. If it is large, the tool was never going to be the thing that moved the number, and you have saved yourself a pilot that everyone except the customer would have called a success.

Don't Automate It Yet. Time It First! 

Don't Automate It Yet. Time It First! 

The organisations getting a return from AI are not the ones with better tools. They are the ones who saw that most of a process's duration was waiting rather than working, changed the structure that produced the waiting, and put AI where it made the new structure possible. That is AI process redesign. It starts with the waiting, not the work, and another pilot will not make that decision easier.

The organisations getting a return from AI are not the ones with better tools. They are the ones who saw that most of a process's duration was waiting rather than working, changed the structure that produced the waiting, and put AI where it made the new structure possible. That is AI process redesign. It starts with the waiting, not the work, and another pilot will not make that decision easier. 

The Align stage of the AI Success Workshop works your own candidate processes down to a prioritised AI Impact Matrix: the ranked shortlist, first process circled, the number it should move beside it. Workshops run across Asia, with dates by region. If you would rather start smaller, we wrote about which strength to point AI at first, the same question from the other end.

Start with one process or reach us here! 

Start with one process or reach us here!

Need a practical AI learning pathway for your team?

Vision Academy helps teams move from AI awareness to hands-on solution building and structured transformation planning.

Contact Vision Academy

Copyright © 2026 Vision Academy. All rights reserved.

Copyright © 2026 Vision Academy. All rights reserved.

Built with