Using inter-run notifications to keep you on pace
Bullseye a run-tracking app
My role
Product designer
Timeline
Apr 2023 - Apr 2024
The problem
Bullseye is a new run-tracking app that has been stuck development limbo. It lacked an identifying feature that would bring in new users and grow an existing user base.
The solution
We created a run-tracking system using pre-run goal selections, inter-run audio notifications, and wearable interactions to keep users on track with their fitness goals.
The results
Based on user feedback, Bullseye found its ‘ah ha’ moment for its users, and has moved along into the alpha stages, breaking the development gridlock.
Understanding the user
User Interviews
We invited potential users, from novice to marathon level runners,
to talk about their running experiences.
Insights
73%
use headphones during their run.
26%
use an Apple Watch while
they run.
66%
wish they could see how their
run is going in real time.
53%
already manually keep track of their pace, run time, and distance.
Design decision
What if we created a system for selecting metric goals
and introduced novel ways of notifying runners of their progress?
Testing and iterating
Usability Testing
Run goal selection
3 iterations were tested using 10 participants.
Conducted over zoom with screen sharing.
Audio notifications
A running stress test with 5 participants.
Focused on comprehension of information during a run.
Run goal selection
Version 1 - The Valiant Try
“It’s fine for when I am just using one goal, but once I select more than one it’s just way too much.”
Version 1 was a valiant try, but suffered once all targets were selected. Seen here.
Not all was lost, as the pace selector was well-liked for giving pre-generated pace goals. The options would eventually be based on users' pace averages. The other inputs needed some serious improvements.
Version 1 had an average task completion of 70%. When debriefing the participants, Version 1 came with a 60 on the system usability scale, showing us it really needed some work.
Version 2 - A Step Backward
“What if I want to just start a run? And not go through this rigmarole?”
I realized I had my blinders on. I was so focused on the runner enthusiast. What if it's someone new to running? A new runner doesn’t necessarily know what pace they want to run, or even if they have a goal. What if they selected a goal outside of their abilities? So many hurdles just to move your legs.
We went to the drawing board with another point of view in mind.
Version 3 - Off to the races
Goal selection in action
A new coat of paint
When it came to the UI color scheme, an assumption was made that a dark mode UI would be the most optimal for high sun pollution environments. As we tested both versions, that assumption was proven incorrect. Swapping to a lighter UI and bringing in an orange action color led to a more inviting and energizing color scheme.
"Oh, now I get the notifications selection. I love that idea! That would be so helpful."
We finally got it!
Version 3 gave runners a clear way to select their goals and when they would be notified.
0% error rate.
78 SUS score, putting us on a solid usability foundation.
Lowest time on task of versions tested.
Let's move on to how users interact with their run goal notifications.
Audio notifications
The development of audio notifications started with finding our tone. We faced challenges with how the information would be communicated, especially when it mattered.......during a run.
We got inventive and had the participants start their run while on a call with us.
Throughout the run, I would read out some example prompts varying in tone and information.
After, I would get feedback on which tone and notification length worked best.
You're currently running at [pace]. Your goal is [pace goal]
Keep it simple
We found a simple and focused tone. Ensuring that users can quickly absorb and act upon the information while running.
Results
Net Promoter Score of 64.
A solid MVP that can be expanded and scaled.
"Hey, when is that running app you had me test for coming out?"
- Mike O.
User/Tester
What I learned
You read all these case studies that show a linear and clean design process. When the reality is, I found, messy. We overcame a lot of challenges to create just this slice, but I am really proud of the work done with Bullseye.
If I were to do it over again, I would spend more time with inexperienced runners. Missing that angle could have saved us a lot of time and headaches.
Plans for future development include exploring how to keep users motivated and engaged, as well as on-boarding users to hit the ground running.