CASE STUDY
I audited key product flows, grouped recurring UX problems, and turned them into a set of practical recommendations the team could review together.
Project Context
Features and flows had built up over time, so navigation, hierarchy, terminology, and feedback no longer behaved the same way across the product. The audit put those issues in one place so the team could discuss them side by side.
The UX Challenge
My Role
I set the evaluation criteria, reviewed key product flows, grouped repeated issues into themes, and organized the findings so design and product could work from one shared view.
Methodology
Each flow was reviewed the same way so findings could be compared, not collected as disconnected notes.
Choose the product journeys most relevant to the audit scope.
Review navigation, hierarchy, feedback, consistency, and task continuity.
Document findings using shared severity and theme categories.
Group recurring issues into broader patterns and recommendation areas.
Findings
Similar controls appeared in multiple locations without a clear hierarchy.
Some journeys did not make the next available action obvious.
Similar concepts were labeled differently across product areas.
Some state changes lacked clear feedback about what had happened or what came next.
Recommendations
Each recommendation stays linked to the observation that motivated it.
Outcome
Instead of a list of disconnected UI problems, the audit created one view of what was recurring, where it appeared, and what was worth addressing first.
I like talking through design decisions. If you would have approached something differently, I’d like to hear it.