NWTN aims to reduce the occurrence of multiple head injuries in athletes by way of sensors paired with their coaches phones. My team and I were asked to develop a mid-fidelity prototype of the app interface. We conducted multiple user interviews with coaches and athletic trainers and built a set of 60 screens in our final prototype based around our findings from extensive research and testing. We ensured our design solutions were desired by users by doing many rounds of usability testing.




Kelsey Fiegle

Natalie Leroy


Three weeks


NWTN is an impact detection sensor intended for use by non-professional athletes. A NWTN sensor is clipped to an athlete’s helmet or headband. When impact is detected, a notification is sent to the coach or trainer who has paired the sensor with their phone via bluetooth. The data surrounding the impact would be recorded for the coach to review along with the option to conduct a S.C.A.T. (sport concussion assessment tool) assessment using the pocket S.C.A.T. tool included in the app.

Neil and Aaron, founders of NWTN, talking about the making of the NWTN sensor on the Conan O'Brien Show

NWTN has been through two rounds of UX research and design with other teams in the past so we started by gaining an understanding of the current state of NWTN. We were provided with a set of deliverables that were produced by the previous UX teams. Some of what was included was a set of personas, interview transcripts and 28 annotated wireframe screens. The majority of the work had been discarded because of a business decision to focus on soccer players instead of on football players. The remainder of the UX and UI work was shared with us in 4 UI screens.

Example of original "LiveMode" concept. This would be what a coach would see on their phone while in game/practice.
Pocket SCAT concept that inspired our research and testing of the SCAT tool.
Wireframe of original Player Profile. Deciding what the most important information to be included in this screen was a very major focus in our testing.

These screens contained components that shaped the mid-fi UX wireframes and user flows we completed in Sprint 2.

After learning what the previous teams had focused on and created, we took note of what pieces NWTN adopted. At that point, the NWTN app consisted of a team roster, individual impact overview and a visual representation of impact by graph or 3D video recreation.

Screen 1 | Player Profile - Record of individual player history.

Key Features:

Live Mode: In Live Mode the player is actively being tracked by the user

Impact Threshold: Each player has a unique impact threshold that determines their ability to handle concussions

Flag Player: Players can be flagged to indicate a history of injuries, or players to be watched.

Impact History: Users can see the entire history of impacts on a player.

Impact Notes: Users can take notes in the player profile.

Performance: NWTN can be also be used to track athletic performance.

Screen 2 | Team View - Team roster of current game/practice.

Key Features:

Live Mode: This state indicates that players are actively being tracked by the user.

Recent Impact Indication: The most recent impact on a player is displayed prominently to the left.

Player Name and Number: Players are identified in two different ways.

Time Between Hits : Tracking when the last hit occurred.

Screen 3 | Hit Replay - The visual replay can help the trainer or coach assess the injury.

Key Features:

Visualize: Seeing the impact on the player through a simulated video.

Graph: Showing the X, Y, Z impact to the trainer.

Screen 4 | Hit Replay - Graph visualization of impact.

Key Features:

Visualize : Seeing the impact on the player through a simulated video.

Graph : Showing the X, Y, Z impact to the trainer.

The graph plotting the directions that the force changed in the athlete’s play is important to show the force at which the athlete’s body received the impact.

Task flow of possible player impact scenario and initial pairing process for coaches.


Tackling the competitive analysis

We wanted to compare what features other competitors on the market had to offer. We created a matrix that displays how competitors compare in terms of impact detection and injury analysis. We looked at six major competitors on the market and two indirect competitors. Our main takeaways were:

- All options are similar in price ranging from $99-$185.

- Most offer basic impact detection, but not all offer additional assessment that could be a valuable asset to coaches and trainers.

- Additional software is often required for use in form of app or assessment device.

In addition to this analysis, we conducted a heuristic analysis on three competitors and NWTN’s interface based on Nielsen’s 10 usability heurisitics. From reviewing the interfaces of Shockbox, Jolt, Headcase and NWTN, we learned:

Concussion detection sensors and apps are a newly emerging product, there are currently no dominant players as of yet and none of the current competitors have a polished, modern interface. This analysis proved to us that NWTN is in a great position to stand out by offering a modern interface and an in-depth analysis tool along with impact detection. There are a good number of impact detection products available, but none offer an outstanding SCAT test. NWTN had a basic “Pocket SCAT” test in the works and we were eager to see how participants reacted to it in our upcoming concept testing.


Although we were left with transcripts of previous interviews from a past UX design team, we conducted our own in order to learn as much as possible about the non-professional athletic world. Going into our interviews, we wanted to evaluate the role of athletic trainers and coaches in regards to equipment distribution, collection and management. We also were looking for those outside of the football realm because NWTN was moving away from targeting football to soccer players.

We spoke with a mix of coaches and trainers and they helped us discover that concussion awareness is becoming an increasing concern for parents and coaches. Devices are growing in popularity to aid in the detection and assessment of head injuries on the field. Equipment distribution needs to be efficient and painless for coaches and their teams. Athletic trainers need to be able to see multiple teams at once, take electronic notes in an evaluation and share information seamlessly with administration and coaches.

