A deep-dive into card sorting as a foundational UX research method. How open and closed sorting sessions surface mental models, inform navigation taxonomy, and validate information architecture before a single wireframe is drawn.
Most digital products live or die by their navigation. Yet teams spend hours debating button labels and tab orders without ever asking the people who'll actually use them. The result is a structure that makes sense to the team — and confuses everyone else.
The brief on this engagement was simple: take a sprawling enterprise platform with seven years of feature accretion and find an information architecture that real users could move through without a manual.
Card sorting works because it puts users in the driver's seat — they group, name, and prioritise content the way it makes sense to them. I ran three layered sessions to triangulate findings and avoid biases that any single technique introduces.
All sessions were moderated, recorded, and analysed for both the obvious patterns (which cards always cluster together) and the quiet ones (which labels are repeatedly hesitated over).
The biggest finding wasn't where the boxes went — it was how users renamed them. Internal terms like Configurations and Asset Library were quietly translated by users into Settings and My Files in nearly every session. The IA wasn't broken; the language was.
The matrix analysis (which cards co-occur in user-formed groups) revealed three cluster pairs the team had never considered grouping. Two of those became new top-level sections in the redesigned navigation.
The new IA shipped without the usual stakeholder pushback because every grouping was traceable to user evidence. Wireframe reviews shifted away from "what should this be called" debates to "does this flow work" — exactly where they should have been all along.
Card sorting didn't just produce a better menu. It produced shared language between research, design, and product — a small artifact that punches well above its weight.
