Casino Operations — Internal Management System
Designed a role-based internal system that brought floor operations, cash desk, staff and player activity of a casino app into one clear workspace.
Client
Casino Gaming Operator (confidential)
Industry
Gaming & Hospitality
Services
UI/UX Design, Internal Tool Design, Dashboard UX, Design System
The Challenge
One crowded screen for five very different jobs
Behind the casino app, daily operations were running on spreadsheets, WhatsApp groups and an outdated admin panel. Floor managers, cashiers and admins all looked at the same crowded screen, so critical alerts got buried and every role had to dig for the information it needed.
Why a shared screen fails
A screen that serves everyone prioritises no one. Each role is forced to visually filter out the majority of what is in front of it before finding the part that matters, and that filtering cost is paid on every single interaction across every shift.
The consequences are specific rather than abstract. A cashier hunting through irrelevant floor data to complete a transaction is slower and more error-prone. A floor manager scanning cash-desk detail to find a table issue is looking in the wrong place. And an alert that appears in a crowded interface alongside everything else is not really an alert at all.
In a round-the-clock operation the cost of a missed alert is immediate and sometimes unrecoverable, which is what made this a priority rather than a tidying exercise.
Reconciliation after the fact
End-of-day cash reconciliation was slow and manual, and there was no single place to see what was happening on the floor right now.
Manual reconciliation at the end of a shift means discrepancies surface hours after the moment they could have been resolved — when the staff involved have left, the context is gone, and what should have been a thirty-second correction becomes an investigation.
An environment most internal tools ignore
There was also a physical constraint. This is a low-light, twenty-four-hour operation. Staff work long night shifts, often standing, often reading quickly between tasks.
An interface designed for a bright office is genuinely harder to use in that setting — brighter than the room, more tiring across a long shift, and slower to scan under pressure. Designing for the actual environment was a functional requirement rather than an aesthetic preference.
What needed to be solved
Separate, role-specific workspaces instead of one shared screen.
Alerts that reach the person who can act on them rather than everyone equally.
A live view of floor activity, replacing after-the-fact reporting.
Cash desk flows that reduce errors at the counter and make reconciliation continuous rather than end-of-day.
An interface readable in low light across long shifts.
A consistent component system so later modules would not feel like separate tools.
A clean handoff the development team could build from without reinterpretation.
What We Did
We designed one system that shows each team only what it needs.
Our approach
The guiding rule throughout was subtraction. In an operational tool used under time pressure, removing information is usually what makes the remaining information usable — so every workspace was defined as much by what it hides as by what it shows.
01 — Research & task mapping
We spoke with floor managers, cashiers and supervisors and mapped every task they perform in a shift — what they do, in what order, how often, and what they need in front of them at each point.
That mapping is what justified the structure rather than assuming it. Once the tasks were written out role by role, it became obvious how little genuine overlap existed between them — and therefore how much the shared screen was costing every role simultaneously.
Talking to the people doing the work also surfaced the informal workarounds that had grown up around the old panel. Those workarounds are usually where the real process lives, and they told us which gaps the system actually had to close.
This became the foundation for a role-based structure instead of one screen for everyone.
02 — Role-based architecture
We defined permissions and dashboards for five roles, so a cashier, a floor manager and an admin each land on a workspace built around their own job.
Each workspace shows what that role acts on and hides what it does not. The practical test was whether someone arriving mid-shift could see their priorities without scrolling, filtering or interpreting.
Permissions were treated as part of the design rather than a later configuration step, because in an operation handling cash and player data, who can see what is a structural question, not a setting.
03 — Core modules
We designed a live floor overview, a cash desk module with step-by-step transaction flows, staff and shift scheduling, player profiles, and an alerts centre that surfaces only what needs action.
The cash desk was deliberately designed as a guided flow rather than a form. Guiding a transaction step by step is slower to design and faster to use, and it removes the class of error that creates reconciliation discrepancies in the first place — fixing the problem at its source instead of reporting it better.
The alerts centre was built on the principle that an alert nobody acts on is noise. Routing each alert to the role that owns it is the difference between a notification system and an operational one.
The live floor overview replaced the reconstructed, after-the-fact picture with a current one, so decisions during a shift could be made on what is happening rather than what happened.
04 — UI built for long shifts
A dark, high-contrast interface designed for low-light environments and long working hours, backed by a reusable component library and a clean Figma handoff for the development team.
Dark UI here is a working requirement, not a style choice. It reduces eye strain across a night shift and keeps screens from lighting a deliberately dim floor, while high contrast keeps critical numbers readable at a glance by someone standing and moving.
The component library means later modules can be added without the system fragmenting into visibly different tools, and the Figma handoff was structured so the development team could build from it directly rather than reinterpreting intent.
Services delivered
UI/UX design
Internal tool design
Dashboard UX
Design system and component library
The Outcome
From scattered tools to one operational system.
Each team now works from a workspace designed for its own role. Alerts reach the right person, daily tasks take fewer steps, and cash reconciliation is visible in real time instead of being a manual end-of-day exercise.
The spreadsheets, WhatsApp groups and shared admin panel were replaced by a single system with one live view of the operation underneath it.
5 role-based workspaces
Each role lands on a workspace built around its own tasks instead of filtering a shared screen on every interaction.
1 live view for all operations
Floor activity, cash desk and staff visible in real time rather than reconstructed after the shift ends.
Dark UI, built for long night shifts
A high-contrast interface designed for the low-light, round-the-clock environment the system is actually used in.
Floor
A live view of tables, staff and activity for managers.
Cash desk
Guided transaction flows that reduce errors at the counter and make reconciliation continuous.
Team
Shift scheduling and staff tracking in one place.
Alerts
Routed to the role that owns them, so they function as instructions rather than noise.
What this unlocked
A design system and component library that let further modules be added to the same system rather than built as yet another separate tool — which is how the original fragmentation happened in the first place.
Role-based workspaces
Live view for all operations
Built for long night shifts
