Knowing When to Pivot vs. Optimize: Reframing a Live-Betting Product Bet

Strategic reframing, mixed methods, and the judgment to deliver an unwelcome answer with a better one attached

Strategic reframing · Contextual inquiry · Behavioral triangulation · Executive influence

---

The situation

Leadership at a top-5 US sportsbook had committed engineering resources to a pre-packaged live same-game parlay product. The ask that reached research was a validation study: help make this feature succeed. Engagement with complex live products was low, and the feature was the bet to fix it.

I did not think the question was right. Users on the platform were already betting live and already building parlays. The interesting problem was why people who did both things separately consistently avoided combining them.

The reframe

Instead of “How do we make this feature successful?”, the study asked three things:

1. Why do users who actively engage in both behaviors avoid combining them?
2. What environmental and systemic barriers shape that avoidance?
3. How should the organization tell a pivot from an optimization problem?

That reframe changed the study from tactical feature validation into a question about product direction, which meant it had to be designed to survive a room that had already made a commitment.

Method

A conventional usability test would have validated the feature in isolation and missed the context that decided the outcome. I combined four approaches in a two-week window:

• Contextual inquiry during live games, observing real betting decisions as they happened.
• Competitor walkthroughs, having participants demonstrate the same workflow on rival platforms.
• Environmental mapping, documenting where and on what devices live betting actually occurred.
• Behavioral triangulation, comparing what participants said with their own betting history.

Before fielding, I pre-aligned decision criteria with product leadership: an adoption signal below an agreed threshold would trigger a strategy conversation rather than an optimization one. Agreeing on the bar before the data arrived is what let the findings land as evidence instead of opinion.

What we found

Learned helplessness, not a usability gap. Market suspensions during live play did more than delay bets. They taught users to stop trying. The theme “I don’t even bother at this point” surfaced unprompted in 8 of 12 sessions, and participants could not identify any pattern in when markets would lock. When a system is unpredictable, users stop attempting the behavior it depends on.

Context caps complexity. Only about half of live betting happened in a setting that could support a multi-step decision. Betting on the go was effectively limited to one or two legs; bar and social viewing prioritized the game over optimization. No interface change would have moved that constraint.

The hidden success story. The same users who had abandoned live same-game parlays were still building cross-game parlays live at healthy rates. “Cross-game is easy, same-game is impossible” was a consistent theme. That pointed to an immediate, low-cost optimization while the underlying infrastructure problem was addressed.

What happened

• The pre-packaged live product moved from a committed quarterly priority to an experimental track, and the engineering investment was redirected toward market stability and cross-game parlay improvements.
• The size of the realistic opportunity was reset to reflect where and how people actually bet live, which reshaped how the team sized future bets on complex live products.
• The multi-method, context-first approach became the organization’s model for validating high-investment features, and product managers were asked to read the findings before their next planning cycle.

What I’d tell another researcher

The most valuable research does not always validate a direction. The judgment call was not “is this feature usable” but “is this the right question,” and the craft was in designing a study that could answer the bigger question credibly inside a two-week window. Pre-aligning decision criteria, building the coalition with design partners before product and engineering, and arriving with an alternative path made it possible to deliver an unwelcome answer without burning the relationships that make research useful the next time.