AIR FILTRATION MANAGEMENT
A B2B software platform that transforms filter performance, HVAC operating conditions, costs, and environmental data into clearer Total Cost of Ownership and Carbon Footprint decisions.
Go to FIltration Advice Software
UX/UI Design · Research · Prototyping
ROLE:

Product Designer · UX/UI Designer · Brand Designer

TIMELINE:

2020–2024

RESPONSIBILITIES:

Design Strategy · User Flows · Interface Design · Data Visualization · Brand Identity · Design System · Graphic Design · Training Documentation

TOOLS:

Adobe XD ·  Illustrator · Photoshop · InDesign

COLLABORATION:

 As the Product Designer, I led the complete design process while working closely with the clients, front-end team, and content specialist. This collaboration helped ensure that technical requirements, product messaging, visual design, and implementation remained aligned throughout development.
Context
Filtration Advice began with a small collection of requirements and an earlier 
version of the software that was difficult to use. The clients provided the 
operational inputs required by the calculation engine, but the product did not yet have a clear user experience, interface structure, or scalable visual system.

As the Product Designer, I was responsible for transforming those requirements into a complete digital product: from organizing the information and defining workflows to designing prototypes, interfaces, data visualizations, branding, and documentation.

Turning Requirements into a Product
The calculation engine remained outside my design scope, so I worked from the information users needed to enter and the results the software needed to communicate. Through ongoing working sessions with the clients, I translated technical requirements into user flows, guided forms, dashboards, reports, and organizational tools.

Each feature evolved through iterative discussions, prototypes, stakeholder reviews, and close collaboration with the front-end developer. This allowed the interface to develop alongside the product’s technical and business requirements.

How we framed the problem space
To understand risk points and user anxiety, we started with: 

●  Competitive scan (AutoTrader, Facebook Marketplace) to identify gaps in verification, transparency, and user burden
●  Stakeholder / peer consultation via focus-group style feedback to refine assumptions and feature priorities
●  A clear definition of who is most impacted (newcomers, local residents, busy professionals)

Output: A clear set of risks to focus on, build trust from the very beginning and moments where the UI must provide stronger guidance.
Strategic goals
●  Reduce cognitive load
Keep the experience simple, mobile-first, and predictable
●   Support informed decisions
 Make it easier to browse, compare, and bid with confidence
●  Reduce risk
Make verification and transparency visible early
●  Design for inclusion
Consider users who lack local networks and familiarity 
with Canadian marketplaces

These decisions focus on reducing friction while reinforcing user confidence at every step.
Who we designed for
●  Newcomers to Canada: 
Need: a safer, more guided process with clear standards
Scenario: browsing without local networks or trusted referral 

●  Local residents : 
Need: a transparent marketplace that saves time and reduces risk
Scenario: comparing options quickly and avoiding sketchy listings
Information architecture approach
We modeled AGA as a simple, streamlined service app, not just a listing site. 


The architecture was designed to:
● Surface trust signals early (verification, seller credibility, vehicle indicators)
● Keep users oriented with a predictable flow
● Reduce errors during bidding by making steps explicit
Prototyping
We moved from low-fi wireframes to an interactive prototype to validate navigation and task completion before investing time into polish.
This helped us focus on:
● Clarity of information
● Flow predictability
● Reducing decision anxiety during bidding
Usability testing (Maze)
To validate key tasks, we prepared usability tests in Maze by importing the Figma prototype and creating three separate tests focused on different app sections. Each included missions, contextual questions, and sight tests. 

We then ran the tests with another team, reviewed results and heatmaps, and used the findings to decide what to refine before moving into hi-fi.
Goal → Design response 
●    Trust & safety → verified listings + transparent bidding flow
●    Convenience → browse/compare/bid directly on mobile
●    Reduce search fatigue → smart recommendations based on user previous searches 
Quality, accessibility, and usability 
This project aligns with a quality-management mindset: embedding usability and accessibility considerations throughout the design lifecycle, not at the end. 

Next validation steps I would run in a real product environment:
● Accessibility review (contrast, touch targets, error prevention, plain language)
● Usability testing with diverse, first-time user groups
● Iteration planning based on evidence (testing + feedback)  
Collaboration
I worked in a team environment with structured milestones, peer feedback, and testing handoffs, including focus-group style feedback sessions and iterative refinement based on results.
What I learned
This case study reinforced something I care about in UX: good design isn’t just visual, it’s a process of defining risk, modeling user needs, testing assumptions, and iterating based on evidence.

Next steps:
● Run a second Maze round focused on newcomer clarity and task confidence
● Improve accessibility + error prevention
● Tighten content hierarchy based on where users hesitate most
↑Back to Top