SELECTED WORK / PRODUCT DESIGN

M5 EGM M&T limits

M5 EGM M&T limits

M5 EGM M&T limits

The platform has all the information required by the player and the casino to operate in normal scenarios, such as playing games, viewing the account balance, the balance used on the machine, player level, ordering drinks, or making reservations for casino amenities.

The platform has all the information required by the player and the casino to operate in normal scenarios, such as playing games, viewing the account balance, the balance used on the machine, player level, ordering drinks, or making reservations for casino amenities.

CLIENT

IGT

ROLE

Senior Product Designer

PLATFORM

Gov Compliance, Real-time Operations

DURATION

3 Months

Context and Role

Context and Role

Context and Role

Product context

Product context

Product context

M5 is a player-facing casino platform used by casino operators to manage account information, machine activity, service workflows, limits, alerts, and required Responsible Gaming acknowledgements.

What I owned

What I owned

What I owned

- End-to-end product design
- UX/UI design
- Information architecture
- Workflow and interaction design
- Documentation and specifications
- Stakeholder alignment
- Compliance collaboration

Who this supports

Who this supports

Who this supports

Players

Manage limits, receive alerts, and acknowledge required messages.

Casino Operators

Configure rules, monitor compliance, and support day-to-day casino operations.

Compliance Stakeholders

Ensure that required limits, alerts, and acknowledgements meet regulatory expectations.

Impact

Impact

Impact

Results reflect post-validation business impact and client adoption after the Responsible Gaming release.

Results reflect post-validation business impact and client adoption after the Responsible Gaming release.

The Responsible Gaming flow helped the product meet compliance requirements, improved client confidence, and created a feature foundation that could be reused for future regulated markets.

+5

+5

Contract extensions

2

2

New clients

+7%

+7%

Casino revenue impact

+10%

+10%

Feature-qualified leads

Component focus

Component focus

Component focus

User Path

User Path

User Path

Mapped the end-to-end Responsible Gaming flow, including system triggers, player actions, acknowledgement states, and navigation paths.

Overview

Overview

Overview

M5 is a player-facing casino platform with years of operational logic, account information, machine activity, and service workflows. The challenge was to introduce Responsible Gaming requirements into this legacy environment without making the experience feel intimidating, fragmented, or disconnected from the existing product.

M5 is a player-facing casino platform with years of operational logic, account information, machine activity, and service workflows. The challenge was to introduce Responsible Gaming requirements into this legacy environment without making the experience feel intimidating, fragmented, or disconnected from the existing product.

Limit Tracking

Limit Tracking

Limit Tracking

Make player limits visible, understandable, and aligned with Responsible Gaming requirements.

Gov. Compliance

Gov. Compliance

Gov. Compliance

Align the experience with regulatory requirements while helping casinos promote safer play.

Gov. Compliance

Align the experience with regulatory requirements while helping casinos promote safer play.

The Challenge

The Challenge

The Challenge

The challenge was not only to add new screens, but to integrate a compliance-sensitive flow into a legacy product with existing navigation patterns, API dependencies, and government validation requirements. The design needed to make limits, alerts, and acknowledgements clear enough for players, while giving the business confidence that the experience could meet regulatory expectations.

The challenge was not only to add new screens, but to integrate a compliance-sensitive flow into a legacy product with existing navigation patterns, API dependencies, and government validation requirements. The design needed to make limits, alerts, and acknowledgements clear enough for players, while giving the business confidence that the experience could meet regulatory expectations.

The legacy product relied on outdated interaction patterns and technical dependencies, making the new compliance flow harder to integrate.

The legacy product relied on outdated interaction patterns and technical dependencies, making the new compliance flow harder to integrate.

The legacy product relied on outdated interaction patterns and technical dependencies, making the new compliance flow harder to integrate.

I collaborated with the Architecture team to understand legacy API constraints, define the required data calls, and translate those dependencies into a clearer UI flow.

I collaborated with the Architecture team to understand legacy API constraints, define the required data calls, and translate those dependencies into a clearer UI flow.

Design Decisions

Design Decisions

Design Decisions

The design decisions focused on making compliance information clear, reducing unnecessary steps, and translating legacy navigation patterns into user flows that could be reviewed by Product, Architecture, and Engineering teams.

The design decisions focused on making compliance information clear, reducing unnecessary steps, and translating legacy navigation patterns into user flows that could be reviewed by Product, Architecture, and Engineering teams.

User Path

User Path

User Path

Mapped the end-to-end Responsible Gaming flow, including system triggers, player actions, acknowledgement states, and navigation paths.

Data collection and compliance

Data collection and compliance

Data collection and compliance

Designed read-only compliance screens to surface required information without introducing unnecessary edit permissions or additional security complexity.

Flags for acknowledgement.

Flags for acknowledgement.

Flags for acknowledgement.

Created alert and acknowledgement patterns to ensure players were clearly informed before exceeding predefined limits.

Process

Process

Process

Built a compliance-oriented product flow by defining alerts, updating cross-product interactions, and translating legacy blueprints into clearer visual documentation.

Built a compliance-oriented product flow by defining alerts, updating cross-product interactions, and translating legacy blueprints into clearer visual documentation.

Discovery Phase

Discovery Phase

Discovery Phase

Translated legacy text-based navigation into readable interaction flows so the Product Owner and Tech Lead could evaluate what needed to move into the new UI.

Workflow Building

Workflow Building

Workflow Building

Mapped system dependencies, triggers, screens, and interactions to replace command-line documentation with visual paths that could support product and engineering alignment.

Validation & Iteration

Validation & Iteration

Validation & Iteration

While the UI was being built, a parallel product team validated the API calls and real-time data updates required to support the new compliance flow. My work focused on refining the information architecture, user paths, alerts, and acknowledgement states so the experience could be reviewed by internal stakeholders and aligned with government requirements.

Let’s make
it clear!

Let’s make
it clear!

LinkedIn ↗

SCALABRIN

SCALABRIN

SCALABRIN

© 2026 SCALABRIN. Built for complex systems, real operations, and scalable product experiences.