Making a team-based fantasy sports product easier to understand.

The difficult part

Team-based fantasy sports asks a new user to understand several things at once: what the format is, how a league starts, what they are choosing, and what happens next. If those pieces arrive in the wrong order, the product feels more complicated than the game itself.

The design challenge was to make the first-run experience feel understandable before adding the depth that returning players would want. That meant clarifying the hierarchy of the product, not adding more decoration to the screen.

What I designed

I led the end-to-end design for the mobile product and its supporting web UI and handoff. The work covered the core home experience, league entry, team-based game surfaces, scoring and leaderboard views, and the states a user needs while moving through the product.

The important decision was to explain the game through the flow itself. Each step answers one question, shows the next action, and keeps the current state visible. The accompanying schematic is a design model for that flow, not a claim about a live system.

How it was researched

The project archive available to me supports the product design, mobile screens, and web handoff. It does not include a complete research log or experiment readout, so I am keeping this case study focused on the design decisions visible in the work rather than inventing a study around them.

Result

The résumé records a reported 20% increase in engagement after launch. I am keeping that qualifier because the supporting experiment design and baseline are not in the project archive I could verify. The design result I can show directly is a clearer product story across the mobile experience and the web handoff.