IBM

Company

IBM

Role

UX Designer

Brief

We partnered with the Government of Canada to help modernize their approach to managing “materiel” data—everything from office chairs to helicopters. The scale and complexity were immense, and the stakes were high.

Our goal was to make their massive datasets usable, insightful, and more human-centered. That meant cleaning up messy taxonomy, building a design system from scratch, and working hand-in-hand with stakeholders to ensure adoption.

Over 250,000 unique SKUs were buried in outdated systems. Our job was to help make sense of it all and create tools that empowered users to find what they needed fast—whether that was printer ink or aircraft parts.

Rather than guess, we asked. Then asked again. We ran continuous workshops with stakeholders across departments to surface real user pain points and build shared ownership in the solution.

Every workshop fed into a prioritized backlog that guided design sprints. We captured behavior patterns, unmet needs, and low-hanging optimizations to build momentum early and often.

track

We logged qualitative and quantitative user pain points across systems.

convert

We translated findings into technical and design requirements.

pattern

We categorized recurring behaviors and themes.

Loop

From better grades to greater peace of mind, students regularly share how Messenger Pigeon has changed their learning experience for the better. Feedback is overwhelmingly positive, particularly around reliability, speed of service, and how inclusive the platform feels.

We didn’t just design the product—we championed modern UX methods across the org. By embedding with internal teams, we helped introduce Agile practices, sprint rituals, and better research hygiene.

We developed a flexible, component-based design system tailored to SAP Fiori guidelines. From data tables to filtering logic, everything was created with scalability, accessibility, and WCAG compliance in mind.

We restructured the digital tools around user tasks, not system logic. Wireframes and prototypes were tested with real users and refined based on direct feedback.

Improved Data Quality

Redundant and inconsistent SKUs were flagged, merged, or removed—paving the way for more accurate reporting and procurement decisions.

Increased Adoption

Usability enhancements and a clearer UX encouraged adoption of the new system by previously hesitant teams.

Cross-team Alignment

Our sprint-based UX process helped break down silos between procurement, engineering, and data teams—leading to more efficient collaboration.