Recently I had the opportunity to rethink a business process that had existed for years.
Like many mature organizations, the process had accumulated additional reviews, handoffs, and checkpoints over time. Every one of those steps had a good reason for existing once. No one intentionally designs inefficient systems. They evolve.
The original assumption was simple: another review should improve quality.
Instead of accepting that assumption, I wanted to ask a different question. Was this review actually adding value, or was it simply delaying work?
After studying the workflow, it became clear that the people performing the work already possessed the greatest understanding of the project. Every additional handoff forced someone else to reconstruct information that already existed in someone else's head. That reconstruction took time. It also created unnecessary communication.
Rather than adding another checkpoint, ownership stayed with the people who understood the work — until it was genuinely ready to move forward.
The Old Way
Many handoffs. Lost time. Lost clarity.
- More delay — work sits in queues, feedback comes too late
- Lost knowledge — context fades with every handoff
- More friction — more questions, more rework
- Lower quality at the next step — downstream teams get incomplete information
The New Way
Clear ownership. Faster flow. Better results.
- 30–60 minutes saved per item, on average
- Better communication — questions happen sooner, while context is fresh
- Less friction — fewer rejections, fewer outbursts
- Higher quality handoffs — complete information for downstream teams
Every handoff transfers work. Very few handoffs transfer understanding.
The measurable improvement was relatively small. Average processing time decreased by roughly thirty to sixty minutes per item. On paper, that's a respectable improvement, but not a dramatic one.
Something much more interesting happened underneath that number. Communication improved. Questions happened sooner. People weren't waiting as long for feedback. Ownership became clearer, and the downstream team received more complete information. Even the number of emotionally charged conversations decreased, because issues were identified while the work was still fresh.
None of those improvements appeared on the dashboard. They were probably the most valuable outcome of the whole project.
30–60 min
Saved per item
Faster
Communication
Clearer
Ownership
More
Capacity
Healthier
Culture
Observation
The greatest improvements weren't measured in minutes. They were measured in communication, ownership, and reduced friction. When the people closest to the work own it all the way through, everyone downstream benefits.
This project changed how I think about process improvement. For years I looked for bottlenecks. Now I also look for unnecessary handoffs.
Every handoff introduces delay. Every delay separates people from the context they need to solve problems quickly. Sometimes improving a process doesn't require another approval. Sometimes it requires trusting the people who already know the work best.
One of the biggest lessons I've learned while studying systems thinking is that eliminating unnecessary work doesn't automatically increase organizational throughput. What it does create is capacity. Capacity gives an organization choices — room for better communication, shorter feedback loops, clearer ownership. Eventually those improvements compound into something much larger than the original time savings.
Continuous improvement is rarely about giant breakthroughs. More often it's about asking one uncomfortable question.
Field Note
If we were designing this process today, would we build it this way?
Current Hypothesis
Eliminating unnecessary handoffs doesn't automatically increase throughput. What it creates is capacity — and capacity is what makes room for better communication, clearer ownership, and faster feedback.
Not a conclusion — a working idea, revisited as evidence comes in.