Back

Scaling Jetpac's navigation

Restructuring Jetpac's navigation from a single-product hierarchy to a four-product structure

RoleProduct Design Lead
Collaborators1 Designer
3 Engineers
1 Product Manager
DurationDecember 2025 – March 2026
ScopeWeb & App Navigation
Information Architecture
Interaction Design
Contributions

Impact & Scope

Defined Cross-Platform StrategyUnified disparate desktop dropdowns and mobile tab bars into a single, scalable navigation framework.
Navigated Executive AlignmentFacilitated trade-off workshops with the CTO and CGO to balance technical constraints with revenue goals.
Systemic HandoffCreated a responsive navigation component library and state matrix (hover, focus, active, disabled) for seamless engineering handoff.
Opportunity

Giving new product lines room to grow without hurting core revenue

Starting as an eSIM app, Jetpac expanded into Voice, Lounge Access, and Fast Track, but only 3% of customers bought products outside of eSIMs. The challenge was to restructure web and app navigation to give every product dedicated visibility without displacing the core eSIM flow driving 95% of revenue.

95%
of revenue driven by eSIMs
3%
cross-sell rate across all products
2%
bought Voice
0.5%
Lounge Pass & Fast Track each
Impact

Quantifiable outcomes and structural improvements post-launch

Voice, Lounge Access, and Fast Track now have dedicated entry points for the first time. The 3% cross-sell baseline was the direct target; post-launch conversion data to follow.

-29%
Page reduction
5→4
Main nav sections
0→4
Dedicated entry points
Problem

Jetpac had outgrown its navigation

Original navigation
  • 1
    The structure had a commercial costOnly 3% of customers were purchasing anything beyond eSIMs: Voice at 2%, Lounge Pass and Fast Track at 0.5% each. The products existed. The navigation made them invisible.
  • 2
    No home for new productsVoice, Lounge Pass, and Fast Track had no unified entry point. On web, they were missing entirely. On app, Voice had its own tab while Lounge and Fast Track were in "Perks," only accessible as data pack add-ons.
  • 3
    Misplaced and duplicated contentCommercial links were buried under company information. The same items appeared across the nav and footer with no clear hierarchy, creating conflicting wayfinding and no obvious path to conversion.
Competitive Benchmarking

Auditing multi-product platforms to scale Jetpac's architecture

I audited Jetpac's sitemap and benchmarked it against direct eSIM competitors (Airalo, Holafly) and multi-product fintech apps (Revolut, Wise) to find scalable patterns for surfacing new product lines.

Competitive Audit Matrix
Key Takeaways
Functional Hubs over ListsGrouping services into distinct hubs prevents menu bloat as new products launch.
Contextual DiscoverySecondary features convert higher when integrated into primary user flows, not hidden in "More" tabs.
Platform ParityStandardizing product names across web and mobile minimizes friction for travelers switching devices.
Information Architecture

Balancing core business goals across 3 sitemap directions

To align internal stakeholders on the 3 sitemap options, I facilitated trade-off workshops with the CTO and Chief Growth Officer to evaluate technical complexity against cross-sell potential.

What did the stakeholders push back on?

Chief Growth Officer (Business Priority): Pushed for maximum surface-level exposure of Voice, Lounge Access, and Fast Track to directly address the 3% cross-sell baseline.

CTO (Technical & UX Constraints): Favored a minimal header structure to prevent mobile viewport clutter, reduce API load times, and preserve the high-converting eSIM checkout funnel.

The Design Compromise (Option C): I advocated for 4 Dedicated Product Hubs by demonstrating that consolidating redundant sub-pages (reducing total page count from 28 to 20) created enough real estate to give new products dedicated entry points without adding top-level visual clutter.

Solution Architecture

Translating one sitemap into platform-native interaction models

Aligning on the App Navigation

Three proposals came from three different parts of the team. Each reflected a different view of the app's primary job.

Proposal 3 was mine. Voice, Lounge, and Fast Track are products, not navigation categories. Everything purchasable belongs in the Store. Home, Store, Manage, Profile maps to how users think: arrive, buy, manage, account. Leadership aligned on it.

Exploring the Navigation's Visual Language

The Manage tab had no icon that clearly communicated its purpose. I explored 27 combinations of icon styles, active states, and label treatments before the team converged on a direction.

27 nav bar iterations: Stars indicate team preferences across icon styles and visual treatments

The preferred direction used an underline active state. Leadership flagged it as outdated before handoff. The final version uses colour, label weight, and a filled icon. 3 signals, so the active tab reads clearly without relying on colour alone.

Desktop Web

Mobile prioritized quick access, but desktop needed to support research, comparisons, and account management across a larger canvas.

Header Layout ExplorationsTested over 10 navigation bar variants, evaluating search bar placement, currency switchers, and global utility actions.
Mega-Menu DiscoveryHover-triggered mega-menus for Voice, Lounge Pass, and Fast Track let users compare features and reach product pages without leaving the page they're on.
Responsive ParityMapped mobile tab bar categories 1:1 to desktop header items, keeping labeling and design tokens consistent across every breakpoint.
Solution

Website Navigation Bar

The new desktop navigation introduces a two-level hierarchy that places Products first to support multi-product growth. High-frequency utilities like Language and Currency move to a dedicated top tier, keeping the primary bar focused on commercial discovery through rich contextual mega-menus.

Same four sections, different structure for mobile. A full-screen drawer contains Products, Language, Currency, and account access. Outlined below are the 3 primary changes made.

1Half-page to full-screenExpanding Products and Resources to 11 sub-items created two competing scroll contexts in a half-page drawer. Full-screen removes that conflict.
2Products added as a top-level sectionThe old nav had no Products section at all. Voice, Lounge, and Fast Track were invisible on mobile entirely.
3Language and Currency separatedPreviously combined into a single pill in the top bar. Now surfaced as individual rows in the drawer, making each setting independently accessible.

Surfaces all four products (Data, Voice, Lounge Pass, Fast Track) right inside the drawer, giving non-eSIM offerings dedicated entry points on mobile for the first time.

Groups secondary content and utilities into collapsible accordions, keeping the drawer easy to scan without crowding primary conversion paths.

Website Search

The original search only returned eSIM destinations. The new design keeps Data results primary while surfacing Voice, Lounge, and Fast Track as a persistent column alongside.

App Navigation Bar

4 tabs: Home, Store, Manage, and Profile. Active and inactive states are distinguished through icon fill, colour, and label weight.

Learnings

What I learned

  1. 1
    Don't reference the pastIn a startup, whatever is currently live becomes the default benchmark for "good." But the existing nav was built for a different version of Jetpac which was a single-product app. Treating it as a reference point anchored early conversations to incremental changes rather than the structural rethink the product needed.
  2. 2
    Reduction is a harder sell than additionGoing from 28 to ~17 pages meant convincing stakeholders to let go of pages they'd built and owned. Addition feels like progress; removal feels like loss. I underestimated how much of the IA work was change management, not just design.
  3. 3
    Handoff is not the finish lineThe underline active state for the App I designed got flagged as visually outdated before the handoff review by a stakeholder. The final version changed as a result. On a live product, the design continues to be challenged after you've marked it as complete.
View more projects