User research, Competitive analysis and Insights
Role-based access permissions restrict access to sensitive data and implement data encryption, and user authentication.
System should be pharma inclined, and compliant with regulations of different authorities in different countries.
Standard and customizable dashboards and reports allow users to generate and analyze data.
Define goals and brainstorm ideas
A setup can be designed to record stock activity coming and going from the warehouse.
Dashboards can be designed to showcase product data and transaction trace.
Instead of manual notes, a separate section for comments can be provided which will be forwarded to the next team for further action.
Purchase Orders and Sales Orders should be capable of undoing the calculations in the system whenever there is recall or return.
Raising credit and debit notes should re-calculate the stock and margin valuations and user should be able to track the activity.
User should track the cancellations and therefore updates supplier and customer history.
I dug too deep!
I got lost in the loop. I started getting into deeper scenerios and loosing the grip over the track. I got too many information about too many areas and I started making up flows for different modules at the same time.
Peers to the rescue
My peers helped me to get out of the loop.
I realised I have to start with the high level overview instead of deeper scenerios.
Once the modules are finalized, I can start digging up scenerios one module at a time.
Products should be created with detailed info required by different governing bodies, set the Sale and Purchase specifics and allow user to repack a product
Supplier and Customer access to specific users or user groups
Include Supplier and Customer licenses for import/export of Controlled Drug (CD) products
Show overall data of products and purchase-sale activity of the same of a particular user
Record Purchase-Sale activity along with Product lifecycle in the reports
Show valuations and margins based on Purchase-Sale activity
Show analytics of Purchase and Sale according to users along with the valuation within a specific timeframe
Goods-IN should include purchase orders and supplier returns while Goods-OUT should include sales orders and customer returns
Show allocation details reflected in the stock management to prevent users from allocating same stock
Flow chart, Lo-fi and Hi-fi prototypes
Emphasized simplicity in design to reduce cognitive load, enhance usability and provide a clean and focused user experience.
Ensured standardized design and brand consistency to facilitate familiarity and ease of use for users.
Ensured that the system can handle increasing data volumes, users, and business complexity without sacrificing performance or usability.
Used primary pharma color to reflect the identity of pharmaceutical companies and considered tints and shades to add depth to the color scheme.
Provided clear and timely feedback to users to indicate the status of their actions and system processes.
Implemented encryption, and authentication mechanisms to safeguard user information and system integrity by adhering to industry standards for data security and compliance.
The prototype outlines the navigation structure of the ERP system, including menus, sub-menus, and navigation paths between different modules and features.
It illustrates how users can move through the system to access various functions and data.
The prototype includes a design for the system's dashboard, which provides users with an overview of key metrics, alerts, and actionable insights.
The dashboard layout and widgets are designed to offer users quick access to relevant information and tasks.
Testing, Iteration and Launch