Pick’Em 2025

A complete reimagining of the NBA's prediction game. Live-play energy and deep gamification brought to a platform that now attracts millions of players and drove a significant rise in engagement.

1. Context

The mandate that landed on my desk was one of high-stakes digital transformation. The National Basketball Association (NBA) possessed a legacy asset in “Pick’Em,” a predictive gaming format that had, for several years, existed as a quiet, background utility within their digital universe. While it had successfully accrued hundreds of thousands of players, the product was suffering from acute technical debt and a lack of visual or mechanical urgency. It was a passive experience in an increasingly active attention economy. My objective was to lead the reimagining of this experience, shifting it from a stagnant weekly chore into a dynamic, “super-live” central hub for basketball prophecy.

From a commercial perspective, the stakes for Monterosa were equally significant. We were in the midst of a foundational pivot, transitioning the business from a bespoke, resource-heavy agency model to a product-led SaaS powerhouse. The NBA Pick’Em project was not merely a client activation; it was the primary testing ground for our “FanKit” web toolkit. We had to balance the immediate, high-pressure requirements of a Tier-1 global brand with the long-term necessity of building a modular, sport-agnostic product architecture. The “legacy debt” of the previous Pick’Em version acted as a drag on fan sentiment. Users would engage on a Monday, make a few static selections, and then disappear until the following week. This lack of “dwell time” meant the NBA was failing to capitalise on the high-intent data of its most valuable fans.

Furthermore, the business logic behind this pivot was rooted in Product-Led Growth (PLG). The NBA’s primary KPI was not just “engagement” as a vanity metric, but the aggressive acquisition of NBA ID registrations. To achieve this, the product needed to feel like an indispensable companion to the live broadcast. We were tasked with moving away from the “agency” habit of building one-off code for specific games and instead engineering a system that could handle the immense concurrency of the NBA season while providing a “turnkey” experience for the league’s operations team. The survival of our contract extension depended on our ability to prove that a modular, configuration-over-customisation approach could outperform bespoke builds in both speed-to-market and user retention.

The technical challenge was formidable. We had to synchronise real-time data feeds with a front-end that felt instantaneous to the user. In the world of 0 to 1 product leadership, the focus is always on surgical interventions. We weren’t just “updating” a game; we were re-architecting the commercial reality of how the NBA interacts with its global audience. The legacy scale was already impressive, but it was brittle. Our goal was to harden that infrastructure and wrap it in a UX that felt “aggressively right” for the modern sports consumer who demands immediate feedback, social proof, and deep gamification.

2. Intelligence

The strategic synthesis for the new Pick’Em platform was informed by a career-long obsession with fan psychology and the mechanics of “live-play” wins. We didn’t start with a blank canvas; we leveraged the “intelligence” gathered from high-concurrency successes such as the live play-along for “Who Wants to Be a Millionaire” and the German trivia phenomenon “Quip.” In those environments, we learned that the “Aha!” moment for a user occurs when their digital action is validated by a real-world event in near real-time. We knew that the core of the NBA fan experience is the desire to demonstrate superior knowledge. Fans don’t just want to watch; they want to be “right” more often than their peers.

The discovery phase identified a terminal flaw in the legacy product: “Leaderboard Fatigue.” In traditional season-long games, if a player performs poorly in week one, they are mathematically eliminated from the top tier by week three. This creates a massive churn point. Our strategic pivot was to shift the urgency from “weekly” to “event-led.” We introduced the concept of “Fresh Starts.” By breaking the season into modular “Game Weeks,” single-game challenges, and even quarter-specific sprints, we ensured that every time a user opened the app, they had a non-zero chance of winning. This psychological reset is a fundamental driver of retention. It removes the penalty of past failure and incentivises the “streak” behaviour that characterizes high-retention products.

We also dug deep into the “punditry” aspect of basketball culture. We observed how Twitch streamers and YouTube pundits engaged with stats. This led to the intelligence that Pick’Em shouldn’t just be about “who wins,” but about the granular “sub-plots” of the game. Will a specific player make a certain amount of rebounds? Will the team be ahead by the second quarter? By diversifying the “pick” types, we created multiple entry points for different types of fans, from the casual viewer to the hardcore “stat-head.” This was about moving from a binary win/loss logic to a multi-layered “points economy.”

