We used a design thinking approach to develop a feature for backroom staff at sports teams to rate their players as part of a review process.
As part of the project we decided to concentrate on Needs 3, 4 and 5. We have a calendaring tool, so point 1 was covered. Point 2 we felt we also covered in the graphing area, all metrics and goals, if input could be visualised per player in this area, so we had covered that need. Finally, sharing the report was also a point we had already covered in our messaging feature and our download to pdf feature. The alternative would have been to build a full end to end flow independent of the current software system, but that would have added a whole new area in the system, which is not a scalable approach, it also leads to confusion for the user, as multiple similar locations would have lead to cognitive load and possibly paralysis, if even only briefly.
Once the needs were identified we started moving into an ideation phase. A number of options were identified. Two concepts stood out, but neither was an obvious selection.
After running a set of usability tests, with a set script, we got clear signals that the Concept 2 - Focused was by far an ideal input mechanism and the historical aspect allowed for reference of previous ratings. What was interesting with regard Concept 1 - Grouped, was how useful this view could be at a general meeting when comparing players and reviewing averages for each player across a season or longer time frame. We decided to build the Focused concept and to later develop the table Grouped concept in the graphing area. A number of smaller interactions were also identified as needing to be updated.
1. Expand all function added
2. Add comment and staff member to a metric, remove talking points
3. Categorise metrics, sections added
4. Link back from reports section to the forms