Understand and address in-branch issues arising from batching feature roll-out.
Broader discussions around process efficiency and accuracy at the branches are ongoing, leaving this UX debt unresolved.
User & stakeholder interviews, journey mapping, UX design
Jan 2019-May 2019
Early in the Chit Chats project, we launched a “batching” feature. This prompted users to group their shipments online and print a batch label for their consolidated packages. The intention was to allow Chit Chats staff to scan a single barcode at drop-off to process many shipments with ease.
Soon after launch, Chit Chats staff began noticing batch discrepancies where the number of packages didn't match the count on the labels. Because our efforts were focused elsewhere, this proved to be a significant source of UX debt that piled up over time.
After conducting user interviews and reviewing hundreds of client support conversations, I discovered that our clients did not understand or value the increased efficiency we sought from the feature. In fact, most users were using our batching tool to provide unintended shipment organization functionality that they felt was missing from the platform.
To address this, I developed designs for a revised flow which would replace the batching feature with two distinct features - groups and manifests. Groups could be used by high-volume clients to sort, organize and keep track of their shipments. Manifests represented a summary of packages clients shipped on a daily basis.