FotMob · Concept

Personalized Onboarding

A self-initiated concept for FotMob: onboarding that lets fans pick their teams and leagues, so the homepage opens on what they follow.

At a glance

60-second read

Problem

FotMob’s homepage shows so many leagues and teams that new users feel overwhelmed, and reaching a supported team’s game takes too many taps.

What I did

Interviewed 6 soccer fans, grouped findings in an affinity diagram, brainstormed 6 ideas and prototyped a personalized onboarding flow in Figma.

Outcome

A 6-screen concept: 3 onboarding questions, a homepage with favorites on top and a Favorites page. Testing is the next step.

Role

Sole designer

Timeline

May 5 – 12, 2024

Platform

Mobile app concept

Tools

Figma · Illustrator · Photoshop · Procreate

Status

Concept · not yet tested

5 of 6

fans called the homepage cluttered

6

fan interviews · 8 questions

1 tap

fans’ expected path to their team’s game

7 days

design sprint

Add a cover image in the CMS

一 ⋅ 01

Research

A self-initiated, one-week sprint. I’ve used FotMob for 4 years, so I started by setting my own assumptions aside and interviewing 6 soccer fans with 8 open questions.

I grouped what I heard in an affinity diagram: organization, usability, pain points and competitors. Two insights stood out:

  • Too cluttered. Fans felt overwhelmed by the number of leagues and teams, especially on first open.

  • Too many taps. One fan said finding their team’s game “shouldn’t take more than one tap.”

5 of 6

fans felt overwhelmed on first open

Fans liked the app once they found their game. Getting there meant scrolling past leagues and teams they didn’t follow.

二 ⋅ 02

Problem

The homepage gives every league and team equal weight, so fans dig for the few they follow. I narrowed the focus to one goal: make favorites (team, league or player) easy to reach. Success would be measured in taps per task.

三 ⋅ 03

Ideate & design

I brainstormed 6 ideas without judging them, from hiding unwanted leagues to a live-score widget, then converged on one: onboarding that builds a personalized homepage.

[Add lo-fi and hi-fi wireframes and the sitemap]

Decision log

Each decision, the evidence behind it, and the screen it became.

Decision

Evidence

Screen

3 onboarding questions: favorite team, other teams, a league

5 of 6 fans felt overwhelmed on first open

Screens 2–4

Followed teams and leagues pinned to the top of the homepage

Fans expect one tap to their team’s game

Screen 5

A Favorites page for every followed team and player

Favorites were scattered across the app

Screen 6

Returning users skip onboarding

Only first-time users need setup

Screen 1 → 5

[Confirm whether players can be picked during onboarding: Screens 2–4 ask about teams and leagues only]

四 ⋅ 04

What’s next

  • Test the prototype with the original 6 interviewees

  • Count taps to reach a team’s game, before and after

  • Iterate on earlier phases based on what testing shows

五 ⋅ 05

Reflection

The problem isn’t always mine

Even as a 4-year user, interviews showed me pain points I’d stopped noticing.

Don’t kill ideas early

Diverging fully gave me better options to converge on.

Design thinking is a loop

Testing is the next turn of it, not the end.