A device designed to get out of the way.
The UPS Ring Scanner is a wearable Bluetooth barcode scanner worn on the finger. Its design intent is hands-free scanning: drivers can carry packages, open doors, and move through a stop without setting anything down to scan. Paired with the DIAD, it is intended to reduce the physical and cognitive load of high-volume delivery.
We were asked to evaluate how well the device delivers on that promise — and where it falls short in real delivery conditions.
Moderated testing + heuristic evaluation.
We recruited active UPS delivery drivers across a range of experience levels and observed them completing representative delivery tasks using the Ring Scanner alongside the DIAD. Sessions were moderated but non-interventional: we watched what drivers did naturally, noted friction, and collected direct quotes.
Moderated Task Testing
Participants completed realistic scanning scenarios in a simulated package car environment. We observed first-attempt scan success rates, confirmation-checking behavior, and the conditions under which drivers abandoned the Ring Scanner in favor of the DIAD.
Heuristic Evaluation
Applied Nielsen's 10 heuristics post-session to frame findings against established usability standards. Severity rated 1 (cosmetic) to 3 (major barrier). Cross-referenced against participant behavior and direct quotes.
The trust deficit.
The single most significant finding from testing was not a broken feature. It was a behavioral pattern: drivers consistently checked the DIAD screen after using the Ring Scanner to confirm a scan had registered, even when the Ring Scanner produced its standard vibration and audio feedback.
"Sometimes I feel the buzz but then I look anyway just to make sure."
Driver, observed during task testingThis double-check behavior directly negates the time-saving intent of the hands-free design. A driver who scans with the Ring Scanner and then looks at the DIAD has added a step to the workflow rather than removed one. The efficiency gain evaporates.
"I learned to hold my hand a certain way. It took a while to figure out."
Driver, describing scan positioning techniqueExperienced drivers had developed personal techniques to improve scan reliability. These workarounds masked the underlying problem during testing with experienced users and represent a hidden onboarding cost for newer drivers.
"By the afternoon I just take it off. It starts to bother me."
Driver, end-of-session debriefPhysical discomfort accumulated over a shift for several participants, leading them to remove the device and revert to the DIAD. A tool that drivers choose to stop using mid-route is not delivering its value.
Where the device breaks down.
Severity 3: major barrier disrupting primary workflow. Severity 2: meaningful problem that should be addressed. Severity 1: cosmetic or minor.
Vibration and audio feedback are not distinct or reliable enough to eliminate double-checking behavior. Drivers verify scans on the DIAD regardless, adding steps instead of removing them.
Bluetooth disconnections during high-pressure stops create disproportionate delays. Drivers are uncertain whether to wait for automatic reconnection or intervene manually.
Read accuracy drops significantly in low light, at non-ideal angles, and on damaged or side-placed barcodes. Drivers developed personal positioning techniques to compensate.
Multi-package commercial stops are where the Ring Scanner delivers the most value and where failures are most disruptive. A disconnect or miss at a 20-package stop can cascade into route delays.
Several drivers discovered a dead Ring Scanner mid-route rather than receiving adequate warning. Battery status is not surfaced proactively on the DIAD.
Transitioning back to the DIAD when the Ring Scanner fails requires reorienting to the workflow and re-establishing context. Several drivers chose not to use the Ring Scanner at all on certain stop types to avoid this cost.
Heat and pressure buildup during extended wear leads some drivers to remove the device mid-route. Limited sizing options compound the problem for drivers outside the default fit range.
Rebuilding driver trust.
The largest opportunity is not fixing individual features. It is making the Ring Scanner reliable enough that drivers stop second-guessing it. A driver who trusts that the buzz means the scan worked captures the full efficiency gain the hands-free form factor was designed to deliver.
-
1Strengthen scan confirmation feedback
Implement distinct vibration patterns for success vs. failure, a clear audible tone that works in noisy environments, and a peripheral LED indicator. The confirmation should be unambiguous without requiring the driver to look at either device.
-
2Make connection status visible and actionable on the DIAD
Surface Ring Scanner connection status prominently on the DIAD screen. When a disconnection occurs, provide a clear, fast re-pairing sequence rather than leaving drivers to wait or guess.
-
3Provide scan positioning guidance during onboarding
Drivers currently discover optimal scan technique through trial and error. Explicit onboarding training on angle, distance, and lighting conditions would reduce early-use failure rates and shorten the trust-building period.
-
4Surface battery level proactively on the DIAD
Trigger a clear battery warning at a threshold that gives drivers enough time to plan. Do not rely solely on the Ring Scanner's own indicator, which is easy to miss during active delivery.
-
5Ensure sizing options are available and accessible
Drivers outside the default fit range experience more frequent discomfort and device removal. Making multiple sizes available and ensuring drivers know how to request them would extend active wear time across a full shift.
-
6Smooth the transition back to the DIAD
When a driver switches from Ring Scanner to DIAD mid-stop, the DIAD should maintain workflow context. Minimizing reorientation time makes the fallback less costly and reduces drivers' incentive to avoid the Ring Scanner entirely.
Test Plan
UPS Ring Scanner Usability Test Plan
Findings
UPS Ring Scanner Usability Testing Findings