Flight status
EXISTING PRODUCT REDESIGN
responsive web

A state-aware hierarchy redesign for WestJet's Flight Status.

A state-aware hierarchy redesign for WestJet's Flight Status.

WestJet Flight Status showed passengers what changed, not what that change meant.

A responsive redesign of WestJet's Flight Status experience with an objective to make flight changes clear, actionable, and responsive across devices. Not a visual rebrand.

TIMELINE

May 2026

2 weeks

role

Sole Product Designer

Self-initiated

Scope
Information hierarchy
Responsive web
STATE SYSTEM DESIGN
EXISTING BRAND DESIGN SYSTEM
TOOLS

Perplexity

Research

ChatGPT

Product Reasoning

Figma + MCP

Figma, FigJam, Figma Make

Design, Ideation

Claude Design
Claude Code

Design System + UI
Targeted refinement

TL ; DR

TL ; DR

WestJet's Flight Status shows passengers whether their flight is on time, delayed, or cancelled. The data is there. What's missing is interpretation: a clear signal of what changed, what matters now, and what to do next.

WestJet's Flight Status shows passengers whether their flight is on time, delayed, or cancelled. The data is there. What's missing is interpretation: a clear signal of what changed, what matters now, and what to do next.

This redesign treats Flight Status as a state-aware system rather than a static data display. The hierarchy shifts across states to match the passenger's actual need: confirmation when nothing changed, recalculation when times shift, and recovery guidance when the flight is gone.

This redesign treats Flight Status as a state-aware system rather than a static data display. The hierarchy shifts across states to match the passenger's actual need: confirmation when nothing changed, recalculation when times shift, and recovery guidance when the flight is gone.

the current experience

Flight Status page only reported status.
It didn't communicate change.

Flight Status page only reported status. It didn't communicate change.

Flight Status page only reported status. It didn't communicate change.

WestJet's existing Flight Status presents departure and arrival times, a status label, and gate information. But in case of a delay or a cancellation the experience doesn't shift to match. Revised and original times appear side by side without clear visual weight. The cancelled state looks structurally identical to on-time. Secondary information competes with what passengers need most.

WestJet's existing Flight Status presents departure and arrival times, a status label, and gate information. But in case of a delay or a cancellation the experience doesn't shift to match. Revised and original times appear side by side without clear visual weight. The cancelled state looks structurally identical to on-time. Secondary information competes with what passengers need most.

THE problem

WestJet Flight Status gives passengers the latest
flight details, but still leaves them to interpret what changed,
how it affects their journey, and what to do next.

WestJet Flight Status gives passengers the latest flight details, but still leaves them to interpret what changed, how it affects their journey,
and what to do next.

WestJet Flight Status gives passengers the latest flight details,
but still leaves them to interpret what changed, how it affects their journey, and what to do next.

the redesign

Same information, but better
hierarchy and disruption communication.

Same information, but better
hierarchy and disruption communication.

Meet Clairo: a safer layer between symptom search and care decisions.

The redesign restructures Flight Status around four levels of information:

Current state → What changed → Current flight details → Passenger action

The redesign doesn't introduce a new visual system. It uses WestJet's existing design language and re-organises the information around what passengers need next.

The redesign doesn't introduce a new visual system. It uses WestJet's existing design language and re-organises the information around what passengers need next.

What changes is structure: which information leads, what gets demoted, and what actions appear based on how disruptive the flight state actually is.

Flight Status: Search Entry

Start with the search that fits the task

After image
BEFORE
AFTER
Flight detail

Know what changed and what it means

After image
BEFORE
AFTER
state system

Confirmation, recalculation, recovery:
the design responds to what passengers need.

Confirmation, recalculation, recovery: the hierarchy shifts with each state change.

Confirmation, recalculation, recovery:
the design responds to what passengers need.

Flight Status has one job: surface what matters most right now. As the flight state changes, so does the passenger’s priority. I focused the redesign on three core states: On time, Delayed, and Cancelled.

On Time contentDelayed contentCancelled content
key product desicions

Three product calls that defined the redesign.

Meet Clairo: a safer layer between symptom search and care decisions.

Each decision below addresses a specific gap in the existing experience.

Each decision below addresses a specific gap in the existing experience.

DECISION 01 • Search Entry

Separating flight-number and airport search into two focused entry paths

The architecture emerged by narrowing Clairo's scope down to one core journey

Flight Status supports two distinct retrieval tasks: searching by flight number or browsing by airport.

The redesign separates the two entry modes into tabs inside a single search card. Each tab shows only the fields relevant to that task. A Recently Viewed panel surfaces repeat access without cluttering the primary search flow.

Focus vs. immediate access
Focus vs. immediate access

