On this page

User journey

The stages a fan goes through, from first seeing XSERIES to waiting for the next edition, with today's touchpoints, the problems, and the role of the digital product.


Journey map

Read each column from left to right. The Problem row shows where fans are lost today. Goals shows what each stage must achieve (Goals), HMW challenges are the design questions to answer so that goal is reached (Challenges & HMW), and Success when is the sign the stage works (KPI).

1Awareness
2Consideration
3Decision
4Match day
5Post-match
6Retention
Today
IG reels, creator reposts, media articles
FAQ highlight, Bola.com article
TICKET highlight, GOERS
Venue, GOS YouTube (members)
YouTube highlights, IG reposts
IG goes quiet until the next announcement
Problem
No place to go after getting interested
Card rules are hard to understand from stories
Prices for 4 sections × 3 ticket types are confusing (XSERIES-3 tickets)
Viewers don't know which card is active
No archive of results and moments
Attention is lost during the gap between editions (12 months from XS-2 to XS-3)
Role of the digital product
A landing page that explains XSERIES in 10 seconds
A How to Play page with visual cards
Seat map and ticket comparison, deep link to GOERS
Live match companion: score, active cards, predictions, MVP vote
Edition archive, best moments, card collection
Waitlist, off-season content, staged reveals
Goals
HMW challenges
Success when
5-second test: participants can say what XSERIES is · IG visitors go on to a second page
4 of 5 test participants can explain the X Card · time on How to Play
UTM-tagged clicks to GOERS per source · fewer CS questions about tickets
Average ≥ 2 interactions per live user · the site stays up on match day
Moments shared per match · archive visits in the week after the event
Registered fans at 5–10% of IG followers · 30/90-day retention

Stages 1 to 3 are answered in Phase 1 (before the event), stage 4 in Phase 2 (during the event), and stages 5 and 6 in Phase 3 (after the event). See Roadmap.

From stage to challenge

Read each stage as one chain. If a link is empty, that stage has no answer yet.

Journey
Stage
  • Where the fan is, and where they are lost today
B · U · T
Goal
  • What must be achieved at this stage (Goals)
Design question
HMW challenge
Answer
Feature
Measure
Success when
  • The sign the stage works (KPI)

The map below shows which HMW guards each stage. Every stage has a user-side HMW, including Awareness (Get XSERIES in 10 seconds) and Post-match (Moments easy to share).

HMWAwarenessConsiderationDecisionMatch dayPost-matchRetention
Get XSERIES in 10 seconds
Recognized across editions
Fans outside Indonesia
Understand the X Card
IG content → seat
Cards readable during live
Present from YouTube
Sponsors in the moment
Withstand spikes
Live fallback
Moments easy to share
Care about teams
Between editions
Proof of audience
Trusted data
Fast updates

Guards this stage Helps

Match day is the busiest stage (five HMWs), so it carries the most risk if Phase 2 is cut. Decision is guarded by only one HMW, even though it is the main conversion point: if IG content → seat fails, goals Measurable tickets and Buy tickets fail with it.

Key moments

The four moments that matter most, grouped by phase. The label in the corner of each note is the journey stage.

Phase 1 · Before the event2
Consideration
1. First time seeing a card played

Why it matters: The "wow" moment that sets XSERIES apart

What to prepare: Must be easy to understand on one screen

Decision
2. Ticket checkout

Why it matters: The main conversion point

What to prepare: Reduce questions before the fan moves to GOERS

Phase 2 · During the event1
Match day
3. A comeback thanks to a card

Why it matters: The moment most likely to go viral

What to prepare: Clips and automatic share cards

Phase 3 · After the event1
Retention
4. Announcement of the next edition

Why it matters: The end of the gap between editions, whose length is not fixed

What to prepare: Fans on the waitlist must know first

Tip

For a full visualization, this journey can be developed into a service blueprint once the event operations team is involved.

Examples of other products that already solve the problem at each stage, with screenshots, are in Product references.

Research basis

How this page connects

Pages this one builds on, and other pages that use it.