Case Study · 07

IRCTC Redesign

A ground-up redesign of India's busiest railway booking platform — replacing a cluttered, frustrating experience with a calm, intuitive interface for 14M+ daily users, with cultural sensitivity and accessibility at its core.

UX Design Gov-Tech User Research Accessibility Mobile-First

Role

UX Designer — Research, journey mapping, wireframing, hi-fi prototyping, usability testing

Duration

6 Weeks · 2024

Platform

Web · Mobile (iOS & Android)

Domain

Gov-Tech · Travel · Accessibility

14M+

Daily Users

6

Screen Flows Redesigned

22+

Languages Supported

67%

Faster Booking Time

The Problem

A platform used by millions, designed for no one.

IRCTC is India's only railway booking gateway — not optional, not replaceable. Over a billion transactions flow through it every year. Yet the design hadn't seen a holistic rethink in over a decade. Users weren't just frustrated; they were anxious. Every booking felt like navigating a bureaucratic maze under pressure.

01

Cluttered Information Architecture

Critical actions buried under irrelevant categories. Users couldn't distinguish the primary booking path from secondary utilities, causing wrong-path errors and repeated back-navigation.

02

Mobile-Hostile Layout

Over 70% of sessions on mobile, yet the interface was desktop-first and table-heavy — requiring constant pinch-zoom just to read train names and times.

03

Accessibility Gaps

No multilingual support despite India's 22 official languages. Low contrast, tiny tap targets, and zero accommodation for low-literacy users who form a huge portion of the base.

"Users were abandoning bookings mid-flow — not because the trains weren't available, but because the interface made them feel lost."

User Research

Understanding the human behind the booking.

Two-week research sprint: 18 user interviews across tier-1, tier-2, and tier-3 cities; competitive benchmarking against MakeMyTrip, Trainline (UK), and Deutsche Bahn; plus a full heuristic evaluation of the live IRCTC flows.

Three distinct personas emerged — each with fundamentally different needs, mental models, and failure points.

01The Anxious Planner — books months ahead, terrified of waitlists. Needs clear confirmation status, PNR tracking, predictive availability. Trust is everything.
02The Last-Minute Traveller — needs speed above all. Can't afford to re-enter data. Saved profiles, smart defaults, and instant class availability are critical.
03The First-Time User — may have limited English, unfamiliar with booking classes. Needs vernacular support, plain-language status, and a forgiving flow.

"I just want to book a train. Not solve a puzzle." — Research participant, Nagpur

Before vs After

From broken to seamless.

Before

  • Average booking completion: 12+ minutes
  • Drop-off at passenger details: ~38%
  • Captcha failures causing session loss
  • PNR status required 3 separate tools
  • No seat visualisation in berth selection

After

  • Booking completion in under 4 minutes
  • Progress indicators cut mid-flow drop-off
  • OTP-based login, zero captcha friction
  • Unified dashboard: PNR, Live, History
  • Visual berth map with live availability

Design Process

From chaos to clarity.

A double-diamond process — diverging wide in research and ideation, converging hard in iteration and testing. Six major screen flows redesigned, each validated with moderated usability sessions.

01
Discover
User interviews, heuristic eval, competitive audit, accessibility review
02
Define
Persona synthesis, journey mapping, pain-point prioritisation
03
Ideate
Crazy-8 sketching, card sorting for IA, design principles workshop
04
Prototype
Lo-fi → mid-fi → hi-fi in Figma, interactive HTML prototype
05
Test
Moderated usability sessions, task completion rates, accessibility checks

The Design

Meet RailConnect.

Renamed RailConnect as a design concept, the platform was rebuilt around three principles: Calm Confidence (reduce cognitive load), Transparent Progress (always tell users where they are), and Inclusive First (design for the hardest use case). Explore all six flows live below.

Interactive Prototype — RailConnect
Home Results Booking PNR My Bookings Live Train
01

Visual Design

Cultural palette, not a cliché

Lotus pink and sage green draw on Indian cultural motifs without stereotyping. The lotus (national flower) and sage (calm, heritage) create contextual trust in a platform that badly needed it. The deep plum background grounds the UI in authority while staying warm.

02

Interaction Design

One search, one card

The original interface exposed 14 fields simultaneously. The redesign collapses everything into a single hero search card — from, to, date, class. Secondary options only appear after the primary action is taken, dramatically cutting decision paralysis and reducing time-to-search.

03

Accessibility

Colour as a language system

Confirmed, Waitlist, RAC, and Cancelled each have a dedicated colour — but always paired with a text label. Never colour alone. This meets WCAG AA contrast requirements throughout and ensures the interface works for users with colour-vision deficiencies.

Key Features

Built for every kind of traveller.

Smart Search Card

Collapsed, single-action search with swap button, date picker, and class selector — all in one place, with zero extraneous fields visible.

Live Train Status

Real-time station-by-station tracking with delay indicators, visual progress timeline, and platform number updates.

PNR Status Dashboard

Unified view of booking confirmation, waitlist position, and passenger berth allocation — all in one card, no separate tools needed.

Language Switcher

One-tap access to 22+ Indian languages across all booking flows — designed for first-time users in tier-3 cities.

Outcomes

Results that speak for themselves.

Moderated usability testing with 12 participants across 3 cities, benchmarked against the original IRCTC interface for identical tasks.

67% Faster
Booking Time
92% Task Completion
Rate in Testing
4.6/5 Usability Score
(SUS Scale)
0 Critical Errors
in Round 2 Test

Reflections

What I learned.

01Constraints are creative fuel. Designing for a government platform with zero backend flexibility forced front-end creativity. The best solutions came from working within limits, not around them.
02Trust is a design element. Indian users carry historical frustration with government interfaces. Every confirmation message, every error state was a chance to either build or destroy trust.
03Inclusive design is just good design. Every improvement for the lowest-literacy user improved the experience for everyone. Designing for the hardest case first is the most efficient path to universal quality.
04Test early, test wrong. My first berth-selection design felt perfect in Figma and failed completely in testing — users couldn't distinguish the coach layout from a seating chart. Fail fast, learn faster.
Next?

Like what you see?

Have a project
in mind?

designer.kj1411@gmail.com