Because there is equal concern for preventing head injuries amongst multiple archetypes, we wanted to test providing multiple interfaces for different types of users. This was to ensure the learning curve would be reduced to enable users to get to using NWTN as painlessly as possible.

Another major focus for my team and I was expanding on the current pocket SCAT concept NWTN had adopted from the previous UX work. Many trainers claimed this would make their day to day lives easier, but coches didn’t understand the medical terminology. This is an example where it would be important to have multiple interfaces. A trainer needs access to an in-depth digital SCAT while coaches just want to conduct simple field side analyses.

We chose to focus our scope on these points when creating our multiple question problem statement.

How can the UX team create streamlined interfaces for users who share information but have different needs? How do we address the need for a field evaluation for coaches and an official SCAT test for athletic trainers?


Based on our scope, we finalized the concepts we were going to test in each of our prototypes:

- Different user interfaces for trainers, coaches and parents

- Pairing process of devices and players

- Pocket SCAT concept from previous research

In our second sprint we focused on diverging and deciding on a design for our prototype. Before we diverged, we created a set of design principles that guided the design direction for the wireframes.

We created three prototypes based on our design principles and tested users who were either coaches or athletic trainers. We gathered a list of main conclusions based on the qualitative feedback participants gave us:

More player identification for hit notification - coaches want number, first name and the ability to upload player photos to quickly recognize a player on the app.
Users loved the 3D visualization of each impact.
Having to enter ‘Live Mode’ is confusing and coaches are worried they would forget to turn it on before a game or practice.
Pocket SCAT is too technical for coaches, not technical enough for athletic trainers.

Moving forward, we used these findings to guide our decisions for our final design. We needed to take what the current NWTN prototype was and make it more intuitive for users - This would include removing ‘Live Mode’ all together, simplifying the analysis tool for coaches and removing unnecessary language/details that distract from the main purpose of the product.


Concept testing we did during sprint two gave us a deeper understanding that there will be a multitude of different scenarios and situations that this device will be used in from the distribution situations, users, level of technical skills and relationship to athlete.

We found it beneficial to fulfill the needs of users by providing different, customized experiences. We sought out users in the following roles for our usability testing so we could narrow in on what their most essential needs and goals would be in using NWTN.


Different interfaces for different users

The ability to add team rosters and individual players is a necessity, but the process will differ for coaches and trainers. We adjusted what features should be viewable for different archetypes in order to reduce distraction and unnecessary content. For example, trainers would be able to add multiple schools, teams and athletes, while parents would only be allowed to add multiple players since they would just be monitoring their own children.

Bluetooth pairing of sensors for athletes

Giving coaches the ability to pair players with a sensor as quickly as possible was our goal. Bluetooth allows for an initial set-up that would be more in-depth but will allow for automatic pairing once the sensors are paired to the app.

SCAT for trainers, basic test for coaches

This is an area where coaches and trainers differ. Trainers wanted to see a SCAT test that is relatable to the current paper process the majority are using today and coaches wanted to conduct quick field-side assessments, they didn’t want to deal with a full SCAT assessment. There is a huge opportunity for NWTN to stand out amongst competition in multiple venues if there were a way to create a catered assessment for both roles.

See our entire final prototype of NWTN below



These are concepts we believe would be successful for NWTN to include, but unfortunately we didn’t have the time in this project phase to create and test them.

Fully fleshed out SCAT test for trainers - Athletic trainers we spoke with all agreed their lives would be made easier with a virtual SCAT analysis and we couldn’t call it a SCAT test if it wasn’t the same as the official paper version made currently available by BMJ.

Basic account/premium account - Neil was excited by the idea of a basic account for those that didn’t need an in-depth SCAT tool and a premium account for those that would need it and additional features.

Player statistics - Coaches we spoke with voiced that they would enjoy this feature in order to keep track of player performance and statistics.


My team and I are proud of the work that we did for NWTN and were happy to contribute to a product focused on preventing multiple concussions and potential brain damage for athletes. The co-founder of NWTN was also very pleased with our wireframes that we presented to him and he plans on implementing these in the final product. There was a situation while working on NWTN that we all agreed was a huge learning experience for my entire team, which I found very valuable in order to actively prevent it from happening again. In our first kick-off meeting with NWTN, the co-founder didn’t want to bias my team so he hadn’t fully explained the current state of NWTN. This included aspects of the planned final product that had already been solved and he didn’t plan on changing. We weren’t aware of these solutions until our final meeting in which we presented our final prototype to our client. He had already planned on using bluetooth pairing which is what our final prototype included, but we had already done extensive testing on different pairing concepts. We also removed the “live-mode” feature from the current NWTN prototype after it testing poorly with our participants and he told us this feature had already been removed. From this experience I learned to encourage communication through the entire design process. although my team and I felt that we could have accomplished more if we had known this information from the start, we understood where he was coming from and we were pleased that our design decisions aligned with his vision of NWTN.