PROJECT
I joined the SBG team as a freelancer, with goal of identifying opportunities to translate the data collated from telemetry devices, cameras and OB units situated at major sporting events.
The goal to put users back in control of the vast array of data available, help users make better decisions, predict future performance, and training gaps within the teams.
OBJECTIVE
Enable users to engage with the wealth of data compiled from multiple systems across each match. The data itself surfaced as an array of data points.
Pairs conforming to standard times code, with a text event descriptor. The data contained vital insights into events and performance but required a significant amount of specialist time to translate it into statistics which the teams use to inform training priorities.
Pairs conforming to standard times code, with a text event descriptor. The data contained vital insights into events and performance but required a significant amount of specialist time to translate it into statistics which the teams use to inform training priorities.
The application was made up of a video playback panel, pitch tracking component which presented the position activities of individual players, player stats and team stats which housed basic performance data compiled from raw data.
FUNCTIONAL REQUIREMENTS
Users need means to :
- filter the types of events showing
- play, stop, jump back 20 seconds, jump to next/previous marker
- set manual “in” and “out” markers to loop through a sequence of footage
- compress / expand timeline, to enable users to zoom in / out
Users should have means to print the timeline so that team / match performance can be reviewed both on and offline.
FUNCTIONAL REQUIREMENTS
Users need means to :
- filter the types of events showing
- play, stop, jump back 20 seconds, jump to next/previous marker
- set manual “in” and “out” markers to loop through a sequence of footage
- compress / expand timeline, to enable users to zoom in / out
Users should have means to print the timeline so that team / match performance can be reviewed both on and offline.
Events to be shown on match timeline
Events to show on the line are configurable by the user but would include as a matter of priority:
- Kick Off, Full Time, Half Time
- Incidents (Yellow Cards, Red Cards)
- Events (Goals, Substitutes)
- Performance metrics (shots on target, shots off target).
There may be other metrics we’d like to display which would have some sort of magnitude against time.
- Other (User specified) Incidents
e.g. a video clip capturing a pass which led to a goal). We’d drag this type of event on from another window.)
- Kick Off, Full Time, Half Time
- Incidents (Yellow Cards, Red Cards)
- Events (Goals, Substitutes)
- Performance metrics (shots on target, shots off target).
There may be other metrics we’d like to display which would have some sort of magnitude against time.
- Other (User specified) Incidents
e.g. a video clip capturing a pass which led to a goal). We’d drag this type of event on from another window.)
WORK
With the objectives defined by the team and limited access to users based on the sensitivity of the solution I had opportunity to reflect on statistical packages available on the market with a view to identifying the paradigms presently in existence.
Having a background in digital media, and post production I had a strong sense where the solution existed and set about working up concepts for how the information might be best integrated into the existing components in the screen.
INVOLVEMENT
- Freelance UX
- Enrich basic application
- Addition of more context
- Support Users unfamiliar with stats packages - negotiate context
- Freelance UX
- Enrich basic application
- Addition of more context
- Support Users unfamiliar with stats packages - negotiate context
FIGURE ONE
MATCH REVIEW SCREEN
- Data split across the breadth of screen
- Data can only present in XOR configuration
- Balance skewed towards numeric statistics
- Little space for video context
- Data split across the breadth of screen
- Data can only present in XOR configuration
- Balance skewed towards numeric statistics
- Little space for video context
FIGURE TWO
PROOF OF CONCEPT DELIVERED
PROOF OF CONCEPT DELIVERED
Having combined calls with the team discussing ideas which the team had previously explored, I delivered concepts for an enhanced timeline component.
FIGURE 2, 3, 4 show an overview of functionality, data presentation and the component itself.
FIGURE 2, 3, 4 show an overview of functionality, data presentation and the component itself.
FIGURE THREE
Context integrated in hierarchical configuration - to put user in control of level of detail presented alongside screen - dedicated to presenting sensible view of video footage (rather than "tiny panel"
Context integrated in hierarchical configuration - to put user in control of level of detail presented alongside screen - dedicated to presenting sensible view of video footage (rather than "tiny panel"
FIGURE FOUR
Player centric data entry, stats supporting user to:
- navigate huge array of context captured within matches
- without sacrificing huge swathes of onscreen real estate
- context presented in individual panels / panel combinations (XOR)
Player centric data entry, stats supporting user to:
- navigate huge array of context captured within matches
- without sacrificing huge swathes of onscreen real estate
- context presented in individual panels / panel combinations (XOR)