Based on the competitive analysis it would be beneficial for MSS to solve a user need not satisfied by other platforms and to have features that are not affected by the size of audience pool. We went back to the user research to look for an unsolved problem space and we noticed that currently mid-level use different platforms to find event information.


At this point out team felt we had enough research and insights to converge towards the problem statement. We began this process by building our user persona Paul James. Paul James is a mid-level athlete working hard to move forward in his sports career. However he is not getting noticed my scouts and has to work hard to promote himself and find tryout applications.

Paul’s Journey

Paul goes to an event to gain exposure. However the scout doesn’t notice him. He decides to upload the photos his friend took but he doesn’t know how to edit them. He finally managed to edit and upload his video. For some reason no one seems to be watching it. Paul tries uploading it on multiple media platforms. He gets exhausted trying to do that and misses the next showcase. Now he’s very frustrated.

Problem Statement

Mid level athletes without strong networks have a hard time getting attention from scouts. In order to get better exposure towards recruiting teams, athletes need to use a large number of platforms for promoting themselves and with potential tryouts.

How might we help athletes to easily connect with open recruitment opportunities?

Ideate — Design Studio

To brainstorm ideas our team decided to conduct a design studio. We prioritized these features and determined the must haves and should haves.

The must haves were:

Onboarding process

  • Clear description on landing page (based on usability testing)
  • Emphasizing a few features (based on market research)

Athlete profile

  • Basic information (based on user interviews)
  • Profile photo
  • Performance video (based on user interviews)
  • Stats (based on user interviews)


  • Event ads list (based on user interviews)

The should haves were:

Athlete profiles

  • connection to social media accounts (based on coach interview)

Find events

  • Event ads of the player’s sports (based on coach interview)
  • favorite event
  • Search event

The must haves required low effort and are necessary. For example, during usability testing, users felt there were too many features so it made sense to focus on a few features. All users mentioned stats during the interviews which implies the importance of showing stats in the profile

The should haves require high effort but are necessary. For example, users mentioned have social media on different platforms and it would be convenient for all of them to be combined on one. However this might require higher effort coding work. Favoriting an event also made sense for the athlete since there might be a select few that peak their interest. However this would require building out a separate system architecture for the favorites.

Source link


Please enter your comment!
Please enter your name here