Receiving
Helping employees within an organisation to quickly document the receipt of items or services that they have ordered.
Overview
Employees within an organisation frequently order goods and services to support operations. Upon receiving these items or services, it is essential for them to document the receipt. This record is then passed to the accounts payable team, which verifies the receipt and processes payment to the supplier in a timely manner.
The Problem
Receivers in an organisation often fail to record the receipt of the goods and services they ordered.
The lack of proper documentation raises audits in accounts payable like quantity mismatches, over billing etc.
Current Experience
Primary Research findings
Casual Receiver who orders goods or services once in a while. For example an employee ordering stationaries, computer accessories etc.
The current desktop application is difficult to use for this simple task, and the design is outdated.
Missing Bills/Over Billing issues raised by the accounts payable are sent to receivers frequently.
Advance Receiver who receives goods and services on behalf of someone else. For example someone in a mail room.
Receiving large volumes on behalf of others is laborious task.
Need to open multiple apps to perform receiving.
Managing the editing quantities for all items is challenging and time consuming.
Design Goal
Receivers want a effortless way record received items, so that they can complete the task and continue with their daily activities without interruption.
Final Designs
Casual Receiver
Advance Receiver
The casual receiver gets an email notification and receives the item with just a single click.
The Advanced Receiver scans the shipments individually and receives them at once, instead of searching for and receiving each item separately.
Learnings and Impact
The newer experience increased user adoption by 70% compared to the existing desktop experience.
As the Lead Designer, I delivered two design solutions: one that met the MVP requirements by translating the existing experience, and a second that proposed an optimal user experience for future implementation by the product team.
Users said this solution was a significantly better and easier experience than the older experience and would use it more.
