A consultant cuts a number by 30%, presents the slides, and leaves. Three months later, the number is back where it started.
I have watched that version many times, and I have been the consultant in it. I have also been the one whose fix was still running long after I was gone. The difference showed up in how the fix got built.
The diagnosis: leadership was reading status, not time
The team ran the path to production at a large enterprise. As usual, the process involved other specialized teams such as security, infrastructure, and cloud. One application took more than a year to get through it. Nobody inside the pipeline knew that, and everybody was doing their job.
No single step was wrong. Whoever you asked had a good reason for their part. The time went somewhere else: the application sat, finished with one step, waiting for the next team to pick it up. Some of it also sat after somebody had taken it, before anything actually moved. Nothing followed it across the whole journey. Each team’s tools showed their own steps. The waiting between them belonged to no one, so no one measured it.
Leadership saw boards full of work in progress and read it as fine. There was nothing saying “in progress, blocked nine days, because two teams each think the other one moves next.”
The countermeasure: build the seeing, do not deliver the map
I could have mapped that alone and handed in a report. Faster for me. It would have just ended up buried in a folder.
So I built the map with the team. We walked one real application from inception to go-live. For each step, we collected when the request arrived in the queue, when somebody actually started, and when it was done. Nobody could hand me those numbers. I assembled them from tickets, old email threads, and conversations at people’s desks. The year disappeared between arrival and start, and inside the steps themselves.
The data was incomplete, and I said so loudly. You do not need perfect numbers to redesign a process. You just need enough to see the shape of the waste. That was already obvious to everyone.
The first morning of that workshop was resistance. Plan for that. Nobody enjoys a chart that says their work took a year, so they explain, then justify, then somebody says it could not have gone another way. Do not argue with the explanations. Arguing hardens them. Instead, ask what the step would look like if you designed it from scratch today.
The situation turns when one person stops defending the old flow and starts drawing the new one.
The case: what changed in the room
They got rid of redundant checks. The approval step no longer waited for architecture review: it started at intake and ran alongside everything else.
They gave each handoff a clear owner, and they wrote their own definitions of ‘ready’ and ‘done’ for every stage.
Then they set their own target: cut lead time by at least half.
That is the part everyone quotes back at me, and it is the least interesting thing that happened.
By the end, the question had moved from who is busy to how long this takes. Blockers stopped hiding inside “in progress” and surfaced where a leader could act on them. People who had argued for months about better communication started talking about handoffs and dependencies. All because they finally saw the flow drawn on a digital wall.
I left instruments behind. A board that shows waiting, not just status. Indicators with a name against each one. The habit of walking to the actual work when something breaks. Those are not the fix. They keep the seeing alive once I am gone.
On the last day, they were the ones pointing at the next thing to fix. A fix is a number that improved while you were in the room. A capability is a team that spots and clears its own next bottleneck once you are not. What I can tell you is what changes when the team builds the map instead of receiving it, and it is not subtle.
Your AI tools made the coding faster. They did nothing to help anyone see where the work actually waits. You cannot buy that capability. You build it in a room, with the people who do the work.
Try this question on your last transformation. Who noticed what was wrong next, and could they say it out loud? Do not ask whether the number moved. Everybody’s number moves while the money is being spent.
Reply and tell me what you found.
A longer version of this case was published on LeadDev in August 2026: How to redesign a broken delivery flow.