I play Ultimate, so I knew how easily stats could be missed from the sideline. Keeping a record competes with watching the game. I wanted to understand what a phone-based tool would need to do for the person responsible for tracking each play.

I surveyed 24 players and coaches and reviewed more than nine secondary sources. Respondents preferred one-tap entry to presets or manual typing. I used that finding to put quick stat entry at the top of the requirements and set a design target of one or two taps per play.

I gave deeper post-game analytics and detailed player profiles lower priority. Those features could add value later, but the first version needed to work for one person keeping stats on the sideline.

I ranked the requirements and mapped onboarding, live stat entry, and team management before building the high-fidelity prototype. I populated it with scores and rosters from real games, including Florida Warm Up 2025, to work through the flows with realistic data.

Using existing game data helped me check how the screens fit together. It did not tell me whether someone could keep up during a live match; that needed a separate test.

The result was a high-fidelity prototype shaped by player and coach research. These figures describe the research and design target:

Next, I would put the prototype in a scorekeeper’s hands during a tournament. I would track missed plays and how often they had to stop following the game to enter data. That would test whether the quick-entry design works under live conditions.