Faster Saws (Every Step Got Faster, and the Customer Still Waits)
The Problem
Every team in the process has an AI story it's proud of. Verification went from half a day to twenty minutes. Pricing went from an afternoon to a few minutes. Reconciliation runs overnight now, in seconds. And the customer waits exactly as long as they did last year. The time was in the waiting between the steps, and nobody's AI story touched that. The Tuesday meeting. The twice-a-week payment run. The sign-off somebody added after a mistake years ago. The file sitting in a queue until the next person gets to it. Sensible answers to problems that no longer exist. That's organizational debt, and AI doesn't pay it down by itself. You can pay off every bit of your technical debt and still owe all of it.
The Principle
Faster stations aren't a faster factory. Walk one real order through the business, color the work blue and the waiting red, and the red wins by a mile almost every time. So stop speeding up the stations and redesign how the work moves between them. Start from zero. If you built this process today, with agents in it from the first minute, what has to be true? Which of those things genuinely needs a person to decide? Let the work move itself everywhere else, and bring people together only at those few decision points. Engineers call it orchestration. In plain words, it's deciding who waits for whom, on purpose. It rarely needs a new tool. The hard part is getting seven teams to agree to work differently.
4 Steps to Take Action
- 1
Follow one order end to end
Pick one real customer order from last month and pull every timestamp from every system it touched. Not a sample: one order, all the way through.
- 2
Color it blue and red
On a wall, blue for anyone, person or agent, actually doing work, and red for waiting. Add up each color. Show it to the team leads together, and let them read it before anyone talks.
- 3
Ask what has to be true
Wipe the board. If you started this business today, what has to be true for the order to be done? Then ask which of those needs a person to decide. Everything else is moving the file.
- 4
Pilot one pod
A small cross-team group, one agent following each order instead of each team, and one short daily meeting where the people who decide, decide. A few weeks, a few dozen orders, everything else unchanged.
💡 Inspired By
Chapter 11 of The Second Factory, "Twenty-Three Days." And Eliyahu Goldratt's The Goal: every system has one constraint, and speeding up anything else just piles up work in front of it.
This is what Analytics Pitfalls & Principles is about: people helping people.
In Practice
A seller sold his 1957 Ranchero through ClassicMotors and got paid twenty-three days after he first called. He was thrilled with the price. He called four times to ask where his money was. Everybody was very nice. Nobody could tell him. The auction itself takes a week. So Nora Berg asked the data team to pull everything about that one car: every system, every person who opened the file, every timestamp. It lived in seven systems that didn't talk to each other, and two of the handoffs had happened by email. She took blue and red sticky notes up to the catwalk. Blue for work, red for waiting. Verification: twenty minutes, then five days waiting for an inspector. Inspection: half a day, then four days waiting for the Tuesday pricing meeting. Pricing: a few minutes, then three days waiting for Monday's auction lists. The payout, matched overnight by an agent, then two days waiting for the twice-weekly payment run. Outside the auction: sixteen days, about a day and a half of them blue. Every team on that wall was faster than a year ago. Some were ten times faster. A year ago, the median wait had been twenty-four days. "We all bought faster saws," said the man who ran transport. The payment run was twice a week because that was how the bank file used to work. It hadn't worked that way for three years.
