GR1 - Project Proposal and Analysis

  • Observations & Interviews. Give a narrative of the three people that you observed and interviewed. Don't use their names. Don't identify the users by name, but do describe who they were. Each narrative should include a particularly interesting moment -- a breakdown or workaround that exhibits a feature of the problem you're aiming to solve.
  • User Classes. Describe the user classes that you have identified, and their major characteristics.
  • Needs & Goals. Describe the goals that you have identified, with reference to the observations you made.

Problem Statement

It is difficult to effectively and efficiently analyze and observe athletes' performance progress over the course of a season or career. It is also difficult to pinpoint what factors lead to good or poor performances in the data.

Stated Needs during Interviews

  • Collegiate Head Coach
    • "Design workouts depending on performances"
    • "Easily pull up records"
  • Collegiate Assistant Coach
    • "See how individual athletes respond to different training methods"
    • "Easily record workout splits"
  • Collegiate Recruiting Coordinator
    • "See trends of prospects' performances toward end of high school career"
    • "Compare multiple prospects performances"

User Classes

  • Coaches
    • High School, College and Professional Trainers
    • Specialized Coaches for distance events, field events, and sprinting events
    • Fitness Trainers
    • Spends the most time with the athletes
    • Has access to workouts, and up to date on injuries
    • Is able to currently see vague overall trends due to changes in personal best times
  • Scouts
    • College recruiters looking at high school prospects
    • Only has official data to observe from competitions or from visiting and watching practice
    • Often needs to compare multiple athletes when deciding which to recruit
    • An outsider looking into a situation often lacks the overall trend of an athlete

Needs & Goals

  • Coaches
    • Users can track athletes' progress / history
    • Users can view performance of athletes with certain features
    • Users can record workout information quickly and efficiently
    • Users can easily see overall performance trends
  • Scouts
    • Users can track athletes' progress / history
    • Users can view performance of athletes with certain features
    • Users can easily compare prospects
    • Users can understand significant trends and process patterns in potential recruits
  • No labels

1 Comment

  1. Problem Statement: You make no mention of who has these problems, and it the problem statement itself seems to be geared towards the coaches.

    User Analysis: Everything else on your wiki seems to indicate that you're looking for a general solution for all sports coaches, but then you break down into specialized coaches for distance/field/sprinting as if you were designing for track. Given some of your group member's close affiliation with track, you should steer away from creating an interface specifically for track coaches.

    Interviews/Observation: From your summaries on your Wiki, it's not obvious that you did interviews. You merely identified your interviewees by their job title and neglected to identify their school or their sport (both could have significant impact on their answers).

    Wiki Presentation: It was difficult to really see the difference between coaches and scouts at first glance, especially because their first couple goals are the same. It would have been nice to see a "common goals" section rather than a simple copy/paste.

    Overall: Please remember to fill out the self assessments. Not one of you submitted a self assessment, and using the self assessment as a guideline for checking the quality of your submission really would have helped you a lot.