How a simple filter replacement reminder became a trust problem

Small maintenance tasks are where product ecosystems either feel connected or start to show gaps.

This critique examines one such gap: a filter replacement flow that created uncertainty at the point of purchase.

Figure 1: Moment of uncertainty that triggered the filter replacement journey critique.

Context

While replacing the filter for my Winix 5520 purifier, I expected the app to guide me to the right product. Instead, I had to verify compatibility across the app, website, reviews, Google, and the manual.

What should have been a straightforward filter replacement flow surfaced gaps in contextual handoff, product discoverability, and compatibility assurance.

**Figure 1:** Snapshot showing the trigger, goal, first-time constraint, and outcome.

Why I documented this

I documented this as a self-initiated product critique because the issue came from a real interaction with a product I use.

The intent was to document the user flow, identify where confidence broke down, and propose focused solution directions that could make the filter replacement purchase flow easier to complete.

**Figure 2:** Scope narrowing the critique to the filter replacement purchase handoff.

Where the Flow Breaks

The breakdown happens across three connected moments: the app reminds the user to replace the filter, the website asks them to find the right product, and the final purchase decision depends on manual compatibility checks.

1. Broken intent handoff

The app prompts the user to purchase, but does not route them to a model-specific replacement filter.

**Figure 3:** The app starts the filter replacement purchase flow with a purchase CTA, but redirects the user into a generic website path instead of a model-specific filter recommendation.

2. Manual reassurance loop

The user has to check reviews, Google results, and the manual to feel confident that the product will fit.

**Figure 5:** With compatibility unclear in the product flow, the user relies on Google, ratings, and reviews to confirm whether Filter Q fits the Winix 5520.

3. Support information is disconnected from the app

The app contains the user’s purifier model and replacement trigger, but does not give direct access to the manual or compatible filter details.

**Figure 7:** The app dashboard shows device and filter status, but does not surface compatible replacement details or the user manual where the need begins.

Key Findings

The breakdown was not caused by one missing page or button. It came from a weak handoff between app, website, support content, and purchase decision.

That handoff broke down in four ways:

Context is lost across mobile app & website.
Air filter compatibility information is buried.
Support information and documentation is hard to access.
Users must self verify manually before purchase.

**Figure 10:** Four recurring issues that shaped the filter replacement flow breakdown.

Solution Exploration

The findings were translated into HMWs, each exploring a different point of intervention in the filter replacement journey: the app handoff, the product discovery path, and the support shown before purchase.

The concepts are not presented as a final redesign. They are solution directions that test how the experience could reduce manual verification and keep the task connected to the user’s known purifier model.

**Figure 11:** HMWs derived from the app-to-web filter replacement flow breakdown.

A. How might we preserve device context from reminder to purchase?

This explores how the app could make the purchase flow feel continuous instead of sending the user into a generic website experience.

1. Model-aware purchase CTA

The app should route users to the correct replacement filter for their registered purifier.

**Figure 12:** Purchase CTA carries the device model into the website flow.

2. App-side confirmation before redirect

The app should confirm the compatible replacement filter before sending users to the website.

**Figure 13:** The app shows compatible filter before redirecting the user to purchase.

B. How might we surface compatibility before users enter a generic catalog?

This explores how the website could reduce product hunting by making the correct replacement easier to identify upfront.

3. Model-specific filter replacement page

The website should route users to a replacement filter page built around their purifier model.

**Figure 14:** A model-specific page narrows the path to the replacement filter.

4. Compatibility-first product content

Make model compatibility visible on listings and product pages.

**Figure 15:** Compatibility is surfaced at listing level as either a badge or product title.

C. How might we make support information easier to reach the decision point?

This explores how manuals, replacement details, and proof of compatibility could support the user at the moment they are deciding whether to buy.

5. Support from the app and model pages

The app and model pages should expose product user manuals and replacement filter details directly.

**Figure 16:** The proposed settings screen adds a row for the user manual and filter replacement information.

6. Inline proof at the purchase point

Use manual or SKU evidence to confirm compatibility before purchase.

**Figure 17:** Product page shows compatibility proof before purchase.

Closing Note

The task itself was simple: replace a filter. What interested me was how quickly the experience became fragmented once I had to move between the app, website, reviews, and support content to confirm the right product.

This critique was my way of slowing that moment down, tracing where the uncertainty came from, and exploring how the flow could better support a user who is trying to complete a routine purchase with confidence.

Up Next

Research-Led Workplace Design

Mapped employee behavior to translate needs into space.