Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

...

  1. Put his team into the Forward Strides system
  2. Enter a workout and assign members to workout
  3. Take times during workout on this device
  4. Disply results in a nice visual representation

Design Sketches

...

Stephen Zhang

Design 1:

Goal: Designed with a focus on workouts

...

The final screenshot is the graphical trends interface. First idea is that the user can pick which athletes to include (multiple is allowed), what distance, and what x axis to run it along. When one of each field is selected, the graph will update, and clicking on the graph brings it to full screen. This is cluttered and needs to be refined as to how to get the best looking graph. maybe make the graphical trends interface multiple screens, selecting first event, then members, then axis. This allows you to filter down the available athletes to the pertinent event.

...

Design 3:

Goal: Tablet usage

Design: Focus on efficiency and ease of use during workouts

...

This can be considered a central page which allows coaches quick access to each athlete and group, as well as a link to begin recording times.

Training Page:

This is the primary page that coaches will use to record times and assign them to athletes in a group.

 

Workout Page:

This page shows the current workouts for each group, and allows coaches to make last minute changes to these workouts.

Athletes Page:
This is a page with the functionality to allow Coaches to see which athletes are members of which groups, and to change those associations if necessary.

Design 2 Tablet Interface:

This is the primary page which shows a quick overview of the weeks workouts.

This page is the workouts page, allowing the user to sort by groups as well as by date for easier editing of workouts.

...

This page allows an all in one input for all the workout groups.  For the ease of the user, the user can prefer to enter all of the results by group, or all of the results by date.

Image Modified

This page is the performance page that lets coaches and scouts see trends in their athletes performance.
Image Modified
Design 3 Computer Interface:

...

The main page here has a global search at the top, a menu pane to the left, and recently viewed and favorites list of charts and diagnostics.

This page is for coaches and scouts to search for workouts based on groups and/or athletes, and then compare the selections in the bottom two panes.

...

Learnability

The learnability for this model is high. Each menu button is labeled with an icon pertaining to what each button does. In addition, the timer feature mimics a stopwatch's start, stop, lap feature. However the coach is now able to assign times to each athlete immediately instead of writing down times and assigning them later. And finally, the graphic trend screen is tailored to guide the user through the process, ensuring that the user is focused on the task and understands whats going on.

Efficiency

The efficiency of the system is pretty high. There is a lot of tactile feedback from drag and drop, and is easily understandable. The only inefficiency comes from the performance page as there are many options and no quick way of selecting what you want. However, maybe adding voice functionality to filter out names may be useful (saying M brings up all the athletes who start with the letter M).

Safety

The system is rather safe. There is a dialog box that appears if you tap the graph to make sure when you're showing the team their performance it doesn't accidentally disappear. It is however difficult to edit times. This can be done from the workouts page as opposed to the timer page, as the timer page is focused on collecting times quickly. As such, it may be harder to navigate to focus on the more prioritized event such as taking times and checking performance trends over a period of time.

Storyboard 3

...

This last design was designed with a tablet interface in mind. Here Coach Martin would first enter in his users, and then drag and drop them into groups that he makes. Then he would head to the workout's page where he can create a workout for his athletes. Afterwards, he goes to the timer page, where he can enter in times for each athlete. This screen would probably be better now after studio if it started a large timer and each time a runner runs by he taps their picture or name to take a time down. Finally he can use a interface much like design 1 and 2 to filter by event, then group, then axes and create a graph to display the trends the coach wants to see.

Learnability

This design is very learn-able due to the large buttons directing the users view, the tactile feedback the user receives from drag and drop, and by limiting the number of conflicting interests on screen, is able to direct the user to the tasks they want to perform.

Efficiency

This form is highly efficient, though keyboard interactivity is not available for power users. The difficulty of this program is getting the initial setup. After that, it is increasingly easier for the coach as there is usually very little group and member maintenance. Mostly just making workouts and taking times, which are straightforward and easy tasks.

Safety

There is very little error correction as this program is made to be very quick. There are no dialogue boxes to confirm or check if information is right, and its up to the coach to find and fix errors.