Documenting and sharing daily injury records within the Athlete RMS NHL platform with an upgrade report system.

Athlete RMS is the world’s first league-wide records management system that collects, analyses and visualizes athletes’ data. ARMS Health is NHL’s internal medical software that serves medical data and tracks performance.

Athlete RMS is the world’s first league-wide records management system that collects, analyses and visualizes athletes’ data. ARMS Health is NHL’s internal medical software that serves medical data and tracks performance.

2023

Sector:

Sector:

Enterprise, Healthcare B2B SaaS

Enterprise, Healthcare B2B SaaS

Team:

Team:

Director of Development, Product Manager, QA Engineer, 2 Developers

Director of Development, Product Manager, QA Engineer, 2 Developers

Client:

Client:

NHL, National Hockey League

NHL, National Hockey League

My Role:

My Role:

Product Designer

Product Designer

Timeline:

Timeline:

3 months

3 months

User Groups:

User Groups:

Internal Medical Staff, Coaches, Team Operations

Internal Medical Staff, Coaches, Team Operations

Impact:

23%

Adoption Rate

Adoption Rate

+57%

Customer Satisfaction Rate

Customer Satisfaction Rate

This is the final prototype!

This is the final prototype!

and see how this new feature increased the NHL's user satisfaction rate!

and see how this new feature increased the NHL's user satisfaction rate!

Research: Mapping behaviour patterns and future needs.

Research: Mapping behaviour patterns and future needs.

Our research strategy focused on two key areas: analyzing users’ existing behavior patterns with the legacy feature, and conducting needs analysis for new goals and functions. By combining insights from both, we created a transition design that aligned with users’ mental models while introducing a more efficient flow.

Our research strategy focused on two key areas: analyzing users’ existing behavior patterns with the legacy feature, and conducting needs analysis for new goals and functions. By combining insights from both, we created a transition design that aligned with users’ mental models while introducing a more efficient flow.

Legacy feature

Question Areas.

Question Areas.

Functionality

Functionality

Purpose: What do users need reports for?

Usage: How are reports used in daily workflows?

Audience: Who are the reports shared with or sent to?

Flexibility: How much do users need to modify or customize reports?

Diversity

Diversity

User Identification: Who are the users?

Workflows: What does day-to-day work look like for different user groups?

Needs Variation: How do the needs differ across user groups?

Learning from Legacy

Learning from Legacy

Usage Patterns: How is the legacy system used by current users?

Frequency: How often is it used?

Friction Points: Where do users experience challenges or frustration?

Mental Models: What familiar patterns or expectations have users developed?

Research Methods.

Research Methods.

Internal Product Survey

Internal Product Survey

We integrated surveys into the existing user flow to learn about users’ main functional needs around reporting. This method helped us collect broad feedback at scale, with over 65 participants contributing valuable insights.

Focus Groups

Focus Groups

To capture usability insights across different user groups, we conducted three focused sessions with Coaches, Medical Staff, and Team Operations staff. Focus groups allowed us to explore different workflows and uncover how needs varied across roles.

User Interviews and Unmoderated Usability Testing

User Interviews and Unmoderated Usability Testing

We ran unmoderated usability tests on the outdated legacy reports flow, combined with targeted user interviews. This helped us understand users’ thought processes, priorities, friction points, and goals when creating and sharing reports.

Insights that drove the solution.

Insights that drove the solution.

Reporting Flexibility

Player Data Management

Need for dashboard-style report layouts

Need for dashboard-style report layouts

Ability to modify data directly within tables

Ability to modify data directly within tables

Need for flexible filtering and sorting tools

Need for flexible filtering and sorting tools

Quick actions to update player status

Quick actions to update player status

Option to hide players selectively in reports

Option to hide players selectively in reports

Add comments tied to individual players

Add comments tied to individual players

User Flow: bridging familiar habits with new flexibility.

User Flow: bridging familiar habits with new flexibility.

Informed by our research, we restructured the user flow to make reporting faster, clearer, and more adaptable. Users can easily move through key actions — selecting players, editing details, updating statuses, and adding comments — while anchoring in familiar patterns.

