Foxsports Single Sports App - Live Streaming 

Screen Shot 2018-06-15 at 11.45.25 pm.png
 

It all started when…

The project began through some conversations with the executive team, who had reviewed customer feedback that pointed to a hole in the live streaming market. 

The stakeholders brief was simple, take the exciting platform of Single Sports App and add live streaming to it. 

From the moment I walked into Fox Sports my focus was to work with the stakeholders to help them throught the journy of understand what User Experience was about. This project was no different to the others in that it had come from the top down, and the timelines on the project were short. 

Project Overview

Add live streaming to the 'Fox League' and 'Fox Footy' Single Sports Apps. Live streaming was not to be the focus of the app but it was a surprise and delight feature for existing users of the app who had a Foxtel subscription. This portion of the apps user base is about 5%. 

The secondary goal of the project was to drive traffic through the subscription journey to purchase a Foxtel subscription. As mentioned before the new experience was not meant to be the primary focus of the app, but it was there to aid the live scores experience with a live stream of the match being played. 

Research: Current state analysis

As in most of my project my starting point is always to analyse the existing product. The goal of a current state analysis is to build a picture of the framework of the existing environment of the app. This will become the backbone of the project as it moves through every stage of development. 

The starting point of the analysis was to start documenting the information architecture of the app.

information architecture

The app has a unique experience to enter the app, users are required to funnel through an onboarding followed by 'Story Cards'. Story Cars was the first point that I established would be effected by this new live streaming. 

The purpose of the 'Story Card' is to reveal to users the newest breaking information that the app has been updated with. Its also used as a navigation tool as it provides users a way to find articles that they might not have seen otherwise. From a editorial perspective its a powerful tool giving them more freedom with what they want users to read. 

As you can see above each key page that has a red dot was in some way going to be affected. 

User Journeys

Once I had documented the app sitemap and had an understanding of what pages were possibly going to be effected by live streaming, I started to build out key user journeys that met the requirements of the user stories. 

This helps to build out a complete picture of the existing app and provides the platform, in a perfect world, for testing with users to understand any key usability issues that are present on the app. 

Stakeholder Sketching Session

After I built a deeper understanding of the current state of the app I started to get the stakeholders across the work I had done so far. Specifically in the early stages of the project its important  to bring stakeholders along the journey so that they feel like they are contributing to the project. 

In this way, I ran two sessions that were both aimed at learning about how stakeholders saw the future of the project. The first of those sessions was a stakeholder walkthrough of the current state analysis. 

This session went for 1 hour and included the following people, Head of digital, Head of Product, Product Owner of Single Sports app, Analytics representative, Development representative and a BA. 

The key outcomes from the session; 
 - Run through user stories individually with the group
 - Ask stakeholders to elaborate of provide more detail on areas of confusion in the group
 - and finally talk through the key user journeys

The second of the two sessions was a sketching session, this session ran for 2 hours over two days. In the first session we focused on building a feature list based on the user requirements that were provided. This list was the prioritised and we started to categorising those features into sections of the app that related to my sitemap that I created earlier. 

This then lead into the second half of the session which I gave each person in the room 4 minutes to take a piece of paper, divided into 6 and sketch out as many different ways of representing each feature one by one. 

The output of that session looked something like the following; 

 Stakeholder sketches were redrawn 

Stakeholder sketches were redrawn 

After both sessions were completed, the wireframes that the team had created were then synthesised and I analysis the best ideas that were the most feasible. 

Sketches were then aligned to the journeys that were created earlier, and then reproduced in sketch to a higher level of fidelity. 

Stakeholder Walkthrough

Once all the sketches were recreated in sketch and all the user requirements had been met with a design. I organised a stakeholder walkthrough with the whole team. 

At this point I began to involve the UI designers who were both busy working on other projects, this was the first opportunity I had to revel to them what they would need to be working on. 

During this walkthrough I give stakeholders a chance to get up close and personal with the designs and were each given some red dots for them to annotate any questions. 

prototyping

Prototyping as Usability Testing

At this point, the most important thing for me to do was to validate that the designs I had been working on were on the right track with what users were looking for. My aim was not to validate the need for live stream, but to validate that users were able to complete key tasks, like, find live streaming, engage with the TV guide etc. 

I built out a high fidelity wireframe prototype in sketch and begun writing out a user moderation guide. 

Unfortunately at this point the user testing budget fell through and I was required to test the designs with internal staff members. This form of testing is not specifically any less valuable then testing with users, although it does limit the insights that I could have obtained from a full user testing session. 

Based on user testing with 8 internal staff members, the prototype was completely functional and users found what they were looking for with no issues. 

Conclusion

Unfortunately at this point the project was depriorities and my focused was moved onto another project.