Tabs add one extra step if users enter through the wrong path, but remove competing fields and reduce unnecessary scanning increasing task focus.

original

Identified tension

Flight-number search and airport browsing stacked vertically -> no focused path.

redesign

Design rationale

  • Tabs keep each path focused, showing only the inputs needed for that task while reducing unnecessary scanning.

  • A lightweight Recently Viewed area supports repeat checks without competing with the primary search flow.

DECISION 02 • Plain-language delay summary

Communicating the change, not just the status

The architecture emerged by narrowing Clairo's scope down to one core journey

A Delayed label signals a problem, but not its magnitude or impact. Showing 20:39 beside Scheduled 20:15 still asks passengers to work out the difference themselves.

The redesign adds a plain-language summary above the times: "Departing 24 minutes late. Your arrival time has moved to 22:11." The raw values remain visible for verification.

System simplicity vs. immediate comprehension
System simplicity vs. immediate comprehension

A change summary must stay synchronized with schedule updates. In return, passengers understand the delay and its downstream impact without interpreting raw timestamps.

original

Identified tension

Labels such as Delayed establish the state but do not explain the difference between the passenger's expectation and the current reality.

redesign

Design rationale

  • Passengers no longer have to mentally compare operational values before understanding their situation.

  • The interface performs the comparison and lets the passenger focus on its consequence.

DECISION 03 • Cancelled State

When a flight is cancelled, the panel's job flips from monitoring to recovery.

The architecture emerged by narrowing Clairo's scope down to one core journey

On-time and delayed states help passengers monitor a journey. Cancellation changes the task: the priority becomes understanding what happened and where to go next.

The redesign moves Manage Trips and Advisories forward, while the original schedule remains as muted reference. Gate and terminal details recede because they no longer help the passenger act.

guidance vs. product boundary

Flight Status can guide recovery without claiming ownership of rebooking, refunds, or eligibility. It points passengers to trusted recovery surfaces instead.

redesign

Design rationale

  • Once a flight is cancelled, monitoring is no longer the user’s primary task; finding a credible next step is.

  • Manage Trips and Advisories provide a clear handoff without implying recovery actions Flight Status cannot determine.

RESPONSIVE ADAPTATION

Critical flight updates need to stay accessible on the go.

Minimising critical product risks in healthcare AI
before development.

Flight Status is inherently an on-the-go utility. The redesign extends the same core status, timing, and action cues to mobile so critical updates remain easy to check throughout the travel day.

Flight Status is inherently an on-the-go utility. The redesign extends the same core status, timing, and action cues to mobile so critical updates remain easy to check throughout the travel day.

intentded outcomes

What success would look like

Minimising critical product risks in healthcare AI
before development.

Success could be measured against these factors:

Success could be measured against these factors:

Status comprehension
Status comprehension

Can passengers correctly identify the flight's current state?

Can passengers correctly identify the flight's current state?

Measures whether the current flight state is immediately clear without passengers having to interpret supporting details.

Measures whether the current flight state is immediately clear without passengers having to interpret supporting details.

Change comprehension
Change comprehension

Can they correctly explain what changed?

Can they correctly explain what changed?

Tests whether passengers understand what changed from the original schedule and how that change affects their journey.

Tests whether passengers understand what changed from the original schedule and how that change affects their journey.

Time taken

How quickly can they find critical information?

How quickly can they find critical information?

Measures how quickly passengers can locate the critical information they need, especially during delays or other disruptions.

Measures how quickly passengers can locate the critical information they need, especially during delays or other disruptions.

Next-action clarity
Next-action clarity

Can passengers identify the appropriate next step?

Can passengers identify the appropriate next step?

Tests whether passengers can identify what to do next when the flight state requires action, such as a cancellation.

Tests whether passengers can identify what to do next when the flight state requires action, such as a cancellation.

reflections

Here's what I would validate next.

This redesign reinforced that information hierarchy in a travel product cannot remain static when the passenger's situation changes.

The most useful intervention was not adding more flight information, but determining which information deserves attention at each moment.

The most useful intervention was not adding more flight information, but determining which information deserves attention at each moment.

Before shipping, I would validate three areas more deeply:

Operational coverage

Whether the proposed hierarchy works across additional real WestJet states beyond the three states represented.

Data availability

Which change comparisons and contextual actions can reliably be supported by WestJet's existing systems.

Real travel conditions

The interface alone could not prove medical accuracy or safety. The challenge was positioning Clairo as useful without implying clinical validation or presenting it as a replacement for professional care.

Let’s build thoughtful products together.

© 2026 Soumya Peruri

Let’s build thoughtful products together.

© 2026 Soumya Peruri

Let’s build thoughtful
products together.

© 2026 Soumya Peruri