Constraint-free cases teach the wrong reflex
An exercise that maximises conversion, usage, or revenue without limits on what may be sold, shown, paid for, or promoted is not neutral. It teaches teams to treat regulation as legal review after the product decision. In regulated products, rules change inventory, journeys, metric interpretation, operating cost, and acceptable risk.
A casino-lobby case that puts the highest-margin game in every prominent slot teaches a dangerous shortcut. The first question is which games this person may see in this jurisdiction, on this device, at this lifecycle stage, under current safer-gambling, licensing, and supplier restrictions. Simulations should expose that constraint before a solution is drafted.
The aim is not to make PMs lawyers, but to train judgment: find value within fixed boundaries, spot risk created by a change, and ask the right teams for evidence before committing engineering capacity or campaign spend.
Model the operating envelope first
Start with an operating envelope, not a feature brief. It defines non-negotiable facts and separates hard prohibitions from choices needing approval, monitoring, or explicit trade-offs.
In iGaming, a jurisdiction may permit slots but not live casino; a supplier agreement may exclude titles from a territory; a payment method may reject certain deposit patterns; and players with a safer-gambling restriction must not receive promotions. An idea that ignores any of these fails before projected uplift matters.
Write constraints operationally. “Comply with local law” gives no decision; “Users in GEO A cannot launch provider X titles; the catalogue service receives the restriction through a jurisdiction flag” is testable. Name the system or team owning every rule, since ownership ambiguity lets bad decisions survive.
Separate four rule classes:
- Eligibility rules — age, identity status, jurisdiction, account state, self-exclusion, and product permissions decide whether an action is allowed.
- Availability rules — catalogue rights, supplier restrictions, device support, limits, and local payment coverage decide what can be offered.
- Process rules — KYC, AML review, withdrawal checks, consent, and recordkeeping affect experience sequence and timing.
- Commercial guardrails — bonus cost, provider fees, payment cost, tax, fraud exposure, and service capacity decide whether an allowed idea is worth operating.
The first three define permitted space; the fourth determines whether effort is justified within it. Do not turn legal restrictions into conversion trade-offs or margin concerns into prohibitions.
Turn rules into decision states
Rules become useful when they change product state. Avoid a static compliance appendix: eligibility, availability, and commercial context should change during the exercise.
For example, repeat-deposit conversion weakens among mobile casino users after a catalogue refresh. The team proposes a personalised “continue playing” module and free-spin offer. Inject three events: a provider removes games from one GEO; a PSP reports higher decline rates for the preferred deposit method; and responsible gambling requires suppression of a cohort with risky intensity markers. The original plan is no longer valid.
Participants must revise the lobby, CRM trigger, payment path, measurement design, and support communication. A strong response narrows exposure to eligible users, substitutes permitted content, shows a payment fallback only where approved, and moves affected cohorts to a non-promotional service journey. “Keep the campaign live and monitor results” is weak.
Each simulation card needs five fields:
- Decision owner — PM, growth lead, payments manager, or accountable cross-functional group.
- Objective — a bounded outcome, such as improving qualified second-deposit conversion without increasing bonus-to-GGR ratio or complaint rate.
- Known constraints — fixed rules.
- Missing evidence — information to request before choosing, such as payment approval by GEO or game-launch rate by eligibility state.
- New information — an event testing whether participants can revise without defending sunk effort.
Missing evidence matters: judgment is not fast opinion. It includes knowing when a cohort cut, legal interpretation, supplier confirmation, or risk review is required.
Storefront eligibility changes the product
A storefront is not only categories, banners, search, and rankings; in regulated products it is an allocation engine. It determines which permitted options are visible, how unavailable options are explained, and which users are removed from an experience.
A casino storefront cannot rank every game for every visitor. Identity state, GEO, supplier rights, device support, account restrictions, and responsible-gambling suppressions shape candidates before merchandising. How an iGaming storefront is assembled makes this hidden logic clear: catalogue, search, and merchandising depend on rules determining what users can see.
Build exercises around: filter first, rank second, render third. Map failures at every stage. Filtering can expose unavailable content; ranking can over-concentrate attention on one provider or high-volatility games; rendering can dead-end when a favourite disappears without explanation or substitute.
Require a fallback, not only a primary experience. If a game is unavailable, should search hide it, label it, or offer a permitted alternative? Legal advice, contracts, and player expectations determine the answer. Reward a reasoned, documented choice, not a universal pattern.
Personalisation ranks inside permitted space
Personalisation does not cancel rules: it follows eligibility filtering and precedes delivery. Treating recommendations as unconstrained relevance engines teaches the wrong architecture and commercial instinct.
The question is not “Which game will this player click?” but “Which permitted content can this player discover without safety, fairness, or margin problems?” Catalogue operations behind iGaming personalisation shows why this layer needs clean catalogue data, rule-aware candidates, and controls beyond relevance score.
Give teams conflicting objectives: increase game-launch rate for new depositors, improve provider diversity, and avoid promoting high-intensity content to users with relevant risk markers. They must define precedence: safety and legal suppressions first, then availability and contractual rules, then preference, recency, popularity, margin, and novelty.
Score decision policy, not “use machine learning.” A defensible policy names input signals, excluded cohorts, cold-start fallback, human exception owner, and guardrails that can stop the experience. Test popularity bias: repeatedly serving dominant games may lift short-term launches while weakening discovery and supplier diversity.
Privacy belongs in the scenario. Behavioural data may exist without consent for a communication channel; a team may personalise an onsite lobby but not send the related push. Separate data availability, permission to use it, and the resulting product action.
Score judgment, not headline growth
Do not reward the biggest projected GGR lift. It rewards optimistic arithmetic and hiding costs outside the primary metric. Score the chain from decision to consequence.
Use an outcome such as eligible-player game-launch rate, qualified second-deposit conversion, or retained NGR by cohort, with guardrails:
- Commercial guardrail — bonus-to-GGR ratio, payment-cost-adjusted NGR, provider-fee exposure, or contribution margin.
- Trust guardrail — withdrawal complaints, payment-error contacts, unavailable-content searches, or support escalations.
- Risk guardrail — fraud flags, duplicate-account signals, KYC backlog, and responsible-gambling intervention markers.
- Product guardrail — page speed, game-load failures, search success, and users reaching an empty state.
Ask for expected direction, not invented percentages; cases rarely support precise forecasts. “Reduce failed search journeys among affected GEOs while monitoring whether substitutes lower session depth” is stronger than a made-up uplift.
Test metric literacy. GGR may rise because actual RTP falls in a short window, not because product value increased. Repeat deposits may rise because a promotion pulled activity forward, not because retention improved. Credit participants who identify alternatives and propose cohort-based readouts.
Time pressure reveals hidden dependencies
Useful simulations include an operational clock: a rule change, supplier outage, payment incident, or campaign deadline forces incomplete-information decisions. This shifts training from feature critique to product management.
Pressure should reveal dependencies, not create theatrical crisis. A new deposit fallback requires checking PSP approval, GEO-specific cashier presentation, support error copy, and reconciliation. Suppressing a promotion requires shared exclusion logic across email, push, SMS, onsite messages, affiliate landing pages, and host outreach.
Create credible conflict: Growth wants a campaign before a major sporting event; Compliance cannot confirm that revised copy meets local advertising restrictions; Payments wants to limit a method after chargeback risk changes; Product wants the launch date. The best response identifies what cannot wait, what needs escalation, and the reversible action that reduces exposure while facts are checked.
Do not grade aggressive activity. Grade protection of restricted users, avoidance of unsupported legal assumptions, preservation of withdrawal trust, and clear leadership trade-offs.
Replay decisions through the evidence trail
Post-exercise replay makes learning durable. Reconstruct what the team knew, assumed, and failed to ask; which constraint changed the answer; and which metric validates it after launch.
Use this review template:
- Decision — chosen action and scope.
- Permitted space — eligibility, availability, and process rules allowing it.
- Trade-off — accepted revenue, experience, operational, or risk cost.
- Evidence gap — data or interpretation still needed.
- Owner and deadline — named role for the next check.
- Stop condition — signal to pause, roll back, or escalate.
This exposes polished solutions with no reversal mechanism. In regulated products, reversibility has commercial value: phased release to an eligible cohort, manual review for uncertain cases, or a temporary substitute may be less elegant than global release but limits the cost of a wrong assumption.
Distinguish knowledge from judgment errors. Missing a supplier restriction suggests a weak source-of-truth process; seeing it and ignoring it is a judgment failure. The first needs better documentation and instrumentation; the second, clearer accountability and escalation norms.
Build judgment before the roadmap
PM training should make constraints native to product work, not last-minute obstruction. Strong exercises start with a commercial objective, state permitted space, introduce changing conditions, and score reasoning. The PM’s job is not the most attractive theoretical answer, but the best defensible answer that operates safely, legally, and profitably.
Start with one real workflow: game recommendation, deposit route, account-verification step, bonus trigger, or withdrawal journey. Map rules, owners, inputs, failure states, and user-facing fallbacks. Then add an event that invalidates the obvious first solution. If participants ask which rule applies, who owns the evidence, and how the decision will be monitored, the simulation has trained the right instinct.
The roadmap can wait. Product judgment starts at the boundary of what the business is permitted to do.