MultiVs - a one stop source for fragmented gaming knowledge.

Two distinct user behaviors emerged from our research: players seeking quick reference to data they'd already learned (frame data, item builds, matchup info), and players seeking onboarding into systems they didn't yet understand. These became Hector and Arlie.

Hector emerged directly from interview patterns. KSU's Marietta campus - formerly Southern Polytechnic - has a significant engineering and CS student population that overlapped strongly with competitive gaming engagement. Local FGC participants, League players, and one internationally-competing player surfaced consistent themes: reliance on stat trackers, preference for quick-reference formats over long-form content, and frustration that in-game information was insufficient for serious learning.

Arlie was a more deliberate construction. Goal-Directed Design often pairs personas to surface tensions, and Hector alone would have over-indexed the design toward power users. Looking back, however, her construction relied more on reasonable assumption than direct interview synthesis. With more time, I'd have weighted research toward casual players to validate or revise her needs profile.

The initial wireframes were sketched out on paper to establish core architecture and user flows. Following preliminary reviews and in-person user feedback, we tightened flow logic, regrouped relevant screens. The information hierarchy and iconography established here carried forward into high-fidelity design.

The high-fidelity prototype was built in Figma. I designed the Game Library, Character pages, Community Guides, and Settings sections and populated them with realistic content to give testers an authentic feel rather than lorem ipsum scaffolding. Visual language emphasized dark mode for extended use, with iconography drawing from established gaming UI conventions.

Screen 01

Game Library

The entry point is a visual-forward grid layout addressing Arlie's need for browsable discovery, with favoriting and search supporting Hector's targeted access.

Hector · targeted access Arlie · browsable discovery

Screen 02

Character Page

Character data laid out for scannability. Stats grid, role tags, and ability cards are organized so Hector can confirm matchup info in seconds, while ability descriptions remain accessible enough to support Arlie's onboarding.

Hector · scannable stats Arlie · readable abilities

Screen 03

Community Guides

Content is tagged by skill level (Beginner / Advanced) to directly addresses Arlie's need to identify what she didn't know without forcing Hector to wade through introductory material.

Arlie · learn what you don't know Hector · skip the basics

Our final usability testing phase surfaced a positive response to the overall layout and information hierarchy, with consistent friction around iconography in the navigation rail. Testers responded well to the efficient layout and the project's premise as a centralized resource. With more iteration time, the next priority would have been an icon labeling system or hover-state treatment to reduce learning curve.

Goal-Directed Design's emphasis on personas and user flows kept the work grounded, and every design decision traced back to either Hector's need for depth or Arlie's need for accessibility. If I were to approach this again, I'd allocate more time for usability testing in the high-fidelity phase. The iconography confusion that surfaced late could have been caught earlier with more iteration cycles.