Redesigning the primary navigation for Ahotu, the world's largest endurance sports calendar. A click here has to work for three different purposes at once: the athlete hunting for their next race, the first-timer who's never used the site before, and search engines trying to crawl the whole thing.
Role
UX Designer
Team
Design Lead, Product Manager, Developer, Tech
Scope
Flyout Mega Menu for Improved Navigation and Event Visibility
Source
Jira DEV‑5924 · DEV‑5881 (SEO)
01
The short version
The site had outgrown its navigation.
Ahotu lists endurance races in more than 195 countries. Its old navigation couldn’t keep up. From the menu, a visitor could pick a sport or a country, but not a distance or a month, and one click on Multisports pre-selected eight filters they had to clear before the results made sense. Every decision had to work two ways at once: for a person clicking through, and for a search engine crawling every link.
Along the way, we ran into real problems:
At certain breakpoints the columns started overriding the available screen space, so we had to design a fallback instead of forcing everything to fit.
Some sports also needed their distances rethought into curated spans rather than raw numbers, so users could filter by something they’d actually recognise.
Mobile turned out to need a completely different filtering solution than the desktop mega menu.
A “Right Now” column went through a lot of testing but ultimately didn’t make it into the final release.
6
top-level categories
4
filter columns, shipped
28
sports, distances checked one by one
02
The brief
The menu had to work for people and for search engines.
Behind the ticket was a simpler problem: the old filtering hadn't kept up with how the site had grown, and a menu that couldn't keep up made Ahotu feel outdated to the athletes it needed to convert. The goal wasn't just a new component: it was a menu effective enough that someone could find their race without friction, and credible enough that Ahotu looked like the platform it actually is.
The ticket asked for a flyout mega menu that made bookable events, top event countries, and event highlights easy to find, while staying fully crawlable. Two disciplines had to agree on the same component: Usability and SEO.
Had to work for people.
Expands on hover or click, without hiding content from search engines
Responsive and accessible: ARIA roles, full keyboard navigation
Menu load time can't hurt page speed
Had to work for crawlers.
Every item a real HTML <a> link, not a JS click handler
Rendered server-side, present in the initial HTML
schema.org SiteNavigationElement markup
03
Research & discovery
We looked outside our category first.
Before drawing anything, we built a reference board to explore how other e-commerce and outdoor retail sites approach mega navigation. We looked at ka-yo.com, Zalando, The North Face, YETI and Care of Carl, among others. IKEA also became a recurring reference throughout the project. Its approach to navigation helped inform several different decisions at different stages of the design process.
References board. Benchmarking flyout structures across ka-yo.com, Zalando, The North Face, Boozt, Bataleon, YETI, Care of Carl, Outnorth and IKEA before any Ahotu screens were drawn.
Our own search showed where the friction was.
The team already knew the old search had a problem, and fixing it was a big part of why the mega menu was needed. Testing our own site confirmed how bad it was. One click on “Multisports” pre-selected all eight of its subcategories at once. Add a country picked from Popular Countries, and users had nine filters to clear manually before the results meant anything. Our own note on the board: “users are met with multiple pre-selected filters which creates friction.”
Filter exploration @ahotu. Results page after one click on “Multisports” and a pick of “United States”. The nine active filters are outlined in red.
Each filter became its own choice.
Three iterations later, picking Running and then Half marathon led to just two filters being applied: “Trail running” (part of Running) and “Half marathon.” The country wasn't forced on the user either: it was just a suggestion they could pick or ignore. That's the real reason behind the final menu layout: instead of clicking one category and having everything pre-selected for you, Distance, Popular Countries, Month, and Popular Events each became their own separate option, so a user could pick from any of them, in any combination, on their own terms.
04
Finding the structure
The four columns evolved step by step.
The final column structure didn't emerge all at once. It started with sports, then added Distance and Popular Countries, and eventually explored two different approaches to the Popular Events section. The final four columns were the design lead's call, and one I agreed with.
Every iteration was tested against real data.
As early as possible, I replaced placeholder content with real event names and counts researched on Ahotu’s own site, to see how the structure would hold up at scale. At the time, that ranged from 2,406 Running events in the United States and 1,406 in France to 650 in Canada and 320 in South Korea.
Bookings and complexity decided where to start.
Sport prioritisation was based on booking data rather than intuition.
454
Running
239
Trail Running
71
Triathlon
49
Walking
Bookings through Ahotu checkout, one month
I asked the team for that data and used it to decide where to focus first: Running, as the most booked sport, and Multisports, as the most complex, since it holds the most sports. Both got the deepest exploration early on. Bookings told us where the business was; complexity told us where the design was most likely to break.
05
Building the system
One pill component, reused everywhere.
The sub-nav pill started as a single Figma component with three states: default, hover and active. It is the small selector used to switch between categories like Triathlon, Duathlon and Swimrun. I first built it for Running, then adapted it for Cycling before scaling it up to the full eight-item Multisports navigation. From there, every pill across the project was built from the same component, keeping the interaction and visual behaviour consistent.
Consistency was the harder problem. With seven or more horizontal sub-nav variations, every click, hover and active state had to behave consistently, including the correct underline state. It's the kind of work that disappears in the final design, but getting those small interactions right is what makes the experience feel seamless.
The sub-nav pill component and its variations, all wired to behave the same way.
Neither of the old distance filters fit a menu.
A parallel taxonomy problem, running underneath the UI work: the old site's distance filters used checkboxes on some sports and free min/max fields on others. A fixed, clickable mega-menu column can't hold either: it needs one curated list, decided sport by sport.
Distance exploration. A sport-by-sport audit across roughly 28 sports: Alternative (external reference standards) against Ahotu (existing site) against Final (adopted list), with a change/no-change legend for every row.
Checking every value by hand found a live bug.
Doing this by hand for Running surfaced something nobody had caught before: the live filter order was Ultramarathon, Marathon, Half marathon, 5 km, 10 km. Five kilometres listed before ten, in a list that's supposed to run longest to shortest. A real ordering bug, live in production, found only because every value was being manually re-typed and checked. "Nobody had seen it, but I found it."
Niche sports needed named distances, not a text field.
The same audit is also where the 'span' idea came from. Niche disciplines like Aquabike and Aquathlon don't have a few standard race distances the way running does. On the old site, that was handled with a free-text field where a user typed in their own minimum and maximum distance, but a fixed menu column can't offer that kind of open-ended input. So instead of forcing a text field into a simple menu, I looked at how official race formats name their distances, like world championships and Olympic-distance events, and turned that into a short list of names athletes would recognise. For Aquabike, for example, that list is: Long distance (140.6 km), Middle distance (70.3 km), Olympic, and Sprint. It's a UX decision about what a user recognises, not a technical shortcut.
06
Four things worth slowing down for
1
The existing search icon already solved it.
The homepage's prominent "Filter & Search" CTA sits centrally in the hero, and the open mega menu visually covers it. Returning users who already relied on that button could lose it entirely. The fix required no new design: the header already had a persistent search icon, top-right, that stays visible and clickable with the menu open. The real work was noticing the risk and confirming the existing pattern already covered it, rather than adding something new to solve a problem that already had an answer.
2
Every column needed a “Show all”.
Two separate testing moments converged on the same fix. Stress-testing the Popular Countries column with a long list raised the obvious question: what about a country that isn't in it? Testing the mobile version made it concrete: dead ends. Note on the design-review board: "To not create dead ends, I think we need to add 'Show all…' to all filter categories."
It also came from watching how athletes actually search: most look for a sport or a distance before they think about a country. That's why Distance became the more important column to get right, and why Popular Countries, being more of a secondary path, needed its own "Show all" link the most, since a country missing from that short list had no other way to be found.
3
The ideal fix was too slow to ship, so we shipped the honest fallback.
Fully populated columns plus longer translated copy (French routinely runs longer than English) could push the menu wider than its breakpoint. The ideal fix, extending the horizontal-scroll-with-arrows pattern already used for overflowing pills to the whole menu was more complex for engineering to build on the release timeline. Rather than delay, the design lead chose a simpler compromise for v1, and I agreed: drop the Popular Countries column entirely at tight breakpoints, giving the space back to Distance, Month and Popular Events. It's not the ideal solution, but it's the one that shipped on schedule.
4
“Right Now” wasn’t cut for scope, the data didn’t exist.
The columns are automatically populated, using data the backend already had: which countries had events, which months, which distances existed for each sport. But a 'Right Now' column (New events, Early bird, Registration closing soon) needed something the backend had never tracked before: there was simply no existing way to know 'this event is new' or 'registration closes soon.' That wasn't a decision to cut a lower-priority feature. It was a real gap in what the system could do, and we only found it once we sat down with tech to actually scope the build.
07
MOBILE: A DIFFERENT PROBLEM WITH A DIFFERENT BEHAVIOUR
A phone can’t hold side-by-side columns.
The desktop pattern depends on hover or click to open a flyout, with columns laid out side by side. That doesn't survive a resize down to a phone. The key thing I'd take from this project: mobile needed a genuinely different interaction, not a smaller version of the same component.
A four-level drill-down, borrowed from IKEA.
What I designed instead, in close discussion with the design lead, is a four-level drill-down, a pattern we first saw in IKEA's mobile navigation during research. It works like this: tap the hamburger for six sport categories, tap one to reveal its individual sports, tap a sport to reach its filter overview (Distance, Popular Countries and Month, with Popular Events listed directly below), tap a filter to reach its options.
Mobile prototype, the four levels. From the homepage, Filter & Search opens six sport categories, a category opens its sports, a sport opens its filter overview with popular events listed below, and a filter opens its options.
Every level slides in from the right, and back always works the same.
The convention for desktop mega menus is to drop down from the top. That doesn't fit a hierarchy you're moving forward into. So each level instead slides in from the right: the same direction, every time, tap after tap. The reference for that motion, again, was IKEA's mobile navigation. The back control follows the same logic: identical position, identical behaviour, on every single screen in the drill-down, so a user can always step back predictably no matter how deep they've gone. Small rule, but it's the kind of consistency that decides whether a four-level flow feels smooth or feels lost.
08
What didn't make it
Two ideas got real design work and didn't make v1, for different reasons.
The "Right Now" column, mid-exploration. Positioned deliberately first, leftmost, the position a user's eye reaches first, following the same convention retail sites use to surface "New" releases.
The ‘Right Now’ column.
Got as far as a full mockup with icons and copy for New events, Early bird, and Registration closing soon (shown above). The reasoning for the cut is covered in finding 4 above: the backend had no concept of “new” or “closing soon” to query. That was a genuine backend gap, so it wasn’t shipped, and it’s a candidate to revisit if that data ever gets modelled.
The commercial and promotional slot.
A fifth position at the far right of the desktop menu, inspired by IKEA's own flyout, which uses that spot for a lifestyle image and a "Best sellers!" callout. Our version leaned more commercial: sports-gear placements or event sponsor slots tied to the selected category. A real monetisation opportunity riding on space the menu already occupies. It was deliberately deferred and is planned for a future release.
09
Pre-production design review
Every review note was tracked to sign-off by both Dev and Design.
Once development had a working build, we ran a structured review pass with priority-labelled sticky notes.
Design review board. "Switch order of 5k and 10k" (the self-discovered ordering bug from the taxonomy audit) tracked through to a confirmed fix, Dev✓ Des✓; "Selected sport category should stay underlined" signed off by Dev, Des still pending, shown against the built menu it applies to.
What came out of the review.
✓Selected top-nav category (e.g. "Running") stays underlined while its menu is open, closing the gap noted on the review board above
✓Winter sports sub-nav reordered by actual race volume, not alphabetically
✓Tab selection resets on menu close or category switch, so a stale sub-tab can't persist where it shouldn't
✓Mobile account buttons (Log in / Create account) kept in their existing position, there was no reason to change what already worked
✓Drop-shadow removed from the top edge; a plain visual clean-up
10
Tested, not just designed
Every sub-tab was tested in a click-through prototype before any code was written.
Every sub-tab across every category was wired into an actual click-through prototype in Figma, not a set of static comps handed over with a hope. That's the difference between a design that looks finished and one that's been proven to actually work as a sequence of real interactions, mobile included.
Wired prototype. Every sub-menu tab, Triathlon, Duathlon, Swimrun, Aquabike and the rest, connected into one testable flow, tried by the team and colleagues across the company to check that it felt intuitive.
11
The outcome
Every category got the same level of finish, not just Multisports.
The point where I’d say the project actually “nailed it”: real, category-specific content throughout, after Multisports had carried nearly all the detailed exploration.
All six categories, one system. Running, Cycling, Multisports, Water sports, Winter sports and Other, each with its own real data: Cycling's distance column in km ranges, Winter sports reordered by race volume.
And then the version that matters most: what's actually live.
Live on ahotu.com: Running. Distance, Popular Countries, Month and Popular Events, each with its own "Show all." Popular Countries shows real, live counts up to twelve countries (United States 27,820 down to Australia 190). Both the “Right Now” column and the promotional slot stayed out of v1.The homepage this menu lives on top of. "Discover the world through endurance," with the "Filter & Search" CTA the mega menu had to learn to coexist with, not compete with.
It launched, slowed the site down, and went live again the same afternoon.
It went live on 21 May 2026. Within half an hour, the menu turned out to slow the site's response time, breaking one of the brief's hard requirements. The developer rolled it back, fixed the speed issue and had it live again the same afternoon. Engineering also confirmed the menu is fully visible to Google's crawlers, the other half of the brief.
The first reactions went straight to Popular Events.
The first reactions across the company went straight to Popular Events, already seen as a future marketing surface: the same territory as the promotional slot deliberately left out of v1. In the launch announcement, the design lead credited the menu to me and the developer.
12
What I'd carry forward
A pattern doesn't survive a breakpoint by default.
The desktop mega menu and the mobile drill-down solve the same problem with genuinely different interactions. Treating mobile as “the small version” would have shipped something worse on both ends.
The best fixes are sometimes findable, not inventable.
The single biggest navigation risk in this project, the mega menu hiding the site's main search CTA, was solved by noticing an existing pattern already covered it, not by designing something new.
Rigour shows up as data, not opinion.
The 5 km/10 km ordering bug and the “span” categories for niche sports: neither was visible from the interface alone. They came from manually auditing the actual underlying data, sport by sport.
Honesty about trade-offs is part of the deliverable.
The Popular Countries breakpoint fallback and the deferred promotional slot weren’t failures to hide: they’re evidence of decisions made deliberately, against a real deadline, with the reasoning intact.