Executive summary
Over several years, FanDuel Casino evolved from static promotional value toward a more connected ecosystem of rewards, loyalty, generosity, and measurement.
I led design across key parts of that evolution, helping teams create clearer customer-value systems, stronger operating models, and better links between customer understanding, product mechanics, and business outcomes.
The public business context matters, but it is not the claim. Flutter public reporting can describe the broader business backdrop. This case study focuses on the design-leadership contribution inside that larger product evolution.
Business context
The business environment was maturing. FanDuel Casino was part of a broader U.S. growth story where rewards, engagement, product quality, and customer value were increasingly important.
The design challenge was to support that maturity without turning the product into a disconnected catalog of value moments. The work needed to help teams reason across customer perception, product mechanics, CRM moments, analytics, research, delivery, and business health.
Starting point: static promotions and casino bonus
Static promotions and casino bonus offers can create value. The issue is that isolated value moments are weaker as a relationship model when customers cannot easily understand persistent progress, earned value, or what to do next.
The stronger strategic question became: how should value behave as a system?
What changed
Before, the system could be understood as static promotions, casino bonus offers, fragmented value moments, limited persistent progression, and one-off campaign logic.
After, the direction became clearer: Rewards Hub, Loyalty / Rewards Club, Reward Box / Reward Machine, Generosity system, Measurement model, and Behavioral value loop.
That shift moved the work from shipping separate surfaces toward shaping a reusable customer-value model.
Strategy decision example
Design helped shift the organization from isolated rewards and promotional surfaces toward a connected customer-value ecosystem.
That meant treating value as a system of visibility, understanding, action, earning, progression, return behavior, and measurement, not just as a collection of offers.
Research signal to product decision
Perceived generosity became a useful product lens.
Customer understanding helped teams evaluate value beyond raw behavioral metrics, including whether rewards felt visible, understandable, earned, and worth returning for.
That signal helped connect research, product mechanics, and measurement planning before teams committed to specific experiences.
What this shows about my leadership
This work shows how I operate when design needs to move upstream.
The value was not only in making screens. It was in helping teams frame the business problem, understand the customer signal, align around a system model, and make better decisions before solutions hardened.
Reflection
The AI-era opportunity is personalization with judgment: using customer signals to improve relevance while protecting trust, transparency, measurement discipline, and responsible engagement.
If I were extending this work, I would keep improving the value loop responsibly: clearer instrumentation, deeper customer segmentation, stronger governance around reward and promotion mechanics, and better decision quality across product systems.
