• Add to Collection
  • About

    About

    PART II LIVE-SCOREBOARD DESIGN
    Published:
Objective
Supplemental design from Full Scoreboard development. UX/UI condensing of data to smaller dimensions for left-navigation with mobile-adaptability in mind.
Overview
The content of the left-nav is fed by the same feeds as the Full scoreboard; Users can still receive event updates when not active on the main page of the selected corresponding sport event.
Some design iterations tested active selected states and whether behaviour as a primary navigation asset had distractions from being interactive; in conclusion this remained a read-only experience with the exception of opening the corresponding event on the main column.
Production release of Mini-scoreboard/Navigation menu
What users need
Alike the Full-scoreboard project, the pre-requisites of ideation was to balance the needs of the business with the goal objectives of the client/user. A firm reality was established based upon an MVP of the full-scoreboard. 
Whiteboard sketch of content wireframe and bookmarking functionality
All features wanted were ideated to be contained inside trays initially. Combination of features, content hierarchy and labelling; challenged proportions, legibility and positioning. The real-estate available pushed intuitive discoverability and the above whiteboard helped illustrate the complexity of the request and the cognitive overload of information for what is primarily a 'game event switcher' info-menu.
Truncated or shortened labels still had to be understandable; for the most part choosing acronyms was not as easy as a three character choice. Given that that such acronyms had meaningful combinations in real-world terms, to introduce a new set would confuse users.
Sketch to Balsamiq
Workshop your UI issues
There was a list of features that challenged legibility and that was merely due to too much content for very little space. Stepping through the scenarios we got a better understanding by minimum what a user would want if not monitoring the main event.
On one hand introducing hidden features requires some knowledge for users to know they are there to be discovered. Also with every UI comes a functional complexity that may eat away at performance which later adds on more resources to complete delivery.
Conclusion
Remaining true to being a menu first and scoreboard second, made less of a complicated CTA.
DISCLAIMER: Please note that this particular story is intentionally descriptive on the process while vague on the research artefacts and methodologies. While I feel the steps are typical of a solution delivery method, the aspects of its how are protected by NDA.