The strategic synthesis extended to the sponsorship layer. We realised that for a brand like Nike to find value, the sponsorship couldn’t just be a banner ad. It had to be a mechanic. We conceptualised “Point Boosts” associated with specific Nike-sponsored players or “Double-Point Weekends” to coincide with major product drops. This turned the commercial reality of the platform into a game mechanic itself. The intelligence was clear: if the sponsorship adds value to the user’s score, the user perceives the sponsor as a partner in their success rather than an interruption. This shift from “interruption” to “utility” is the hallmark of a mature, product-led growth strategy.

Finally, we synthesised our findings into a “Dual-Track” roadmap. Track one was the “NBA Experience,” focused on the aesthetics of the court and the specific cadence of the basketball season. Track two was the “FanKit Core,” focused on the underlying logic of a predictive engine that didn’t care if the ball was being bounced or kicked. This intellectual separation allowed us to build a product that was “sport-agnostic” at its heart while remaining “fan-obsessed” on the surface. We weren’t just building a game for the NBA; we were building the definitive toolkit for global fan engagement.

3. Concept

The conceptual architecture of the new Pick’Em was built on the tension between the Tier-1 client’s demands and our internal SaaS roadmap. As the UX Lead and Product Owner for FanKit, my role was to ensure that every “bespoke” request from the NBA was distilled into a reusable “feature” for our core product. We moved away from the “agency” trap of hard-coding solutions. Instead, we conceived a “Modular Hub” design. This wasn’t a single game; it was a container for “Experiences.” This architecture allowed the NBA to toggle different game types—from simple polls to complex predictors—without requiring a new deployment.

A central piece of this concept was the “Number Predictor” slider. We moved away from simple multiple-choice buttons to a more tactile, “analogue” UI mechanic. Users were asked questions like “How many three-pointers will be made?” and responded by sliding a selector across a range. This created a much higher level of “micro-engagement.” The user had to consider the number, feel the resistance of the slider, and make a conscious choice. From a product standpoint, this was a “White Label” win. By designing this as a generic “Number Picker” element, we created a tool that could just as easily ask an F1 fan about pit-stop seconds or a Premier League fan about corner counts.

We also concepted a sophisticated “Streak and Reward” system. The idea was to gamify the act of returning. We introduced avatars, taglines, and “Attack vs Defence” statistics for player profiles. This allowed users to build a digital identity within the NBA universe. If you were a “Defensive Expert,” your profile reflected your accuracy in predicting low-scoring quarters. This “Roleplay” layer added a dimension of social proof that was missing from the legacy product. We looked at “Winner vs Rejected” ideation: we rejected the idea of a single, monolithic season-long prize in favour of “Tiered Trophies” that could be earned in a single night. This kept the dopamine loop tight and the “time-to-value” low.

The navigation concept was equally critical. We had to solve the “Discovery” problem. With dozens of games happening simultaneously, how does a user find the “hot” game? We designed a modular navigation system that surfaced live scores directly within the tabs. The UI acted as a “Live Scoreboard” first and a “Game Entry Point” second. This ensured that even if a user wasn’t playing, the app provided enough utility to justify a daily open. We also concepted “Modular Cards” that could be injected into the feed—advertising, challenges, or live updates—ensuring the “Engagement Hub” felt like a living, breathing ecosystem rather than a static menu.

Crucially, the concept had to be “Poka-yoke” (fail-safe) for the NBA’s own content team. We were building a tool that non-technical operators would use to manage millions of users. The concept for the back-end “Experience Library” was to allow an NBA staffer to “drag and drop” a new Pick’Em challenge into existence in minutes. This operational efficiency was the hidden “commercial logic” of the project. By reducing the reliance on our own developers to launch new content, we increased the “gross margins” of the account and moved closer to the “configuration over customisation” ideal that defines successful SaaS scaling.

4. Execution

The execution phase was a masterclass in “Poka-yoke” leadership and technical orchestration. As the functional head of design and product, I had to ensure that our multidisciplinary squads—spanning design, engineering, and operations—were perfectly aligned. We were building on a “Super-Live” infrastructure designed to handle millions of concurrent users during peak broadcast windows. The execution didn’t just happen in Figma; it happened in the “engine room” of real-time data synchronisation. We had to ensure that when a player hit a three-pointer in Los Angeles, the Pick’Em “Live Score” widget in London updated within seconds, triggering the “Success” state for thousands of users simultaneously.

