Throughput, Without Disruption
- Mar 23
- 3 min read
Updated: Mar 24
How a Simple Add-On Delivered 10% Gains in Under a Month
March 2026

Most people wouldn’t expect this.
Most would not think that a simple accessory for their handheld scanner could improve throughput by 10% in under a month.
Not without new software.
Not without workflow redesign.
Not without retraining an entire workforce.
And yet—that’s exactly what happened.
This isn’t a story about transformation through disruption. It’s a story about what happens when you remove friction from work that’s already happening—and what that unlocks over time.
The Environment
The operation was a large, high-volume distribution environment where throughput isn’t just important—it’s everything.
Every process was already tuned. The WMS was proven. The workflows were established. The associates knew exactly what they were doing. Like most well-run operations, there wasn’t much appetite for change—especially the kind that risks slowing things down before making them better.
So when the idea of introducing something new came up, the bar was high. It had to work within the existing system, not against it.
A Different Approach to Improvement
Instead of asking, “How do we change the workflow?” the team asked a different question:
What if the workflow stays exactly the same—but the experience of doing it improves?
That’s where Six15’s ST1 Bluetooth® HUD came in.

Rather than replacing devices or reworking systems, the HUD simply moved the instructions from the handheld screen into the associate’s line of sight. Paired with a ring scanner, it allowed users to pick hands-free—without changing the underlying process at all.
Same system. Same workflow. Same work. Just a different way of interacting with it.

Some users found the display unfamiliar. Others described it as slightly uncomfortable at first. A few questioned whether it was actually helping or just adding something new to manage.
None of this was unexpected.
Any time you introduce a new way of working—even a small one—there’s a period where it feels like friction before it feels like progress.
What Changed
Around week four, the tone shifted.
The device stopped feeling like something extra and started feeling like part of the workflow. Movements became more natural. The constant back-and-forth between looking down at a device and back up to the task began to disappear.
Work started to flow. Users who were initially hesitant began to prefer the hands-free experience—especially in manual and batch picking environments.
The Result
Once the team moved past the adjustment period, performance was measured over time.
Throughput increased by more than 10% across the team.
This was not a short-term spike—it was consistent and repeatable.
Why It Worked
Before, every step required a small reset: look down, read, process, move, scan, repeat.
After, those interruptions were gone. Instructions stayed in view. Hands stayed free. Movement became continuous instead of stop-and-go.
The workflow didn’t change—but the experience did.
The Financial Reality
A 10% improvement translates to meaningful savings.
For an individual associate, this equates to roughly 0.8 hours saved per day, or more than $4,000 annually, at the national average hourly pay rate.
At scale, this can exceed $140,000 annually for a 30-user deployment, with a payback period of approximately four months.
What This Actually Means
Most operations don’t have a throughput problem—they have layers of small inefficiencies that compound over time.
This showed that removing those inefficiencies can unlock meaningful gains without major change.
Final Thought
Nothing about this required a major decision.
No system overhaul.
No operational reset.
No disruption to the floor.
Just a small change in how the work is experienced—and a measurable result that followed.
Because if this kind of gain is possible without disruption—without retraining, without replatforming—it naturally raises a different question:
Not whether it works.
But how long does it make sense to operate without it?