Index / Selected Work / Case 02 · ITILITE Homepage
Product Design Prototyping Interaction Design Information Architecture

ITILITE homepage revamp.

Turning the homepage into a fast, self-serve, scalable control center for managing business and personal travel, end to end.

Plate 01 · The new traveler homepage ITILITE · 2024
My Role
Lead Product
DesignerInformation architecture · Interaction design
Timeline
3 monthsWith PMs, eng, support, sales & QA
Users
Travelers,
approvers, bookersBusiness + personal · Power users · Approvers
Impact
14× faster
trip access7s → 0.5s · Conversion <10% → 50%
01 · Problem

The default landing experience was everyone's headache.

The Traveler Homepage is the default landing experience for most users and functions as both a navigation hub and a trip management center. As the product scaled, the experience became difficult to use and reason about.

Six key problems compounded into a single, anxious surface:

Page loads > 11s
Performance had quietly degraded
PDF vouchers
Trips lacked clarity, forcing reliance on PDFs
Mixed contexts
Business + personal bookings blurred together
23+ statuses · 8+ tabs
Cognitive overload was the default state
No recovery
No clear way to resume incomplete or failed trips
Fragmented actions
Post-booking actions were inconsistent

Design constraints: preserve critical existing workflows, support complex backend & approval states, and lay a foundation scalable enough to absorb new features without rework.

I open the dashboard and stare at it for thirty seconds trying to find my own trip.
Frequent traveler, internal interview
02 · Design challenge

How might users instantly know where they are, what state their trips are in, and what to do next?

The goal: keep the homepage feeling calm even as the platform scaled. No new tabs. No new dashboards. Just a sharper sense of place.

Solution · Re-architected around intent
03 · Solution

A performance-first, self-serve control center.

The experience was re-architected around three user intents, entry, recovery, and management, so users always know where they are and what to do next.

Complex trip and approval states were simplified through clearer hierarchy, smarter cards, and in-place actions without page reloads.

Plate 02 · The homepage as a calm departure board 16 : 9 · Above-the-fold capture

Four moves that shaped it.

A re-architecture that reduced anxiety, surfaced recovery, and made complex workflows feel almost mundane.

01

Re-architected around user intent

  • Three clear sections, Centre Stage (entry), Continue Where You Left Off (recovery), Trips & Approvals (management)
  • Prioritized next actions instead of listing everything at once
  • Replaced the feeling of "infinite trips" with structure and hierarchy
02

Made at-risk trips impossible to miss

  • Introduced "Continue Where You Left Off" for approved-but-unbooked, payment-failed, and recently drafted trips
  • 30-day logic with deduplication by route, traveler & mode
  • Ensured users could resume booking without starting over
03

Smarter trip cards & mental models

  • Auto-generated human-readable trip titles
  • Time-based tags, "2 weeks to go", "Tomorrow", "Departs in 3h"
  • Leg-level statuses surfaced without exposing system complexity
  • Quick actions directly on cards to reduce navigation depth
04

Unified complex actions into one flow

  • Embedded modify and cancel actions directly within trip views
  • Ensured partially cancelled trips stayed visible and understandable
  • Consistent patterns across flights, hotels, and cars
Plate 03 · Recovery
Plate 04 · Card system

The impact.

04 · Outcomes
14×
Faster trip access, 7s → 0.5s. The homepage finally feels like a homepage.
−55%
Dashboard load time cut, 11s → 5s through perf-first design decisions.
Conversion rate jumped from <10% to 50%. Self-serve actions rose from 30% to 70%.
9 / 5 / 1
Simplified UX, 9 statuses, 5 tabs, 1 unified page (from 19 statuses, 8 tabs).
05 · Beyond metrics

What the numbers can't say.

The homepage stopped being a place users dreaded opening. Confusion dropped. Support tickets eased. Abandoned bookings finished. And the team got back the time it used to spend defending a slow page.

  • 4× more powerful search, 22 parameters vs the original 5
  • Improved recovery of abandoned and payment-failed bookings
  • Faster task completion due to clearer actions and fewer reloads
  • Reduced support dependency and ambient user anxiety

Field notes & learnings.

06 · Reflection
i.

Clarity beats completeness.

Enterprise dashboards reward restraint. Every additional toggle, status, and label compounds anxiety, show only what helps the next decision.

ii.

Hierarchy beats more labels.

Status-heavy systems need strong visual hierarchy, not more taxonomy. Group, weight, and reduce, let position speak before language does.

iii.

Surfacing next actions reduces anxiety.

"What do I do?" is the question every dashboard answers, well or badly. Designing the next step explicitly outperformed adding features.

iv.

Performance is a design responsibility.

Load times are part of the experience. Working with eng on payload, caching and skeleton strategy moved the perceived needle more than any layout choice.

07 · Takeaway

Make complexity feel predictable, recoverable, human.

Great enterprise UX isn't about simplifying the product, it's about making complexity feel predictable, recoverable, and human.

This project reinforced that designing for scale is less about new features and more about giving people a calm, confident sense of where they are.

Next chapter · 03 / 04
Hotel room deduplication
Open to opportunities

Like what you see?
Let's connect.

Status
Available
Q3 2026
Connect
LinkedIn
Loc.
Bangalore,
India