Overview
Problem
Objective
Research
Branding
Navigating the mess
Reiteration
Reflection
Some projects go beyond the work itself and hit closer to home. The New York Road Runners case study was one of those moments — as a new runner, designing for a community I’m part of made the project feel personal and fueled the ideas behind it.
... without a central platform, NYRR struggled to establish brand cohesion, support smaller races, or retain users outside marquee events. Behind the scenes, NYRR faced significant limitations around authentication, data storage, and the integration of two third-party APIs. These constraints made it difficult to build a seamless, scalable, and unified mobile experience.
The experience needed to feel reliable for spectators, motivating for runners, and flexible enough to grow with NYRR’s future roadmap.
Many were unaware that NYRR hosted more than just the marathon. Technical and legal constraints—particularly around login, personalization, and data storage—also surfaced early, shaping the scope for our initial release.
The shoot, brought to life with dynamic, authentic imagery, became the thread tying the identity together — showcasing the determination of runners, the vibrance of the crowds, and the shared joy that defines NYRR.
I explored new navigation systems, content hierarchies, and modular card structures that could scale across a full race calendar. Early wireframes mapped how spectators switch between tracking, results, and event content under real-time pressure. Because login and profile APIs were not feasible for the initial release, we prioritized discoverability, race information, and tracking clarity. This required restructuring flows so they were intuitive even without personalization.
The app was coming along, but there was a big problem hidden within
The app was reliant on multiple third-part APIs for different datasets
We partnered closely with the development team, maintaining constant communication and collaboration. By understanding development limitations early, we planned phased design releases that aligned with their sprint cycles, ensuring design updates stayed in sync with development and keeping the project on track for a successful launch.
The app is launched 🎉 but it doesn’t stop here!Â
After the 2.0 release, we conducted user testing and monitored live app behavior to understand how runners and spectators were interacting with the new experience.
Real usage exposed friction points that were less visible in controlled testing—particularly around race discovery, tracking clarity, and the way content surfaced during event weeks. We also gathered feedback from NYRR stakeholders and event teams, who highlighted operational needs that weren’t fully addressed in the initial launch.
total users engaged with Tracking
used the Following feature
hmm... where to start? This project pushed me more than any large-scale product I’ve worked on, and it became a defining moment in my growth as a designer. Navigating multiple APIs, shifting requirements, and an immovable race-season timeline forced me to think more strategically, prioritize with intention, and communicate more clearly across teams. I learned how to advocate for design while staying flexible to technical realities, and how to turn constraints into resilient, scalable UX decisions.
Seeing the app perform under real race-day pressure—used by hundreds of thousands of runners, spectators, and supporters—was both validating and humbling. It confirmed many of our core decisions while also revealing areas only real-world use can expose, shaping how I approached iteration and refinement.
What made this project especially meaningful is that, over its course, I also became a runner myself. I trained throughout the redesign journey and went on to run the 2025 NYC Marathon—a full-circle moment that deepened my appreciation for the community we were designing for. Experiencing the race firsthand gave me a new perspective on the emotional, logistical, and communal aspects of running, and it’s a journey I plan to continue for many years to come.
Ultimately, this project not only strengthened my craft—it expanded my perspective. I walked away a more thoughtful, adaptable designer, with a clearer sense of how to build systems that scale, lead through ambiguity, and create experiences rooted in purpose. This work marks a noticeable step forward in the designer—and the runner—I’m becoming.