“Our process is too slow.”
90% of the time, that sentence is wrong. The process is not “slow”. The process is stalled. Work is just sitting there, untouched, in someone’s queue, waiting for someone with authority to look at it, answer a question, or approve an exception.
When we cut the lead time of a credit flow from 14 days to 7 days, we did not redesign the whole process. We didn’t “automate”. We didn’t throw more people at it.
We did one thing: we forced leaders to own the waiting time they were creating.
Where time actually disappears
In most service / back-office flows, the “work” time is tiny. Filling the form, checking a document, validating a number — that’s minutes.
The real delay is:
- waiting for clarification because input was incomplete,
- waiting for an approval that only one person is “allowed” to give,
- waiting because the person who should handle it is “on something more urgent”.
So your 14 days are not 14 days of work. They’re 13.5 days of nobody touching the file.
Leadership creates (or removes) that waiting time
This is the part that hurts a little.
Lead time balloons when:
- No one is clearly accountable for unblocking.
- Escalation is informal (“can you have a look when you can?”).
- People are juggling more work in progress than they can physically advance.
None of those are “process flowchart” problems. They’re management problems. They come from how leaders organise work, assign ownership, and control capacity.
You can standardise a form all you want. If an analyst still has to “chase legal” for 3 days to get a yes/no, your lead time will stay garbage.
What we actually changed to go from 14 → 7 days
Here’s what unlocked the improvement in the credit flow:
1. A single visible board of live files
We made work visible. Every file in progress, with owner, status, and age in days.
Suddenly you could see files on day 9, day 10, day 11 just sitting. No more “I thought Legal had it” or “I assumed Compliance replied”. That illusion died in 30 seconds.
Visibility kills excuses.
2. Daily unblock, not weekly status
We did a short daily review (15 minutes, not a meeting to chat nicely). The only questions were:
- Which files are stuck right now?
- Who can unblock them today?
- What do you need to unblock it?
This is different from “reporting progress”. We weren’t asking, “How are things going?” We were asking, “Who is going to move this file in the next 24h?”
That forces ownership.
3. Capacity protection
Before, people were overloaded “because the volume is high”. Classic excuse.
We set a WIP (work in progress) limit per analyst. You don’t get 23 files “in progress”. You get 5.
This sounds restrictive. It’s actually the opposite. You stop drowning. You finish work faster. And fewer things rot in the queue.
4. Escalation path that actually works
Before: “I sent Legal an email.” After: “If Legal doesn’t answer by tomorrow 10:00, it’s raised to X.”
That wasn’t a threat, it was clarity. We just said out loud what happens if someone becomes a bottleneck.
When everyone knows escalation is automatic and time-bound, people stop being a bottleneck.
The myth of ‘we just need better tools’
People love to believe that a new system will magically fix lead time. “If only we had workflow automation…”
No.
If your people can’t unblock a file in under 24h because nobody feels accountable, digitising the chaos won’t save you. You’ll just get prettier dashboards of the same waiting time.
If you’re serious about lead time, do this first
- Make all in-flight work visible with owner + age in days.
- Run a daily unblock review, not a weekly status update.
- Limit individual work in progress so things actually finish.
- Define a clear escalation rule and stick to it.
Do that before you map 47 swimlanes. Do that before you buy tooling.
Lead time is not about “process maturity”. It’s about how quickly leadership forces decisions to happen.
You don’t speed up the work. You stop letting it wait.