UPS DIAD V Usability Study

The device drivers depend on.

The UPS DIAD V (Delivery Information Acquisition Device) is the handheld scanner drivers carry on every route. They use it to scan packages, navigate stops, capture customer signatures, and flag delivery exceptions. It is the primary tool of their job, in their hands for hours at a stretch, across varied outdoor conditions.

We were asked to evaluate how well the device supports drivers doing this work. Rather than rely on a lab or a simulated task, we went to where the real work happens: a full delivery route, with an active driver, on a normal day.

Ride-along + heuristic evaluation.

The study combined two methods. First, we conducted a contextual observation ride-along, accompanying a driver on his route and watching how he interacted with the DIAD V in the field. No tasks were assigned. We observed what he did naturally, noted moments of friction, and collected direct quotes. Second, we applied Nielsen's 10 usability heuristics as a structured evaluation lens, rating each against what we observed.

What the driver said and did.

Three patterns emerged clearly during the ride-along. Each connects directly to a screen content or information density problem.

Stopping mid-route just to read the screen costs time and breaks the physical flow of the job. Screens packed with low-priority data make it hard to locate the relevant detail at a glance, forcing drivers to stand still and search.

Dense screen layouts push type sizes down to fit everything. The driver was physically compensating throughout the day, not because of a vision problem, but because the screen was asking him to read too much at once at too small a size.

Drivers are measured against tight delivery windows. Screens with too many elements require more reading and more decisions per interaction. Across hundreds of stops, that overhead adds up.

Ten heuristics, rated by severity.

Severity 3 indicates a major usability barrier that disrupts the primary task. Severity 2 indicates a meaningful problem that should be addressed. Severity 1 is cosmetic or minor.

Six changes, screen and software only.

All recommendations target screen content and layout. Hardware changes were out of scope for this engagement.

• 1
  Reduce information density on primary task screens

  Each screen should show only what the driver needs to complete the current action. Secondary data (route metadata, internal codes, system fields) should be hidden by default and accessible on demand.

• 2
  Increase font size on scan, signature, and stop confirmation screens

  Removing non-essential content creates room to increase type size without restructuring the layout. Larger type directly addresses the physical compensation observed during the ride-along.

• 3
  Clarify confirmation states with prominent visual feedback

  After a scan, signature capture, or stop completion, the screen should show a clear, full-size confirmation before advancing. Small status text is too easy to miss while moving.

• 4
  Simplify input fields to match driver mental models

  Fields that ask for system codes or internal identifiers should show plain-language labels. Where the physical QWERTY keyboard is available, text fields should default to it rather than forcing numeric-only input mode.

• 5
  Move the Signature confirmation button away from high-traffic screen areas

  Repositioning the on-screen Signature button reduces accidental taps during scanning. A brief confirmation step before finalizing prevents deliveries being incorrectly logged as signed.

• 6
  Add an in-screen quick reference for edge-case procedures

  A collapsible help panel for infrequent tasks (refused deliveries, damage claims, access code issues) reduces dispatch calls and removes the need to rely on memorized workflows.