Velox.
Velox is a central hub for adaptive endurance training, user rankings, and personal analytics. As a result, information density can increase user cognitive load and hesitation. To tackle this problem, a process of deep user research and iteration proved crucial to improve user onboarding time, post activity input, and hierarchy.
Foundations.
What is the priority for advanced runners physically and emotionally? To answer this question, I conducted interviews with top NCAA cross country coaches throughout the US. Throughout this process, responses were recorded and cataloged into a broader set of categories to inform information hierarchy and design structure. Here are some snippets from some of my conversations...
Persona Creation.
The next step, identifying our target users. Sounds easy enough, but in reality...it is deeply nuanced. My team and I identified two types of users through user interviews and observational sessions.
Carter is a collegiate endurance athlete who prioritizes personal analytics and trends to gauge performance and confidence. Carter's philosophy is grounded in hard work and science. So the more data he has, the better he can understand his potential. He's a data-driven athlete who enjoys dissecting workout markers and racing simulations.
Max prioritizes performance comparison to iterate on his training methods alongside his current fitness data. He's a competitive athlete who graduated out of formal training settings and lost access to professional coaching. Max is self-motivated with high goals for his running career, and he's eager to engage with the social side of running.
The Problem.
We identified the user's clear "want" after extensive user research, and it turns out they are already determined and self-motivated, so what's the problem?
Well to start off, a target user may really want to see 100+ different metrics alongside our ranking systems, workout plans, and analytics...but do they really have the bandwidth to process all that information productively? In other words, the challenge is: how can I build a mobile experience that reduces cognitive overload of information-dense systems, while satisfying data-hungry users?
Structuring & Wireframing.
On to Figma, where I wireframed the basic structure and card layouts for this challenge. This process was imperative in brainstorming how to break up dense user metrics, optimize user workflows, and balance the user's need for a rich data-driven interface while still keeping it digestible.
.png)
Solution.
Riding the line between user expectations and creating visually digestible interfaces proved to be quite the challenge. However, by utilizing cards in my designs, I broke up previously overwhelming dense metrics into efficient views. Not only did I improve textual overloading, but I also emphasized user control and reduced clicks by designing all KPIs to be swappable based on user preferences.
Dashboard View
The weekly view provides a visual cue to weekly training progression, in alignment with target users' personalities who see positive reinforcement in maintaining consistency. Additionally, ranking updates are customizable to suit a user's preferred event. As a result, target event viewing dropped by approximately 3 seconds.
Establishing visual hierarchy, the biggest card is the most important. Here, users are given today's activity summary, reducing user intervention by 1 click (small...but they add up).
Workout View
Breaking down cognitive overload, flagged consistently for reps, importance, and RPE markers, with color coded sections to emphasize that. The detail page includes an activity notes toggle, reducing 1 backtrack click.
Increasing user context. Target users feel secure with credibility and explanation.
Calendar View
Reducing user cognitive load by utilizing color temperature, signaling which days are ranked in-season. Monthly insights are presented to enhance user context around training type and mobile activity stress metrics.
Increasing user context and promoting member confidence.
Reflection.
Building Velox has given me the tools to take ownership of my designs, iterate frequently without attachment, and communicate with developers effectively. In this experience, I've had to be 3 things at once: a software dev, product designer, and team player. Velox has been a valuable experience that has taught me more about building products than anything else to date.
.png)
.png)