
GFL · Pharma & Narcotics Waste System
Replaced an undocumented legacy app with one platform of around 22 sections for handling pharmaceutical waste, admin tools included.
Company
GFL Environmental Services
Year
2025-2026
Role
Senior Product Designer
1. The Challenge
A pharmaceutical waste facility ran on a legacy supply chain app that nobody had documented. How it worked lived in people’s heads, and every task opened its own separate dialog box. There was also no admin screen, so fixing even a small data error meant asking an engineer to change the database through a ticket.
The constraints were tight:
Compliance: Health Canada rules gave the facility 10 days to process incoming hazardous shipments.
Little room for mistakes: A wrong entry or a system failure could put that compliance at risk.
The Impact
One platform instead of separate dialogs. Around 22 sections in four areas (admin, returns workflow, reporting and invoicing), organized around the tasks people actually do. Planned with a Business Analyst and the engineering team.
Admin tools for manufacturers, consignees, groups and products, so data fixes no longer wait on an engineering ticket.
Built for the warehouse floor. After launch, I used Microsoft Clarity recordings to adjust button sizes and how often data refreshes. Warnings and system states appear in context, so new operators don’t have to memorize the steps.
Clearer system messages. I used AI to rewrite technical messages into plain notifications.
Design and engineering in step. We built on a Shadcn UI component library and worked in feedback loops of about two weeks during parts of the project.

The Process
1.
Foundation
9 Months
Replaced the pop-ups. Reorganized the app around tasks instead of separate dialogs.
Wrote the design brief and site map for the Material Control System.
Turned regulations into design rules. With a Business Analyst and engineers, translated federal requirements and admin rules into how the screens behave, and shaped the data structure so the system could grow.
2.
Core Workflow
6 Months
Watched the work happen. Visited warehouses to see how handlers worked, so the screens matched the real steps.
Redesigned receiving, processing, sorting and shipping, plus the admin tools behind them.
Shortened the loop with developers. Changed how we worked together to get design-to-build cycles down to about two weeks, which sped up handoffs.
3.
Reporting and review
6 Months
Designed the reporting area and finished the remaining sections, bringing the total to around 22.
Checked the design with users. Met with them once or twice to confirm flows, features and fields, then changed the design based on what they said. Also ran a UI audit and brought an experienced warehouse operator into engineering sessions.
Worked with an uneven pace. Review rounds took between one and three weeks depending on the team’s availability, so I tackled the most critical flows first.
Project Gallery








