Product Design
Optimising betting speed: redesigning the quick bet slip for Playtech Sports
Role
UX Lead
Timeline
2024
Tools
Figma, UserTesting.com, InDesign
Deliverables
High-Fidelity Wireframes, Interaction Specification Documentation
Overview
In sports betting, conversion relies heavily on speed—particularly during live, in-play events. Playtech’s core transactional journey featured a legacy "Quick Bet Slip" (QBS) designed to accelerate single-selection bets. However, users looking to place other highly common combinations were forced to open the full, traditional bet slip (the "cart"), interrupting the flow, slowing down the transaction and hurting conversion.
The problem
Inherent domain complexity: sports betting is exceptionally complex, requiring the interface to balance constantly shifting odds, diverse bet combinations, promotions, and intricate backend behaviours like overask (manual trader review).
Feature creep vs. core utility: the primary challenge was determining how to introduce advanced bet combinations and features into the QBS without increasing cognitive load or breaking existing journeys.
The approach
Data-driven prioritisation: we requested and analysed transactional data to isolate the most common betting behaviours. Singles, Accumulators, and Bet Builders formed the overwhelming majority of transactions, while complex system bets accounted for a negligible percentage. Competitor benchmarks were mapped against this data to validate focusing exclusively on these core workflows. We also mapped the most common stake inputs to identify clear user patterns.
Usability audit & friction mapping: the team ran remote usability testing sessions via UserTesting.com and gathered feedback from internal stakeholders to diagnose the existing QBS. The research uncovered several design flaws:
Redundant input steps: inputting a stake required a clunky two-step process (tapping the input, then triggering the keypad).
Excessive click-debt: placing a bet required an extra tap simply to dismiss the custom keyboard before the primary "Place Bet" button became accessible.
Real estate waste: a settings button occupied primary screen space despite knowledge that once configured it was rarely accessed again.
Fragmented hierarchy: the stake input field was disconnected from the primary call-to-action button, breaking natural scanning patterns.
Feature parity gaps: Users could not access free bets or bonuses within the QBS, and the transition between the mini-slip and the main slip was jarred and unintuitive.
Iterative testing: we established stringent screener questions to select testing participants and structured tests to purposely mitigate recency bias. We ran multiple prototype rounds, such as completely removing the Settings panel from the QBS, to see if it impacted user confidence (it did not).
the existing "Quick Bet Slip"
The output
Two-tap bet placement: we implemented permanent "Quick Stake" shortcuts into the default view, which dynamically swap to a dedicated keypad upon interaction. tapping a quick stake populates the value, establishing a true two-tap placement flow.
Streamlined layout: we stripped the settings button out of the QBS (retaining it only in the main slip) and moved the stake input field directly adjacent to the main call-to-action button, unifying the group.
Intuitive states: the slip remains open during active bet creation, allowing multiples to be created using the QBS. We introduced drag-to-open and drag-to-collapse gestures, following current trends.
Phased feature integration: due to API limitations with back-office systems, we intentionally restricted initial promotional integrations to available, high-priority bonus types.
in-progress wireframes
The impact
Enhanced B2B adoption: previously, several operators forced the full bet slip open with every selection to push multiples, hurting the user experience. Deploying this streamlined slip generated overwhelmingly positive client feedback, resulting in immediate adoption across our entire operator network.
Product consolidation: the redesign successfully served as a unified slip framework for both lottery and sportsbook products, lowering development and maintenance overhead.
Quicker interaction: the introduction of persistent "Quick Stake" shortcuts accounted for a substantial proportion of overall completed transactions, driving a small but noticeable upward shift in average stake values.
Decreased full betslip reliance: use of the heavy full betslip dropped significantly, as users could complete their core betting journeys entirely within the updated QBS.
examples of the updated betslips in use
QBS developer guide showing all states
Takeaways
Design for the 90%: trying to accommodate every edge case and exotic bet type within a quick-action interface defeats its entire purpose. Optimising for the 90% use-case path reduces maintenance debt, simplifies the codebase, and delivered maximum immediate value to the business.
Acknowledge API constraints: while we wanted a completely flawless bonus integration from day one, we had to launch with a phased solution because the backend architecture was not currently able to fully support the streamlined slip. Knowing when to launch with a stable MVP rather than delaying for backend parity is vital.