← Selected work

Player trust · 2026

More context before joining a match.

Playtomic

Leading the Player Statistics refresh to help players assess Open Matches beyond a level number, with 63.7% daily adoption among Open Match explorers.

Player trustJV / 007
Playtomic

The context

Joining an Open Match means deciding to play with people you may not know. Players needed more context to assess a potential match than a level number alone.

I led a refresh of Player Statistics to bring match history, play style and feedback from other players into that decision. The goal was to help players set expectations and give them useful context before joining.

My contribution

  • Led the feature refresh. Took the existing Player Statistics experience forward around a concrete decision: whether to join a match with unfamiliar players.
  • Connected delivery to product goals. Worked with the team on adoption and perceived-value measures, alongside guardrails for Open Match participation, matches per player and player-review ratings.
  • Followed real usage after launch. Reviewed repeat use, profile exploration and the path back to the match list, where players typically continued their joining journey.
  • Adapted the service to demand. The statistics service saw roughly ten times its previous request volume; I increased its memory allocation to support the additional load.

The outcome

Daily adoption reached 63.7% of Open Match explorers, more than double the 30% target. Among users who viewed statistics, usage averaged about 5.5 views per day. Return rates were 78% in week one and 68% in week seven, showing that the feature became part of a recurring workflow.

Engagement beyond the first visit

Match-search-to-payment conversion moved from 28.0% to 28.6%, an increase of 0.6 percentage points. Match exploration clicks rose from 48.0% to 49.2%, and Open Match participation was 12.2% against an 11.4% baseline. These were observed comparisons without an A/B test, rather than gains attributable solely to the feature.

From a player need to a widely used feature

This project brought together product judgment, cross-functional delivery and service operations. I led the refresh around a specific player decision, followed its adoption after launch and adapted the backend to roughly ten times its previous request volume. The result was a statistics experience that players returned to regularly, supported by the engineering work needed to serve that demand.