A Casino is a Small City

After spending 2 decades working in the gaming industry, I always enjoy hearing the perspectives of people outside the industry.  I frequently hear about some recent experience they had at the property, whether it was a big win on the gaming floor, a memorable meal at the steakhouse, a breathtaking show they watched, or a relaxing afternoon at the pool. 

What none of them realize is what takes place behind the scenes at a casino. 

Behind every guest experience is an organization made up of a diverse group of teams: finance, cage operations, count, surveillance, compliance, IT, marketing, hospitality, and more. Every department has different priorities, but none operate in isolation. Decisions made in one area almost always affect another.

Over the years, I’ve come to think about casinos a little differently.

A casino isn’t just one business. It’s a small city. 

And the point of that comparison isn’t size — it’s that a city’s neighborhoods run on their own schedules, budgets, and incentives, each making sensible decisions for its own reasons without always seeing how those decisions land next door.

One of the things I enjoy most about visiting customer properties is seeing how differently each team experiences the same operation:

 

—Spend an hour with the cage and you’ll hear about optimizing guest service on the front lines. 

—Talk to the compliance director and the conversation shifts to minimizing risk and ensuring accountability.

—Sit with finance and the focus becomes proper reconciliation, accurate reporting, and return on investment.

 

Every conversation is different because every team is responsible for solving a different problem. None of those perspectives are more important than another but all too frequently I notice properties that measure these teams on different outcomes. 

This results in each team optimizing to achieve their own goals, which is exactly why a department can be doing its job well and still be working against the grain of the operation without knowing it.  The best operators that I have come across do a really good job at driving alignment across all teams with a shared vision, goal and desired outcomes. 

 

Early in my career, I assumed better software meant adding more features and capabilities. Over time, I realized that understanding the users mattered much more than adding functionality. Before you improve a process, you have to understand who depends on it, what happens before it begins, and what happens after it’s finished.

One of the first things I tell product teams is that nothing interesting happens in the office.

Instead, the best product decisions are made by understanding how people actually do their jobs. That means spending time on casino floors, in cage operations, inside count rooms, and alongside the people responsible for keeping daily operations moving. I believe watching experienced operators work often reveals opportunities that would never surface during a planning meeting or while looking at a product roadmap.

Sometimes the challenge isn’t that people lack information, but that information exists in different places, arrives at different times, or isn’t available to the people who need it most.

Every department may be performing well individually while the organization as a whole still experiences unnecessary delays, duplicated work, or avoidable inefficiencies. A change one department makes for good reasons — a new cutoff time, a revised count procedure, a different reporting cadence — often shows up somewhere else as extra work, a gap in visibility, or a decision made later than it needed to be. That’s just the reality of managing an operation as complex as a casino, and recognizing that level of interdependence is most of the work.

Modern casinos manage cash, compliance, hospitality, security, technology, and guest experience simultaneously. Product teams shouldn’t try to remove that complexity. They should help people move through it with greater clarity and confidence.

These days, I spend far less time asking what feature should come next and far more time asking how information moves through an organization.

If one department has better visibility, who else benefits? If one process becomes more efficient, what decisions become easier downstream? Those are the questions that ultimately lead to better products.

For example:

—When finance receives information sooner, reconciliation becomes more efficient.

—When cage operations have greater visibility into cash movement, they can make better operational decisions.

—When compliance, surveillance, and audit teams have consistent information, investigations become more straightforward and confidence in the process grows.

Improvements like these may happen within a single workflow, but their impact rarely stays there, which is what makes casino operations so fascinating. Every decision affects something beyond the department where it began, usually more than one, and usually in places very few thought to check. Better visibility leads to better decisions. Better coordination creates stronger operations.

The longer I’ve worked alongside casino operators, the more I’ve come to appreciate that you’re never solving just one problem. You’re strengthening the connections that allow the entire operation to function.

A casino isn’t just one business.

 

It’s a small city.