Shared Streaming
Allowing videos and live streams to be shared between two teams to give more users access to the most wanted feature.
Project Profile
-
Company GameChanger
-
Timeline Feb 2024- Jun 2024
-
Team Solo designer - 1 product manager - 4 engineers, 1 Engineer manager, 1 QA developer
-
Tools Figma, pen & paper, dovetail, Figjam
-
Process
Requirements, Research, Design, Develop -
Target users
All sports coaches, Team fans, and players' parents.
Problem Statement
Streaming games and accessing game videos and highlights post-game are invaluable features of the GameChanger app for both coaches and fans. However, some teams lack the resources or personnel to stream their games. This limitation prevents coaches from using video evidence to coach their players effectively and deprives fans, such as grandparents, of the opportunity to watch their loved ones play from home.
Solution Statement
Developing a feature that enables a team streaming a game to share the live video with the opposing team, while ensuring privacy and access control for both teams, would be beneficial.
Understanding the problem
Methods:
1) Design Brief: We kicked off the project with a design brief meeting, where we learned about our client's target users, brand, and goals.
2) Competitive Analysis: Collaborating with the project manager, we analyzed the existing competition to identify pain points, understand current live streaming capabilities, and pinpoint areas for improvement in video sharing.
3) User Interviews: I interviewed four coaches and three parents from various age groups to understand their pain points and determine if shared streaming would be beneficial to them, and if so, why.
Key Findings:
1) Lack of Resource: Coaches often struggle to find someone to livestream their team's games.
2) Audience Control: Coaches prefer to have complete control over who can access their game videos, whether they are streaming the games themselves or receiving videos from an opponent.
3) Lack of a centralized platform: There is no single platform where coaches can manage all their team's data, including scoring and game videos. Typically, coaches use one app for scoring, another for sharing videos, and rely on platforms like Facebook and YouTube for live streaming.
Ideation Solutions
Goals:
1) Allow one team’s stream to be applied to their opponent’s game
2) Allow the streaming team to opt in or out of sharing
3) Allow the receiving team to accept or decline a shared stream
4) Enable the receiving team to restrict the audience that can view the shared stream or video on their team page.
Sketching allowed us to explore different ideas & layouts
Diagram allows us to map and understand userflow
Low fidelity wireframes allowed us to curate our ideas & review them
Designing the Final Solution
Winning Ideas:
1) Including "Share with opponent" feature in the video setting set up to allow the streamer team to see the feature every time they want to go live.
2) Provide options for both public and limited access to videos, allowing the streamer and the receiving team to manage the audience.
3) Synchronize each team's scoring data with the video, highlighting their respective players.
4) Send a consent push notification to the receiving team, allowing them to accept or deny the shared stream or video on their team page.
Selecting what to share with opponent in video setting
.jpg)
-1.jpg)
Choose audience for shared stream before going live
Change audience for shared videos - post game
Btw, this is a feedback session I hosted with my team for these designs before I get feedback from users.
User Feedback
Think-Aloud
I conducted user testing sessions with five participants, guiding them through the designs and encouraging them to think aloud. This approach enabled us to evaluate our solution with real users who interact with our product daily.
Key-Findings
The Prototype I built to present my design to users for usertesting.
1) Overkill design: Users were comfortable sharing both live streams and videos without the need for separate settings. The essential features were the ability to select an audience and choose whether to share content.
2) Discovery: I learned that receiving teams want the option to accept or deny shared streams/videos, disproving our assumption that they would always be open to receiving shared content.
Design Iteration
Changes I made
1) Video setting redesign: I removed the "what to be shared" from the setting and instead added "Opponent audience".
2) New design: Designed and added a new flow for the receiving team to be able to "accept or deny shared stream/video".
New design for the receiver to accept or deny the shared stream/video
New video setting design
Results
What we built:
1) Video setting for the streaming team
2) Share with opponent feature for the streaming team
3) Consent push notification for the team that received the stream/video
4) Change the audience option during and post-game for the team that received the stream/video
Streamer team side:
Receiver team side:
Conclusion
Challenges
1) Post-game request: After launching this project and engaging with more users, we discovered that coaches have a strong need to request access to opponent videos once the game is over too. This is going to be the next step for us.
2) Nailing down the scope: New requirements came up throughout the design process, which often required us to rethink our original concepts.
Key-Takeaways
1) The importance of a process: Having a structured UX process as opposed to an organic process is key to challenging assumptions and practicing true user-centered design.
2) Cross-team collaboration: Sharing the UX spirit with product managers and developers is an awesome way to generate new ideas and help others understand the intentions behind design.