The build process focused on the creation of a “Modular Hub.” We executed this through a library of React-based “Cards” and “Carousels.” These weren’t just visual elements; they were data-aware components. A “Challenge Card” knew if the user was 80% of the way to a goal and would visually animate that progress upon entry. We prioritised the “Number Predictor” slider, ensuring the haptic feedback and “snap-to-number” logic felt premium. We also executed a complex “SSO” (Single Sign-On) integration with NBA ID. This was the commercial “north star.” The execution had to be frictionless; if a user had to “log in” again, we would lose 40% of the conversion. We engineered a background “Handshake” that validated the user’s identity without interrupting the play flow.

One of the major technical hurdles was “Modular Navigation.” We needed a UI that could scale from a quiet Tuesday with two games to a frantic Friday with fifteen. We executed a “Dynamic Tab” system that automatically prioritised “Live” games over “Upcoming” ones. We also built a “Fail-Safe” mode. If the real-time data feed from the arena flickered, the UI would gracefully degrade to a “Last Known State” rather than showing an error message. This level of “Poka-yoke” engineering ensured that the NBA brand was never compromised by technical volatility.

We also focused on the “Broadcast Integration” layer. We didn’t just build a web app; we built a “Tool” for the broadcast pundits. We created a simplified “Admin View” that allowed commentators to see real-time “Fan Sentiment” (e.g., “70% of fans think the Lakers will win this quarter”). This execution created a “Loop of Authority.” When a pundit on a live broadcast mentions the Pick’Em stats, it validates the user’s participation and drives a massive spike in “Instant Traffic.” Managing these “spikes” required an execution strategy focused on “Edge Computing” and aggressive caching of static assets to protect the database.

The final stage of execution was the “White Labeling” of the features back into FanKit. As each NBA feature was “signed off,” we performed a “Surgical Extraction.” We stripped away the NBA branding and “initialised” the feature as a generic, configurable module within the FanKit library. We documented the “Behavioural Logic” of the streak mechanics and the number sliders so that the next customer—whether it was Formula 1 or a major broadcaster—could deploy them with a single click. This was the “product-led” reality: we were using the NBA’s funding to build the world’s most sophisticated engagement toolkit.

5. Outcome

The outcome of the NBA Pick’Em reimagining was nothing short of a commercial and cultural phenomenon. Upon launch, the platform saw an immediate, sustained uplift in user activity. From my memory of the internal analytics, the “visitor count” rose by a staggering 60% in the first week. Crucially, this wasn’t a temporary spike driven by marketing spend; it was the start of a “compounding growth” curve. For three consecutive months, the platform saw week-on-week growth in active users. By the conclusion of the season, the product had achieved “sustained triple-digit growth” in total player numbers compared to the legacy version.

The most significant “commercial proof” was the impact on NBA ID registrations. We saw a “sustained double-digit increase” in account creations directly attributed to the Pick’Em funnel. While many fans already had accounts, the new gamification features—the avatars, the rewards, the Nike-sponsored “Sneaker Giveaways”—finally provided the “Value Proposition” necessary to convert the “anonymous fan” into a “known user.” This data capture is the lifeblood of the NBA’s modern business model, and our product became their most effective “Registration Engine.”

Culturally, the product transcended the app. It became a fixture of the “NBA Universe.” We saw YouTube pundits making dedicated “Pick’Em Strategy” videos and Twitch streamers playing the game live with their audiences. The “Number Predictor” slider became a common visual language for fans to debate player stats. During live broadcasts, celebrities and pundits would reference their “Pick’Em Streaks,” creating a “Social Proof” loop that drove millions of new players into the ecosystem. This cultural “stickiness” verified our “Intelligence” phase: fans don’t just want to watch; they want to compete.

For Monterosa, the outcome was transformative. The success of the NBA project “secured the contract extension” and paved the way for a multi-year partnership. More importantly, it “validated the SaaS pivot.” We had successfully built a high-performance, Tier-1 experience using the “FanKit” modular framework. The features we “extracted”—the number sliders, the streak logic, the modular navigation—became the foundation of our “Experience Library,” which we then successfully sold to 26 other enterprise clients, including FIFA and F1. We had moved from being an “Agency that codes” to a “Product company that configures.”

The “Return on Investment” (ROI) was clear. By reducing the “Engineering Overhead” for subsequent activations, we significantly improved our gross margins. The NBA Pick’Em project stands as the definitive chapter of my time as a product leader at Monterosa. It proved that “surgical UX interventions” and a “logic-led product architecture” can rescue a stagnant legacy asset and turn it into a global growth engine. We didn’t just “fix” a game; we “optimised” the commercial reality of fan engagement at the highest possible scale.