The result is a modular, low-friction experience that supports both legacy habits and new, more efficient workflows.

Informed by our research, we restructured the user flow to make reporting faster, clearer, and more adaptable. Users can easily move through key actions — selecting players, editing details, updating statuses, and adding comments — while anchoring in familiar patterns.

The result is a modular, low-friction experience that supports both legacy habits and new, more efficient workflows.

Solution #1: Editable table format.

Solution #1: Editable table format.

We introduced an editable table format, allowing users to update report data directly without switching views. Changes are saved seamlessly to the database, making updates faster and keeping users focused.

We introduced an editable table format, allowing users to update report data directly without switching views. Changes are saved seamlessly to the database, making updates faster and keeping users focused.

Solution #2: Filtration System.

Solution #2: Filtration System.

A new filtration system enables users to quickly sort and focus on key report data, like player availability or injury status. It keeps the experience fast, flexible, and scalable as data volume grows.

A new filtration system enables users to quickly sort and focus on key report data, like player availability or injury status. It keeps the experience fast, flexible, and scalable as data volume grows.

Solution #3: Player Visibility Controls.

Solution #3: Player Visibility Controls.

We improved player management by making status always visible during report creation and allowing users to hide irrelevant players without deleting records. This helped users create cleaner, more focused reports faster.

We improved player management by making status always visible during report creation and allowing users to hide irrelevant players without deleting records. This helped users create cleaner, more focused reports faster.

Solution #5: Report Templates.

Solution #5: Report Templates.

Users can create custom report templates to adjust the structure, manage data in bulk, and set recipients. Templates save each setup for future use, making report creation faster, more consistent, and less error-prone.

Users can create custom report templates to adjust the structure, manage data in bulk, and set recipients. Templates save each setup for future use, making report creation faster, more consistent, and less error-prone.

Execution: Cross-functional partnership.

Execution: Cross-functional partnership.

We partnered closely with the development team through weekly feasibility meetings, reviewing every design iteration to catch technical constraints early. This helped avoid rework and saved valuable development hours.
In parallel, we collaborated with leadership to craft an adoption strategy and post-launch plan, ensuring a smooth rollout and strong internal alignment.

We partnered closely with the development team through weekly feasibility meetings, reviewing every design iteration to catch technical constraints early. This helped avoid rework and saved valuable development hours.
In parallel, we collaborated with leadership to craft an adoption strategy and post-launch plan, ensuring a smooth rollout and strong internal alignment.

Impact: Driving feature adoption and satisfaction.

Impact: Driving feature adoption and satisfaction.

To support adoption, we created targeted communications: email announcements, online workshops, and in-product pop-ups to guide users through the new experience.

To support adoption, we created targeted communications: email announcements, online workshops, and in-product pop-ups to guide users through the new experience.

23%

Adoption Rate

Adoption Rate

A month after launch, the feature reached a 23% adoption rate — a strong result given the smaller target user group. Additionally, 7 out of 10 activated users engaged with the feature within two weeks, marking a successful Time to Adopt outcome.

A month after launch, the feature reached a 23% adoption rate — a strong result given the smaller target user group. Additionally, 7 out of 10 activated users engaged with the feature within two weeks, marking a successful Time to Adopt outcome.

+57%

Customer Satisfaction Rate

Customer Satisfaction Rate

CES (Customer Effort Score) surveys improved significantly after launch. The legacy feature averaged a 7/10 effort score (higher = more effort needed); post-launch, users reported a 3/10 average. This reflects a 57% increase in satisfaction, validating the usability improvements.

CES (Customer Effort Score) surveys improved significantly after launch. The legacy feature averaged a 7/10 effort score (higher = more effort needed); post-launch, users reported a 3/10 average. This reflects a 57% increase in satisfaction, validating the usability improvements.

Drop Me a line at:

Visit my page:

Drop Me a line at:

Visit my page:

Drop Me a line at:

Visit my page:

Drop Me a line at:

Visit my page: