I designed warehouse workflows for material movement on rugged Zebra handhelds, balancing scan-first speed with safeguards for high-risk actions.
ROLELead Industrial UX Architect
DESIGN TIMELINEDesign & Prototyping
TARGET DEVICESZebra TC52 / TC57 Touch
MIDDLEWARE INTEGRATIONZebra DataWedge API
TARGET ENVIRONMENTAutomotive Floor
The Harsh Reality of the Factory Floor
Line operators, warehouse pickers, and dock coordinators use these handheld terminals for 8+ hours a day. Extreme environments break consumer UX assumptions. Heavy duty gloves, one-handed touch, overhead fluorescent glares, continuous mechanical noise, and Wi-Fi dead zones require absolute visual clarity and physical resilience.
Line Operator
Production Assembly
Manages just-in-time Kanban bin replenishment directly next to fast-paced heavy welding cells.
Warehouse Picker
Directed Storage
Coordinates bulk pallet relocation, stock transfers, and high-density material putaway sequences.
Dock Coordinator
Logistics & Dispatch
Verifies outbound trailer dispatch, final package manifests, and physical security seal compliance.
3 of 8 Designed Core Workflows
STEP 01 / STARTPreserial Create
WMS-level batch print of physical product labels.
STEP 02 / TRANSITKanban Classic
Closed-loop replenishment signal verification.
STEP 03 / DISPATCHClose Truck
Validating outbound pallet counts & loading.
THE CORE QUESTION
How do you keep low-risk tasks instant and high-risk tasks completely safe, on the same terminal, for the same users?
CORE DESIGN TENET
Friction is proportional to risk, not uniform.
Instead of enforcing a rigid security scan step on every action, the interface scales transactional resistance dynamically. Low-stake loops trigger automatically on a single scan; high-consequence operations require structured gates.
LOW RISK // ASYNC BUFFER
01. Kanban Replenishment
A physical barcode scan triggers instant automated loop execution.
MEDIUM RISK // GATE CONFIRM
02. Close Truck Dispatch
Fast inventory tracking is combined with a conscious, deliberate physical hold.
HIGH RISK // PERSISTENT OVERLAY
03. Preserial Stock Block
Errors cause severe downstream shipping blocks. Highly guarded alert screens.
01. Instant replenishment scan
02. Fast scan with hold-commit
03. Strictly guarded block validation
01Component Kanban Classic
Replenishment Loops — One scan empties a bin, one scan refills it.
01 The Problem
Production Lines Can't Wait for Parts
Kanban replenishment must be instant and error-free. The core challenge: make a highly reversible action feel instant while still preventing wrong-line triggers that cause major manufacturing downtime.
02 Core Flow Progression
01. Initial Scan Prompt
02. Empty Success
03. Wrong Line Exception
THE DECISION
Light-Switch Trigger
One scan equals action complete. No verification dialogue, no second tap needed. The scan itself is the confirmation because Kanban actions are fully reversible — if you empty the wrong bin, an instant Undo is always one tap away.
THE TRADEOFF
Speed Over Caution
Wrong-line validation catches structural errors automatically; for the rare physical mis-scan, a one-tap Undo is cheaper than adding a confirmation step to every scan.
03 Design Polish Highlight
Multi-Modal Feedback Signature
Every state change fires an audible beep, a unique haptic pattern, and a bright LED status indicator concurrently. Operators feel and hear the transactional outcome through heavy gloves.
02Close Truck Dispatch
Fast LPN scanning during loading, then a deliberate hold at the irreversible commit.
01 The Problem
High-Speed Loading vs. Accidental Dispatch
Dock coordinators load pallets under intense time pressure — they require fast, uninterrupted scanning. But closing a truck officially dispatches the ASN and seals the trailer. An accidental tap-to-close causes expensive physical retrievals from packed moving vehicles.
02 Core Flow Progression
01. High-Speed Loading
02. Verify Shipment
03. Hold-to-Close Action
04. Route Guard Block
THE DECISION
Hold-to-Close Pattern
A physical press-and-hold replaces the standard tap-to-confirm. The duration was set at 3 seconds as a starting point, to be calibrated with real operators. The gesture is intentionally demanding — you cannot accidentally complete it with gloved hands while juggling heavy scan equipment. If you release the press early, the state resets with zero data loss.
THE TRADEOFF
Targeted Micro-Friction
Every single step in the packaging, loading, and scanning sequence is optimized for maximum speed (scan-to-add, auto-tally). The hold gesture is the single point of deliberate friction in the tool, positioned at the exact moment of no return.
03 Design Polish Highlight
Integrated Route Guard Mismatch Block
The system intercepts misrouted pallets before the truck is allowed to seal. If an LPN belongs to a different trailer, the screen flashes red and blocks immediately. It presents a simple “Remove LPN & Continue” escape hatch, following the same mistake-proofing paradigm as Kanban.
03Preserial Stock Creation
Registry-backed serial blocks with verification gates — printed labels can't be unprinted.
01 The Problem
Manual Destruct Loops & Serial Clashes
Generating preserial stock produces physical labels with unique serialized barcodes. A misprint, duplicate block, or unverified sequence requires tedious manual label destruction, database quarantining, and immediate line delays. Every step must be heavily guarded.
02 Core Flow Progression
01. Scan Material Label
02. Print Progress
03. Label Verification
04. Serial Collision
THE DECISION
Strict Verification Gates
Every individual label must be physically scanned to register active verification before the entire serial block can release downstream. An unverified block stays locked in PENDING status forever — there is intentionally no override command on this gate.
THE TRADEOFF
Throughput vs. Traceability
Verifying a 50-label batch requires exactly 50 individual verification scans. This slows down the batch-creation throughput. However, each verification creates an ironclad, auditable chain of physical custody that satisfies automotive tracing standards.
03 Design Polish Highlight
Intelligent Local Collision Recovery
When the central serial registry triggers a collision warning, the system gracefully rolls back only the unprinted spooling cache, identifies the conflicting duplicate, and automatically increments the queue to the next available unique ID. Line operators resume printing in one click without restarting their entire task.
What separates 8 screens from one design system
Four shared interaction patterns surface across every workflow — proving this is one coherent system, not eight isolated builds.
PATTERN 01
Scan-First Template
Every flow starts the same way: a full-screen scan prompt with a single call-to-action. The scan target label changes, but the layout and the trigger are identical.
PATTERN 02
The Gate Pattern
When progress must be blocked, the system uses a consistent hard-gate: a full-screen alert with a clear explanation and a single path forward.
PATTERN 03
Prevention & Recovery
Every flow has both a prevention mechanism and a recovery path. Wrong Line + Undo in Kanban echoes Destination Mismatch + Remove LPN.
PATTERN 04
Consistent Severity
Errors follow a traffic-light severity system across all flows. Green = success/info, Yellow = warning/attention, Red = blocking error.
SYSTEM SCOPE
The Other 5 Designed Workflows
Component Reintro
Reintroducing quarantined assembly pieces into raw stock bins.
Move to Warehouse
Direct storage relocations from docking bays to long-term holds.
Close the Picking
Closing out dispatch waves to verify pallet completeness.
Transfer Picking
Direct inter-station relocations with active barcode routing.
Quick Move
Instant one-scan relocation for rapid line adjustments.
What I'd validate if this shipped
Empirical field testing and technical performance markers to measure operational resilience.
Open Questions
Does one-scan verification hold up against fatigue on a 50-label batch?
Does the 3-second hold gesture feel natural under heavy industrial gloves?
How do operators experience the transitional UI in extreme Wi-Fi dead zones?
What I Would Change
Reusable slot-based templates for all scanner interaction layouts.
Introduce a synthetic simulation training sandbox mode for new hires.
Build the complementary real-time supervisor productivity cockpit dashboard.
