8 UX designers, 1 UX Director, 3 developers, 2 business analysts, 3 product owners
UX Research, UI/UX Design, Design Systems
11 months (April 2024 - March 2025)
Microsoft Office, Jira, Figma, Adobe Creative Suite
Cardinal Health had an opportunity and a problem: Their radiopharmacies (nuclear pharmacies) have been expanding due to radical new products on the market. However, their internal application was last updated over a decade ago and was starting to show its age, as it was designed solely for Windows. Finally, several of the users had grudges with its antiquated design and numerous roadblocks.
We created IsoMod: Cardinal Health's modern application to manage orders, waste management for their nuclear pharmacies. I was responsible for providing UX research and consulting, as well as designing several modules of the application, which included orders and waste management.
During this time, I travelled to a nuclear pharmacy in Atlanta, GA to see how it functioned, their processes, how their products were created, and how IsoTrac was used by its employees.
The main room where lab technicians, nuclear pharmacists packaged products, shipped products, and stored any waste.
The Buffer room where products were assembled. IsoTrac was being used by numerous types of machines, which informed design decisions.
It was clear that the current application was dated and cluttered.
Several buttons were oddly placed (such as edit to decrease demand), and there was a lack of unity and cohesion throughout the application.
Original process flow, which was clunky.
Sample Emails that I would send daily to my TCS Team Members after my visits. I would write my observations, potential areas to explore, and what the next action steps would be.
The aforementioned buffer room, where products were created, was very cramped, which led to users accidentally knocking over equipment such as timers.
One of the intro slides from my PPT, going over the process flow.
Sample slides, where I propose having the pharmacy use modern scanners to update inventory and waste modules, rather than doing it manually.
A video of the full powerpoint presentation
We would have elaboration calls with the appropriate buisiness analyst, product owner(s), designers and developers to review what was currently in IsoTrac, how it functioned, and what the new application would need.
Once all the elaboration calls were completed, these would result in Jira Stories and Epics being created. Sample User Story in Jira.
Sample mid-fidelity wires presented to product owners and team. These were instrumental in informing the information architecture and the look and feel of IsoMod.
We would create numerous iterations and variations of these to show the delivery partners, product owners, and clients.
Screenshot of sample User Story. It would be organized by screen number, what the scenario was, what actions and reactions, and additional notes as required.
Once the user stories were completed, the stories would end up assigned to me in the UX queue.
One of the first iterations of the "Customer Orders" page, where users can keep track of and search orders.
We would organize each of the designed Jira stories in numerical order on Figma. This was done to make it easy for product owners to find and review the stories and designs.
Final Disposal Landing Screen
Final Bin List Landing Screen
Final Customer Orders Landing Screen
Finalized Edit Order screen.
Finalized Add Order screen.
Customer Impact and price Adjustment, a sample popup where the user can adjust the prices of the order.
Finalized Dashboard for IsoTrac.
We would have numerous calls with the development team to go over the developed screens, and make adjustments as needed.