Elites Optimization Services is a program that helps elite athletes transition into their professional careers using career coaches and mentors. Communication between career coaches, mentors, and athletes was primarily done by email, text messaging, and phone and video calls. This method was very challenging for the coaches and athletes as it was difficult to manage communication, turned in assignments, and scheduled appointments. The athletes experienced the same struggles, and it felt less like a program. 


My team and I were tasked to design an online dashboard for EOS where coaches could review documentation & share them with the correct parties; and for athletes to have one place to turn in assignments, review old assignments, and schedule their sessions.

Phase 1: Research

Competitive/Comparative Analysis:

We researched four different platforms related to sports and eduction. I compared their features and methods, and the listen key takeaways.

Key takeaways:

  • Dashboard to track athlete progress

  • Tracks exercises and tasks

  • Star rating feedback

  • Side tab bar made it easy to communicate

  • Specific lesson ideas: Quick workshops

User Interviews:

People we interviewed:

  • 3 Stakeholders

  • 5 Athletes

  • 2 Mentors

  • 3 Career Coaches

Questions for athletes:

  • Onboarding

  • Scheduling

  • Mentor/Coach relationships

  • Tasks, motivations, outcomes, etc

Questions for career coaches and mentors:

  • Background

  • Managing athletes

  • Scheduling pain points

  • Assignment management

  • Wishlists & improvements

Elites Optimization Services

Timeline: 2.5 weeks

My Role: UX Designer, Researcher, Visual Designer

A dashboard for career coaches and athletes looking to establish careers after their athletic careers. 

Tools: Sketch, InVision, Omnigraffle

Methods: User Interviews, Affinity Mapping, Personas, User Journey, Mid/Hi Fi Wireframes, User Flows, Site Map


Phase 2: Synthesis

We synthesized our data by creating an affinity map. From here, we organized our key findings by listing key quotes and creating two personas: one for the athlete, and one for the coach.

The quotes we gathered allowed us to list the needs and frustrations for our personas. 

Career Coach Pain Points:


5 users

“The onus of scheduling was always on the athlete … who have really busy schedules already.”


6 users

“Athletes need to get invested in the program in order to hold themselves accountable.”

Assignment Management

5 users

“I would go looking for an assignment … and it was gone in my inbox.”

Taking Notes

2 users

“I want to be able to easily see the notes on the last session… not just mine”

Athlete Behaviors:

Athletes Take Notes

4 users

“I would use Google, and open up the document to everyone to see what I was typing during the session”

Scheduling ASAP

5 users

“I’d always try to schedule my next session right at the end of that session.”

Scheduling ASAP

5 users

“Getting those reminders that ‘hey, you need to schedule a session’ … was helpful”


With our synthesized data, we created two user personas. We created Alex to represent the athletes, and Jamie to represent the career coaches. 

MoSCoW Graph:


Phase 3: Design

We started with low fidelity wireframes of 2 dashboards: one for the career coaches and one for the athletes. We then converted our wireframes into hi-fi wireframes, and turned them into a prototype, and performed 3 usability tests. 

Assignments Page:

For the Assignments page in the career coach prototype, we wanted the career coach to be able to view all of his students' assignments. We gave the option to sort by name, and filter by assignments that are overdue, ready for review, pending, and reviewed. 

Iteration 1:



  1. Users felt slight awkwardness selecting tabs to filter assignments by reviewed, overdue, etc.

  2. Some users had difficulty figuring out how to select an assignment. 

Iteration 2:



  1. Some users spent a few seconds interpreting what each tab meant.

  2. Some users still had difficulty figuring out how to select an assignment. 

Iteration 3:



  1. We changed the text of the tabs to clarify what each one means.

  2. Created clear, colored buttons for each assignment under "status"

Main Page:

For the Main Page on the career coach's side, we wanted his to see all immediate important information, and then be able to navigate to a more in depth version of whichever information he was looking for.  

Iteration 1:


  1. Users felt awkward reading This Week panel.

Iteration 2:


  1. Some users felt confused about which assignments to look for under the Assignments panel.

Iteration 3:



  1. We made sure This Week was more clearly laid out and have no unnecessary panels.

  2. We clarified the Assignments panel.


Phase 4: Delivery

Our final deliveries to the stakeholders included user flows, a sitemap, and annotated wireframes. 

Next Steps:

  • Athlete Action Plan

  • Athlete Notification Possibilities

  • Build a dashboard for leagues to view how their athletes are doing

  • Find what would be the best ways for EOS athletes to connect with one another

  • Increase research into athletes to learn their pain points.