CLIENT
IGT
ROLE
Product Designer
PLATFORM
SaaS, Real-time Operations
DURATION
4 Years
Portfolio
Floor Net
Floor Net
Floor Net was designed as an operational visibility layer for casino floor teams. The product helps users monitor machine status, identify issues faster, and move from scattered operational signals to informed action.
Context and Role
Product Context
Floor Net centralizes live casino floor information, including machine activity, status flags, hardware and software signals, alerts, and operational exceptions.
What I owned
- UX/UI design
- Information architecture
- Operational dashboard structure
- Alert and status patterns
- Workflow and interaction design
- Design documentation
- Stakeholder alignment
Users
Casino Floor teams
Monitor floor activity, machine status, and exceptions during daily operations.
Support / technical teams
Review machine data, logs, groups, and issue details to investigate and resolve problems.
Operations managers
Need visibility into floor performance, recurring issues, and operational patterns.
Overview
Casino floor operations depend on reliable live information. Floor Net brings together machine activity, status flags, hardware data, software information, alerts, and operational signals into a single monitoring environment. The product acts as a hub for floor teams, helping them understand what is happening, identify problems faster, and coordinate daily actions with more confidence.
Operational visibility
Structure machine status, alerts, and floor activity so teams can understand the state of the floor at a glance.
Actionable workflows
Create clearer paths from monitoring to investigation, helping users identify issues, review details, and take the next operational step.
The Challenge
The main challenge was making a complex live environment easier to understand without removing the operational depth that expert users rely on. Floor teams needed speed, accuracy, and context, but the interface also had to support large volumes of machines, alerts, and changing conditions.
Simplify the process without sacrificing context or operational depth.
Critical machine information was difficult to scan across dense operational views.
Operational alerts lacked enough hierarchy to support fast decision-making.
Users had to move between monitoring, investigation, and action through disconnected paths.
Design decisions
The design decisions focused on creating a clearer operational layer: one that prioritized machine status, highlighted exceptions, and connected monitoring workflows with the actions floor teams needed to take.
Operational Visibility
Structured machine status, floor activity, and exception states into clearer views so users could understand the floor at a glance without losing access to detail.
Action-oriented Workflows
Designed flows around the decisions operators need to make: identifying issues, resetting PODs, reviewing groups, checking logs, and gathering machine data.
Scalable information patterns
Created reusable patterns for tables, filters, status flags, alerts, and user-specific views to support different levels of operational complexity without compromising consistency.
Process
The process started by understanding how casino teams monitor live operations, what information they prioritize, and where friction appears when they need to investigate or act.
Discovery Phase
Mapped user roles, operational routines, machine states, alert types, and the level of detail required by floor teams, managers, and support teams.
User Path Enhancement
Designed repeated workflows with familiar layouts and consistent decision points, helping users move faster without relearning each flow.
Quality-of-life Improvements
Refined interaction patterns, table behavior, and workflow details through stakeholder feedback, making the product easier to extend with future features and technical integrations.
Impact
Floor Net became a stronger operational visibility layer, helping casino teams scan dense machine data faster, follow more predictable workflows, and reuse scalable patterns across future system modules.
Building the product across the differen stages, from the basic port from the legacy system to the 2nd iteration of the product allowed me design, test and enhance each step for the product and give a clear path of how the product needs to work.
↓20%
Less time required to identify machine issues
+6
Client-specific operational flows created
+ 22%
Time saved across repeated workflows
- 10%
Training time reduced through more consistent patterns