No bet left behind.
Bet matching on Wagr.
Bet matching on Wagr.
Bet matching on Wagr.
Context
Context
Context
Wagr is a startup that sought to combine sports betting with consumer social. It was a platform where friends could bet against one another on their favorite games in a way that was friendly, safe, and fun.
Bet matching was a feature that sought to combat high churn rates by expanding the network of who could receive bets on the platform.
As the designer for this project, I spearheaded the user research, detailed user flows, and crafted hi-fi prototypes.
Wagr is a startup that sought to combine sports betting with consumer social. It was a platform where friends could bet against one another on their favorite games in a way that was friendly, safe, and fun.
Bet matching was a feature that sought to combat high churn rates by expanding the network of who could receive bets on the platform.
As the designer for this project, I spearheaded the user research, detailed user flows, and crafted hi-fi prototypes.
Role
Role
Role
Product Design, Prototyping
Product Design, Prototyping
Tools
Tools
Tools
Figma, Origami Studio
Figma, Origami Studio
Timeline
Timeline
Timeline
April 2022 - August 2022
April 2022 - August 2022
How to not leave behind bets.
How to not leave behind bets.
How to not leave behind bets.
A how-to guide you can trust.
A how-to guide you can trust.
A how-to guide you can trust.
Step 1: Identify the problem
Step 1: Identify the problem
Step 1: Identify the problem
Wagr was witnessing high churn rates right after users invited their friends to take on the other side
Wagr was witnessing high churn rates right after users invited their friends to take on the other side
Wagr was witnessing high churn rates right after users invited their friends to take on the other side
Step 2: Reflect and rework
Step 2: Reflect and rework
Step 2: Reflect and rework
Why were users turning down bets?
Why were users turning down bets?
Why were users turning down bets?
Exploring why recipients were not accepting bets in their inboxes
Exploring why recipients were not accepting bets in their inboxes
Exploring why recipients were not accepting bets in their inboxes
Was the price not right?
Was the price not right?
Was the price not right?
Were users rejecting bets because they were too expensive?
Were users rejecting bets because they were too expensive?
Were users rejecting bets because they were too expensive?
Verdict: No
Verdict: No
Verdict: No
Users were accepting bets of all price ranges
Users were accepting bets of all price ranges
Users were accepting bets of all price ranges
Stranger danger?
Stranger danger?
Stranger danger?
Were users rejecting bets from people they didn't know?
Were users rejecting bets from people they didn't know?
Were users rejecting bets from people they didn't know?
Verdict: No
Verdict: No
Verdict: No
Bets were taken regardless of relationship
Bets were taken regardless of relationship
Bets were taken regardless of relationship
Wrong side?
Wrong side?
Wrong side?
Were users expected to support teams they didn't love in real life?
Were users expected to support teams they didn't love in real life?
Were users expected to support teams they didn't love in real life?
Verdict: Yes
Verdict: Yes
Verdict: Yes
Users were turning down bets for teams they didn't already support
Users were turning down bets for teams they didn't already support
Users were turning down bets for teams they didn't already support
Step 3: Create a game plan
Step 3: Create a game plan
Step 3: Create a game plan
Rolling out new features
Rolling out new features
Rolling out new features
Figuring out where on Wagr I was going to introduce bet matching to the user base
Figuring out where on Wagr I was going to introduce bet matching to the user base
Figuring out where on Wagr I was going to introduce bet matching to the user base
Home screen
Home screen
Home screen
Bet confirmation
Bet confirmation
Bet confirmation
Invite friends
Invite friends
Invite friends
Step 4: Execute the game plan
Step 4: Execute the game plan
Step 4: Execute the game plan
Prototypes I demonstrated to design, product, and engineering alike to illustrate how I envisioned each different user lifecycles playing out on Wagr
Prototypes I demonstrated to design, product, and engineering alike to illustrate how I envisioned each different user lifecycles playing out on Wagr
Prototypes I demonstrated to design, product, and engineering alike to illustrate how I envisioned each different user lifecycles playing out on Wagr
Step 5: Adapt the approach
Step 5: Adapt the approach
Step 5: Adapt the approach
I wanted bet matching’s initial launch on Wagr to the loud and clear. I wanted later iterations to be subtle and intuitive
I wanted bet matching’s initial launch on Wagr to the loud and clear. I wanted later iterations to be subtle and intuitive
I wanted bet matching’s initial launch on Wagr to the loud and clear. I wanted later iterations to be subtle and intuitive
Phase 1: Bold and upfront
Phase 1: Bold and upfront
Phase 1: Bold and upfront
Phase 2: Clear messaging
Phase 2: Clear messaging
Phase 2: Clear messaging
Phase 3: Subtle reminders
Phase 3: Subtle reminders
Phase 3: Subtle reminders
Phase 4: Fully integrated
Phase 4: Fully integrated
Phase 4: Fully integrated
What difference was made?
Matched bets
Matched bets
80%
+ 30%
+ 30%
Users saw an uptick in their number of bets being accepted
Users saw an uptick in their number of bets being accepted
