05 / TAKE-HOME STUDY

Pick three.
Get them all right.

A mobile prediction experience designed from scratch as part of a combined UX/UI and marketing take-home.

Take-home · Product designMobile-firstCompany anonymizedDesigned from scratch

Three random matches. One ticket. Every pick has to be right.

Screens as submitted, cleaned for publication · Matches, times and ticket numbers are demo data.
01 / The assignment

Three parts.
One test of how I think.

The exercise separated business thinking, product design and the reasoning behind the work. The screen was only one part of the answer.

Part 1 · Business thinkingQuestions, priorities, a crisis.

What to ask before designing. How to decide when five teams want different things. What to do when the flow changes two days before launch.

Part 2 · The UX/UI challengeA mobile prediction game.

A free-to-play landing page: predict 1, X or 2 on at least three random matches, confirm, and get a ticket. In the brand's look and feel.

Part 3 · ReasoningExplain the decisions.

The three key decisions, the assumptions, what to test if conversion is low, and where AI helped. AI use was allowed if disclosed.

02 / Before I design

Questions that
change the solution.

Product asked for a landing page “ready next week”. I wouldn't start until the business, audience and market context were clear. Each answer could change what the page leads with.

01Business objectiveAcquisition, monetization or retention?
02AudienceWho are we designing for?
03Traffic & authWhere do users come from, and are they logged in?
04Conversion eventWhat action defines success?
05Essential infoWhat must users know first?
06ConstraintsRegulatory, legal and technical.
07Success metricsHow will we measure it?
08LocalizationWhat changes across markets?

Business + user + market context → grounded decisions, not guessed solutions.

03 / Priorities

One critical path.
Five agendas.

The brief presented five competing stakeholder positions. I treated them as inputs to evaluate, then ranked what the first screen had to do and moved the rest one layer deeper.

“We need to explain all the functionality.”
PRODUCT
“Most traffic is paid. The page needs to convert quickly.”
ACQUISITION
“Our users already know us. We don’t need a lot of explanation.”
CRM
“It needs to feel premium and match the new campaign.”
BRAND
“Our users don’t understand this feature yet.”
LOCAL MARKET
The value proposition, the primary CTA, a fast path to actionKeepThe first screen does one job: get to the first pick.
Detailed explanations, How to play, FAQMove deeperAvailable for newcomers, never in the way of regulars.
Anything that adds friction without helping the main pathChallengeAsk what it's for before it goes on the page.

CLARITY → VALUE → ACTION · GOAL → EVIDENCE → DECISION → TRADE-OFF → MEASUREMENT

04 / A launch scenario

60 minutes.
The date doesn't move.

The exercise asked how I would respond if a critical part of a flow changed two days before launch. This is the first hour I proposed.

0′–10′UnderstandWhat changed? What breaks?
10′–20′AssessCritical, high or low impact.
20′–30′AlignProduct, CRM, Acquisition and Design.
30′–50′ExecuteThe minimum safe change.
50′–60′MonitorOwners, deadlines, real-time tracking.

Accuracy and conversion first. Polish second.

Risk reduction, not a redesign under panic.
05 / From brief to structure

Requirements in.
A product flow out.

I translated the practical brief into one short path: understand the game, make three predictions, review the commitment and receive a ticket.

The brief asked forProduct behaviorWhere it lives
Random matchesAt least three upcoming matches. Each can be replaced before predicting.02 · Predict
1 · X · 2One toggle per match. Every selection must be right to win.02 · Predict
Continue after threeThe primary action stays locked until the minimum is complete.02 · Predict
Short rulesFree to play, deadline, random selection and the rules.01 · Entry
Review and confirmA summary with an edit option before confirmation.03 · Review
Ticket and timerA receipt and a countdown to when results are decided.04 · Ticket

The company scoped the complete take-home, across all three parts, to 90–120 minutes.

Not just a screen. A way of thinking.
06 / Product decisions

Three decisions
hold the flow together.

I designed the experience from scratch around three moments where the interface has to explain itself without slowing the user down.

1Explain enough. Not everything.A minimal hero and an optional How to play keep experienced users moving while giving newcomers a clear place to learn.
2Turn the rule into feedback.The counter connects the three-pick requirement to the locked Continue action and makes the next step visible.
3Control before confirmation.Review and Edit let users catch mistakes before the prediction ticket is generated.
07 / The submitted experience

From first pick
to a confirmed ticket.

The final submission turns the written requirements into a short mobile journey with one clear action at every stage.

01ENTRY
Entry screen: Pick. Predict. Win. hero, How to play in the header, and the first random match
02PREDICT
Predict screen: three matches with a pick made on each
03REVIEW
Review screen: each pick with an Edit link, and Confirm picks
04TICKET
Ticket screen: prediction confirmed and a countdown to results

Brand logo removed and copy errors fixed for publication. Everything else is shown as submitted.

08 / Play it

Your random picks.

A working model of the submitted flow. Pick 1, X or 2 on all three matches, replace one if you like, review, then confirm.

HOW TO PLAY
  1. 1Get three random matches. Replace any of them.
  2. 2Predict 1, X or 2 on each one.
  3. 3Review your picks, then confirm.
  4. 4Get every prediction right to win.

Demo only. Free to play, nothing is placed, and the fixtures are examples. Club crests belong to their clubs.

Pick. Predict. Win.Demo
Champions LeagueToday · 21:00
Real Madrid
VS
Barcelona
LaLigaSun · 18:30
Atlético Madrid
VS
Real Sociedad
Serie AMon · 21:45
AC Milan
VS
Inter Milan
1 of 3predictions completed
09 / Assumptions

Assumptions helped
me move. Data decides.

Mixed traffic: acquisition plus CRMAnalyticsTraffic source and funnel behavior.
Users understand 1 · X · 2Usability testCan users finish the flow unaided?
Markets behave alikeLocal reviewLanguage, culture, regulation.
IF CONVERSION IS LOW, FIND THE DROP-OFF FIRST
01Is the promise and CTA clear enough to act on?
02Would “Home / Draw / Away” reduce friction compared with 1 · X · 2?
03Is “Replace match” discoverable and understood?
10 / AI and ownership

AI sped it up.
I owned the calls.

Where AI helped. Critique, alternative directions, microcopy exploration and test planning.

What stayed mine. Strategy and priorities, stakeholder alignment, ethics and responsible gaming, and local cultural context.

What I'd still ask for. Before production: the technical constraints, historical benchmarks, and the regulatory requirements in each market.

What I'd check first with real users. Whether 1 · X · 2 needs words. It's the one assumption the whole flow rests on.