Bet at the Table (PokerStars)

High Level Overview

Following on from the success of QuickBet, we set about expanding the scope of this to allow users to browse and bet on various sporting events.

Planning

I worked with all relevant stakeholders in defining how the QuickBet feature could be expanded such that users could browse for and bet on additional sporting events.

Defining Scope

It was important to understand how the feature could be expanded while not compromising the simplicity and intuitiveness of the original QuickBet feature.

Dedicated Analytics

I worked with the BI team in planning feature specific metrics we wanted to track and review in Data Studio post- launch, including poker events which could influence betting habits.

Starting with the end in mind

While only relevant to football at first, we wanted to cater for additional sports and events in future, and ensure that the feature was scalable so as to accommodate such requirements.

Game Carousel

The game carousel which sits below the table bar allows the player to make bets without worrying about missing a hand.

Categorisation

Categories allow the user to quickly navigate to their game of choice and are dynamic based on the event type.

Bet Options

In contrast to QuickBet, Bet at the Tables allows the user to navigate to their open bets and betting history.

Navigational Memory

So as not to slow down the poker games, the feature remembers where the user is in the betting process when switching.

Analytics

Identified the feature specific tracking requirements and created a dedicated Data Studio dashboard to track behaviour.

Notifications

Wrote the rules as to when to surface or suppress prompts based on the action at the poker table at any given time.

Such was the success of Quickbet, there was a demand to expand this to include a broader range of features as well as additional sporting events.

Some more information…

Background How it was Built My Scope

How do you develop a feature loved for its simplicity into a more rounded experience?

It was important to remember that the purpose of QuickBet was to allow the player to make bets on their chosen sports events without leaving the poker table, or even missing playing any poker hands.

So the question became, can we enhance this feature, to incorporate open bet information, bet history, event selection and categorisation without negatively impacting the simplicity of the original QuickBet functionalist that players had come to love.

The answer was yes.

How do we go about aligning a large shift to native within internal teams? 

Since we knew the user may spend more time engaging with this feature than they typically would with the QuickBet feature, owing simply to the more expansive navigational options, we tweaked the rules surrounding when notifications were surfaced to the user, taking poker table events into consideration.

We also made changes to when notifications were surfaced based on how many tables the user had open at any given time. Once we ensured the poker experience was not going to be compromised, we began rolling out the product and carefully gauging how users engaged with the enhanced experience when compared to QuickBet, so as ensure the action at the table was not slowed down. Feedback was positive and twenty-one percent of all UK real money players engaged with the feature and placed a bet in the first month of its release.

What were my main areas of focus?

Strategic

  • Working with the business to identify how the Quickbet feature can be extended to cover additional sporting events.
  • Working with key stakeholders in defining the feature HRL.


Product

  • Translating the Bet at the Tables feature HRL into well-defined user stories, and acceptance test criteria for both the computer client and the mobile apps, including for all related menus.
  • Refining and expanding the logic for how and when messages would be surfaced to the user.
  • Working with cross-functional teams and stakeholders including: design, compliance, BI, engineering and testing.


Testing

  • Assisting the QA teams in testing the feature to ensure it met the requirements.


Reporting

  • Reporting on the progress and feature rollout.
  • Reporting on feature adoption, and positive impact on revenue.
  • Presenting feature demos to stakeholders.