Players said the menu felt scattered. I ran a card sort with the X8 Discord community, analysed with Casolysis 2.0, and shipped a colour-coded migration doc that engineers could read at a glance.
Role
Sole UX designer, X8
Team
Card sort participants recruited from X8 Discord community
Platform
Cross-platform VR — Meta Quest + Steam VR
Tools
Card sort survey tool, Casolysis 2.0 (analysis), Figma (migration doc)
Duration
2024
Status
Shipped — IA reorganization in production
Setup
Player feedback through the X8 Discord, in-game guerrilla observation, and team consensus all pointed to the same problem: the main menu felt scattered. Tab grouping was inconsistent, related options lived in different places, and players had to develop tribal knowledge to find what they wanted.
Rather than redesign from gut, I ran the work. The community was right there in Discord; the methods were familiar; the only real constraint was time, which is why I leaned on fast, structured techniques instead of long-cycle research.
What I did — 01
Every main-menu option and tab became a card. Open recruitment from the X8 Discord — real users of the game, voluntarily sorting on their own time.
What I did — 02
Used Casolysis to pull out the hierarchy and grouping signal from the participant data. Where players consistently grouped items together, the IA should reflect it. Where players diverged, the choice needed to come from design intent backed by a defensible read of the data.
What I did — 03
The deliverable to engineering wasn't a redesign — it was a map of the change. A Figma file with the existing IA on the left and the new IA on the right, with colour-coded arrows showing what moves where. Engineers could see “this tab goes there” in one glance.
What shipped
The reorganized IA is in X8. Tabs are grouped according to the card-sort findings. The migration doc made the engineering implementation a follow-the-arrows exercise rather than an interpretation exercise.
Conclusion
The full research → design → handoff loop, executed on a real product, in real time, with real users — using a recognisable, defensible method. The migration doc in particular is the artifact: it shows I think about engineering's job, not just my own.