Walk into any casino and look at the slot machines.
The layout isn't random. The machines closest to the entrance produce more noise — more jingles, more flashing lights, more simulated winning. The machines near the exits are often the loosest (highest payout rate) in the entire casino. The ones in the center, where most players end up, are the tightest.
Ask yourself: why?
This is the puzzle I open my product metrics course with. Not because casinos are a great industry to emulate — they're not — but because the logic of the layout reveals something true and non-obvious about how designed systems work on the people inside them.
The logic
The entrance machines are loud because first impressions calibrate expectations. If you walk in and see people winning, you calibrate your expectations for the whole casino accordingly. You've already formed a mental model of "what kind of place this is" before you've sat down.
The exit machines are loose for the same reason anchoring works in reverse: if you're leaving having lost, and you pass a machine that pays out in front of you, your memory of the session gets updated. The cognitive bias that makes losses hurt more than gains feel good works in the casino's favor everywhere except the exit — so they give the exit machines a better payout to moderate the regret.
The center machines are tight because that's where the committed players are. By the time you're in the center, you've already made the decision to play. The nudges that got you there no longer apply.
This is a decision architecture. It's designed with a user model in mind — a detailed, accurate model of how human beings make decisions in a specific context. The "product" (if we're willing to call it that) is fully coherent with its user model. Every element is doing a specific job.
What this teaches about product intuition
Product intuition isn't a sense you're born with. It's a habit of seeing designed systems as designed — not as natural phenomena, but as artifacts built by people who had beliefs about users, and then made choices in service of those beliefs.
The slot machine layout is legible as a system once you ask: what does the designer believe about the person using this? The answer is specific and operationalized. The entrance machines reveal a belief that first impressions anchor behavior. The exit machines reveal a belief that loss aversion peaks at the point of departure.
Every product has a user model buried inside it. Usually implicit. Often unexamined. Sometimes contradictory. The product intuition I'm trying to develop in students — and in myself — is the habit of surfacing that model and interrogating it.
When you see a product with a complicated onboarding flow, ask: what does this design believe about how motivated users are when they first arrive? When you see a product that buries the cancel button, ask: what does this design believe about why users leave? When you see a product that surfaces social proof prominently, ask: what does this design believe about how users make decisions?
These questions are almost always answerable. The answer almost always tells you something about the product's actual values — not the values the team espoused in the strategy deck, but the values embedded in the design choices.
The casino's honest problem
There's a reason I use the casino as the example rather than a product I admire.
The casino's design is technically brilliant and ethically compromised. It has an extremely accurate user model and uses it to exploit the people it models. The decision architecture is optimized for the casino's outcome, not the user's.
I want students to notice that these can come apart. A product can be technically excellent at driving the metrics it chose, and still be failing the people who use it. The casino is an extreme case. The Pulse case study — the mental health app with a green dashboard and a failing product — is a subtler one.
The question I want stuck in students' heads: who is this design for, really? Not in the mission statement sense. In the sense of: when the interests of the user and the interests of the business diverged, which way did the design tip?
That question, asked of every product you use, is the beginning of product intuition.