B2B sports engagement platform
Turning a Status Dashboard Into an Operational Overview
How I redesigned a dashboard that surfaced a handful of disconnected metrics into a clearer view of events, games, series and the things that needed attention.
Role
Product Designer
Timeline
2023 · 4 months
Company
BettorGames
Platform
Desktop web
Before — A small set of event-status cards
Dashboard
From: 10/08/2023 00:00 to 17/08/2023 23:59After — A broader operational overview
Dashboard
Events Overview
Based on the last 7 days
Games
Series
Pending Tie-Breakers
Tie-breaker games that need to be finalized
| Game | Age | Type | |
|---|---|---|---|
| FUL | Troy Missouri ChallengeTroy Missouri Challenge | 9 hrs | MT |
Automation
Winners
2023 © Chalkline
Overview
BettorGames gave sportsbook teams tools for creating and managing sports engagement products — games, events and series. The dashboard was meant to show them what was happening across the platform.
Over time the product grew and the dashboard didn’t. It surfaced event statuses and little else, so clients still went elsewhere to check active series, pending tie-breakers, automation status and changes in prize value.
The challenge wasn’t simply to add more information. It was to decide what belonged on the dashboard, what needed attention, and what was more useful when shown over time.
- My role. I led the UX and UI work, with the product manager, the head of product and the engineering team.
- The goal. Make the dashboard a starting point for understanding the platform, not another screen to pass through.
Dashboard
From: 10/08/2023 00:00 to 17/08/2023 23:59The product had grown beyond its dashboard
Client conversations kept arriving at the same issue from different directions: teams wanted the information their day-to-day work depended on, without moving between different parts of BettorGames.
What clients were asking for
Series
“For the ‘Series’ section, it would be beneficial if we could have an at-a-glance chart showing the progress of built vs. open vs. live series. This way, we can easily see which series needs immediate attention.”
Client messagePending Tie-Breakers
“It’d be great if there’s a notification feature for ‘Pending Tie-Breakers’ so we can address them promptly and ensure a smooth player experience.”
Client emailPrize value
“In the ‘Winners’ section, can we get a graphical representation of the prize value changes over the last 7 days? It would help us analyze our budget and prize strategy better.”
Stakeholder callTaken together, they suggested a larger problem: the dashboard’s information model no longer matched the way clients were using the product.
More information wasn’t automatically a better dashboard
The obvious response would have been to add every requested metric as another card. That would solve the individual requests while creating a new problem: a dashboard full of equally weighted numbers.
So I sorted what clients were monitoring by the kind of signal it was.
What’s happening
- Events
- Games
- Series
What needs attention
- Pending Tie-Breakers
What’s changing
- Prize value
- Winner count
A stronger basis for the dashboard than reproducing the product navigation as a set of cards.
Giving different signals different weight
A completed-events count, a pending tie-breaker and a seven-day prize trend shouldn’t compete for attention in the same way. Three decisions followed.
Group status, don’t scatter it
Events, Games and Series each had several states. I grouped them into product-level summaries so clients could scan an area instead of reading a grid of unrelated numbers.
One card per state
Pending Results
5
Completed
1434
Off
29
Scheduled
204
One card per product area
Events Overview
Based on the last 7 days
Pull action out of status
Pending Tie-Breakers could require intervention, so I separated them from passive metrics rather than letting them disappear among status counts.
One more status count
Its own area
Pending Tie-Breakers
Tie-breaker games that need to be finalized
| Game | Age | Type | |
|---|---|---|---|
| FUL | Troy Missouri ChallengeTroy Missouri Challenge | 9 hrs | MT |
Show movement, not just a value
Prize value became more useful when clients could see how it changed over time, so the static number became a compact trend view.
A value
Prize value
A value and its movement
Winners
Adding information without turning it into noise
The redesign deliberately increased the amount of information on the dashboard. That meant density became part of the design problem.
Each exploration traded off the same three things: how states were grouped, which information earned a larger card, and how much history to expose.
The aim wasn’t to minimise the amount of information. It was to make more information easier to understand.
01 · Fragmented metrics Sixteen equally weighted line items, and nothing stands out.
Events
Games
Series
Automation
Tie-Breakers
02 · More data, weak hierarchy States are grouped, but everything still carries the same weight and nothing shows change.
Dashboard
Events Overview
Based on the last 7 days
Games
Series
Automation
Pending Tie-Breakers
Tie-breaker games that need to be finalized
| Game | Age | Type | |
|---|---|---|---|
| FUL | Troy Missouri ChallengeTroy Missouri Challenge | 9 hrs | MT |
2023 © Chalkline
03 · Grouped by purpose Status, then what needs attention, what is running, what is changing.
Dashboard
Events Overview
Based on the last 7 days
Games
Series
Pending Tie-Breakers
Tie-breaker games that need to be finalized
| Game | Age | Type | |
|---|---|---|---|
| FUL | Troy Missouri ChallengeTroy Missouri Challenge | 9 hrs | MT |
Automation
Winners
2023 © Chalkline
Retrospective view of the main design iterations — the labels are my analysis now, not the names these files carried at the time.Recreated for this case study from the original product designs.
One place to understand the state of the product
The dashboard brought the main operational signals together without treating them all as the same kind of information.
Dashboard
Events Overview
Based on the last 7 days
Games
Series
Pending Tie-Breakers
Tie-breaker games that need to be finalized
| Game | Age | Type | |
|---|---|---|---|
| FUL | Troy Missouri ChallengeTroy Missouri Challenge | 9 hrs | MT |
Automation
Winners
2023 © Chalkline
- 01Events — Status grouped by product area
- 02Games — Activity visible at a glance
- 03Series — Built, open and live states surfaced
- 04Tie-Breakers — Actionable work separated from status
- 05Winners — Prize movement shown over time
- 06Automation — Operational status visible
Recreated for this case study from the original product designs.
Summary first, detail when needed
A dashboard still needs to lead somewhere. The cards acted as entry points into the relevant areas of the product, allowing the overview to remain compact while deeper information stayed available when needed.
Checking whether the dashboard answered the right questions
I reviewed the redesign internally and with a small number of clients, then gathered additional feedback through the Client Relations team.
The response was strongest around the broader overview: clients could see more useful information from the first view, while the new structure made the dashboard feel clearer and easier to use.
Feedback themes
Clearer than the previous dashboard
The redesigned dashboard felt clearer and easier to use than the previous version.
More useful at first glance
Clients valued being able to see more useful information from the first view, without having to move through as many areas of the product.
A stronger starting point
The broader overview made the dashboard more useful as a starting point for understanding what was happening across the platform.
A dashboard that better reflected the product
The redesign expanded the dashboard from a small set of event-status metrics into a broader operational overview covering the areas clients were actively monitoring.
The biggest change wasn’t simply the amount of information available. It was the structure around it: related statuses were grouped, information requiring attention was easier to identify, and trends were visualised where a single number wasn’t enough.
Feedback after the redesign was positive, particularly around the clearer layout and the ability to see more useful information from the first view.
What I took from it
This project changed how I think about dashboards.
The challenge is rarely fitting the maximum amount of data onto one screen. It’s deciding which information helps someone understand the situation, which information asks them to act, and which information needs context before it becomes useful.
I still use the same principle in the more complex B2B products I work on now: decide what deserves attention before deciding how to display it.