...

The Login page is the first page the trainer sees. We wanted a simple user interface that allowed both the athlete and trainers to login.

Trainer - Home page

Logging in as a trainer takes them to the Trainer Homepage.  The trainer's home page presents the trainer with athletes that he or she has been working with, giving them a snapshot of the health and injury status of the athletes they work with.  The user can view the profile page for an athlete by clicking on their thumbnail if it appears, or using the auto-completing search bar if it does not.  If the trainer wants to add a new athlete, clicking on the "add a new athlete" button brings up a form to enter a new athlete into the system.  The look and feel of this page has changed very little since the original paper prototype.  One important difference is the way new athletes are created; rather than having a "+" button next to the search bar, the button now explicitly states that it is for adding a new athlete.  This helped with usability for first time users, who did not understand what the plus button represented.

...

4. Add a note to his profile saying that he’s recovered from his injury.

Usability Problems

...

Trainer

...

1

The user trainer didn’t recognize a body area in the ‘create a workout’ tab and tried clicking ‘select a different body area’ label to search for it. This is not very severe. We should just make the label a search bar for body areas not being displayed.
In the add a new injury form you should be able to enter the date as the word instead of numerical. This is not very severe. We should just replace the input box with a dropdownThis is also a function of the fact that we did not have a complete set of exercises any every body part available.

The trainer was confused about how the alphanumeric translation of dates to numbers. It took much longer than needed for them to enter the date. Additionally, they suggested that she records injuries on the day they occur, so pre-populating the date as today would be a big efficiency improvement.

The drag and drop functionality in ‘create a workout’ wasn’t obvious at first. This problem was originally discovered in our first computer prototype. To mitigate the confusion, we added text in the workout chart that said 'Select a Body Part', and then 'Drag Exercises Here'. This made the drag and drop more apparent, but the trainer still clicked on an exercise twice before dragging it into the chart. The drag exercises here message should also be displayed on click and not just drag.

The trainer . We tried fixing this by adding a label saying ‘drag exercises here’ where a workout would go when the workout program is empty. In a real scenario the user would see this message before beginning to create a workout and there should not be a problem.This is not very severe.
He missed the significance of the colors in the note section.This is not very severe. Perhaps we could make selecting a color change the background of the input text box also to indicate the message will have that background. The trainer submitted a note without choosing a color

She
He felt like we should be able to edit multiple days of reps for a single exercise at once. This would be a minor change, and definitely a good suggestion.

He She also said it would be nice to have a way to contact the athlete when updates to his profile are performed. 

He thinks the dashboard player boxes should have more information such as the most recent note. He also suggested that a sort of news feed for recent injuries and notes could be nice to have on the dashboard also.

-Quick sort of trainer cards

Student 1:

Also, we could have minimized the time spent to find an athlete by having the cards on the trainer homepage change based on the text entered into the search bar. For example, if you start to search 'Ko..", then only athlete's names that have 'Ko' in their name cards visible. This feature would also provide visual feedback.

Trainer 2

When told the When told to update a player’s injury status, this user was confused by the ‘select a body area’ list in the ‘create a workout’ tab. This is somewhat severe. Perhaps the create a workout area should be grayed out when the player is healthy. This would take attention away for it and allow the user to look at all of the page and see the injury section.
This user from the sidebar. On the contrary, a trainer may still want to prescribe exercises to a healthy athlete, so we are caught between design flexibility and learnability.

This trainer understood the significance of and used the colors for athlete notes. When looking for Kobe Bryant it took this user a long time to find the athletes bar. Also when he found it he said that with the number of athletes a trainer is actively treating, showing them all in a dropdown is not very realistic. This is very severe. If we replaced the athletes dropdown with a search bar the user would be more likely to see it and know it needs to use it to find additional

athletes.
This user This trainer had no problem at all creating a workout.

Student 2:

The trainer suggested that there be a way to batch upload all of the athletes into the system. The trainer commented that they have the same athletes all year long, and it would be very time consuming to enter all the athletes by hand through the 'Create An Athlete' form. To solve this problem, we could potentially create a table layout where a trainer can upload multiple athletes at once.

The trainer mentioned the ankle sprained exercises are pretty similar so it would be helpful to have all the ankle exercises in the workout already. This is a great suggestion and would be implemented in the next iteration.

Student 1

The student effectively logged in to the athlete page

The athlete understood the athlete's workout chart, and injury history. The student was also confused about the colors for the athlete notes.

The athlete commented that the workouts would be on a mobile phone, so this desktop interface was not useful to athletes. In order to address this, we could add a mobile design for the athletes to view on their smartphones.

With paper, the athlete mentioned they can write down the number of sets and reps they were able to complete, which you can't currently do with Easy Trainer.  Our interface does not allow notes next to the exercises. We can add a way for athletes to check off exercises as they complete themNo problem creating athlete
“how do I find kobe bryant?” It took him a long time to find the athletes drop down. Again this is severe. The same suggestion applies from above.
He struggled to find how to add exercises (clicked around until he found the side bar). This is somewhat severe. Maybe we could make the workout locked in, and require the user to enable editing once a workout is set. Then the area would be in his field of view and more clear.
When trying to add an exercise he kept clicking the clean and jerk button (eventually figured out that he needed to drag and drop). The drag exercises here message should also be displayed on click and not just drag.
He had no problem changing sets/reps, or adding a note.
To add an injury, his first instinct to click injury history, but he found the actual button immediately after. No real problem here.

Reflection

There were two big things we took away from this course that we think we had all undervalued prior to the course; : prototyping, and user testing.  Most of us thought that going into this class we would learn more about what makes a good UI rather than the process of creating one.  Even when presented with these ideas, some of us thought the idea of creating a paper prototype wasn't worth the time.  It seemed nearly as easy to make the website in html and then later change whatever small things needed to be changed.  I don't think any of us realized that getting a good UI on the first try just isn't going to happen, and the paper prototypes definitely allowed us to see problems with our UI before we created it.  It was pretty surprising how some of the elements in our UI that we considered intuitive were anything but to the users we tested.  

We also learned about the design decisions you take for granted. When you are the designer, it is easy to assume that your users will have the same understanding of the system. You cannot simply pretend to be a new user. You must actually go out and have users play with your prototypes. It's amazing how a new user can identify a problem in seconds that our entire team missed all semester.