EOS:
League Dashboard

Summary
After successfully researching and designing the athlete and coach dashboards, EOS returned to our team to ask for another dashboard to fit their business - a dashboard for the sporting leagues. This dashboard would be for league representatives to see how the athletes were performing with the EOS program.
Timeline
1 week of designing and testing.
Role on the Team
Main contact point between the EOS stakeholders and small team, usability tester, and wireframe/prototype creator.
Technology
- Desktop website, matching the look and feel of the coach & athlete dashboard
- Wireframes built using Sketch, prototyped in InVision
Research Limitation
Due to how new EOS's program is to the leagues, the league representatives had ideas for metrics they wanted to view within the platform, however were unsure if these metrics would remain the same, or if they would change as they better understood the program as athletes went through it. We also learned from our stakeholders that one, maybe two people within the leagues at any given point would be using this dashboard. We also knew that the timeline for this project was very short and it was better to have a design as soon as possible for the league clients.
Therefore, I was not able to conduct new research at this time with league representatives. Our designs were based off of existing research, which had been done the month prior by myself and my team. However, as the program progresses there will likely be future opportunities for research to better understand and iterate on the design created.
Designing the Dashboard
From our understanding of the business, previously conducted research, and previously constructed prototypes, we knew we had to include the following things for the league dashboard:
1. Athlete Listing
2. Athlete Detail Pages
3. Assignment Overview
4. Overview Metrics
Therefore, based on these criteria we decided to start with what we had created for the coach dashboard, and remove capabilities around editing and adding assignments or notes. This way, the leagues could view all the information they needed but would not have to see everything in as great of depth as the coaches.
The page that had the most significant changes was the home page, as we needed to ensure it had a clear overview for the league representatives. We wanted to ensure that when you looked at it, you knew exactly what information you were getting.
Usability Testing
Creating a usability testing guide for the league dashboard was tricky, as the main objective is clarity and viewing metrics. Therefore, I focused the usability test on ensuring that the copy was clear, and that users could navigate the league dashboard as well as they could the coach and athlete dashboard previously designed.
After one round of usability testing with 4 users, we found that all users were able to clearly understand the copy and follow along with the design's look and feel, navigating through pages. Similar to the responses we heard from the previous project, users found the prototype clean and straightforward.
Final Design
Next Steps
In my opinion, there is one main step that needs to be taken to ensure that this dashboard is perfect for the leagues: which is to do further research by putting this dashboard in front of league representatives for usability testing. I believe that if they see and use the dashboard, they can better understand what it does, what it can do, and what they want out of it. With this information, we could alter the design to fit their needs.
I also believe user interviews with league representatives will also help, by giving us a sense of what metrics or information is most important to them as they consider the EOS program in the long term to work with their athletes.







