Zahid Al Muhasibi
Digital Product Research & Design
Research
Mobile
Designing for Flight Disruptions
Designing mobile experiences that reduce confusion and support passengers during delays, cancellations, and unexpected schedule changes.
Designing mobile experiences that reduce confusion and support passengers during delays, cancellations, and unexpected schedule changes.
01 Context & Challenge
Context
Flight delays and cancellations are part of flying. Most airline apps already show status updates, but many stop there. They tell users what changed, without helping them understand what to do next.
In this case study, I explored how an airline app could respond to flight delays with a more human-centered approach, not only informing users what has changed, but also guiding them toward what to do next without increasing stress or confusion.
The focus is a critical moment: when users open the app and realize their flight won’t leave as planned.
The Problem
As a result, users often:
Struggle to understand the real impact of the delay
Feel unsure about which information matters most
And are forced to make decisions under pressure
Instead of acting as a support system, the app unintentionally becomes an additional source of stress
When a delay happens, users aren’t exploring the app. They’re trying to regain control. They’re asking simple questions:
What changed?
How bad is it?
What should I do right now?
The core problem is not the lack of features, but the lack of clarity and timing in how information and actions are presented.
Design Lens
As a design foundation, I referenced a principle from Don Norman in The Design of Everyday Things:
Good design is invisible; it fulfills needs so seamlessly that only bad design stands out.
In disruption moments, design shouldn’t demand attention. It should lower cognitive load, feel calm, and quietly point users in the right direction.
01 Context & Challenge
Context
Flight delays and cancellations are part of flying. Most airline apps already show status updates, but many stop there. They tell users what changed, without helping them understand what to do next.
In this case study, I explored how an airline app could respond to flight delays with a more human-centered approach, not only informing users what has changed, but also guiding them toward what to do next without increasing stress or confusion.
The focus is a critical moment: when users open the app and realize their flight won’t leave as planned.
The Problem
As a result, users often:
Struggle to understand the real impact of the delay
Feel unsure about which information matters most
And are forced to make decisions under pressure
Instead of acting as a support system, the app unintentionally becomes an additional source of stress
When a delay happens, users aren’t exploring the app. They’re trying to regain control. They’re asking simple questions:
What changed?
How bad is it?
What should I do right now?
The core problem is not the lack of features, but the lack of clarity and timing in how information and actions are presented.
Design Lens
As a design foundation, I referenced a principle from Don Norman in The Design of Everyday Things:
Good design is invisible; it fulfills needs so seamlessly that only bad design stands out.
In disruption moments, design shouldn’t demand attention. It should lower cognitive load, feel calm, and quietly point users in the right direction.
01 Context & Challenge
Context
Flight delays and cancellations are part of flying. Most airline apps already show status updates, but many stop there. They tell users what changed, without helping them understand what to do next.
In this case study, I explored how an airline app could respond to flight delays with a more human-centered approach, not only informing users what has changed, but also guiding them toward what to do next without increasing stress or confusion.
The focus is a critical moment: when users open the app and realize their flight won’t leave as planned.
The Problem
As a result, users often:
Struggle to understand the real impact of the delay
Feel unsure about which information matters most
And are forced to make decisions under pressure
Instead of acting as a support system, the app unintentionally becomes an additional source of stress
When a delay happens, users aren’t exploring the app. They’re trying to regain control. They’re asking simple questions:
What changed?
How bad is it?
What should I do right now?
The core problem is not the lack of features, but the lack of clarity and timing in how information and actions are presented.
Design Lens
As a design foundation, I referenced a principle from Don Norman in The Design of Everyday Things:
Good design is invisible; it fulfills needs so seamlessly that only bad design stands out.
In disruption moments, design shouldn’t demand attention. It should lower cognitive load, feel calm, and quietly point users in the right direction.
01 Context & Challenge
Context
Flight delays and cancellations are part of flying. Most airline apps already show status updates, but many stop there. They tell users what changed, without helping them understand what to do next.
In this case study, I explored how an airline app could respond to flight delays with a more human-centered approach, not only informing users what has changed, but also guiding them toward what to do next without increasing stress or confusion.
The focus is a critical moment: when users open the app and realize their flight won’t leave as planned.
The Problem
As a result, users often:
Struggle to understand the real impact of the delay
Feel unsure about which information matters most
And are forced to make decisions under pressure
Instead of acting as a support system, the app unintentionally becomes an additional source of stress
When a delay happens, users aren’t exploring the app. They’re trying to regain control. They’re asking simple questions:
What changed?
How bad is it?
What should I do right now?
The core problem is not the lack of features, but the lack of clarity and timing in how information and actions are presented.
Design Lens
As a design foundation, I referenced a principle from Don Norman in The Design of Everyday Things:
Good design is invisible; it fulfills needs so seamlessly that only bad design stands out.
In disruption moments, design shouldn’t demand attention. It should lower cognitive load, feel calm, and quietly point users in the right direction.
02 Problem Framing & Analysis
Key Insight
Flight delays aren’t just scheduling problems. They’re emotional ones
When users encounter a delay, their primary concern is rarely why it happened.
What they need most is clarity, reassurance, and a clear sense of what they can do next.
In moments of disruption, users value guidance over information, and certainty over completeness.
Why This Matters?
Most airline apps treat delay states as a variation of normal states:
The same layout
The same hierarchy
With only a status label changed
If the interface doesn’t answer these questions immediately, users feel lost, even if the information technically exists.
02 Problem Framing & Analysis
Key Insight
Flight delays aren’t just scheduling problems. They’re emotional ones
When users encounter a delay, their primary concern is rarely why it happened.
What they need most is clarity, reassurance, and a clear sense of what they can do next.
In moments of disruption, users value guidance over information, and certainty over completeness.
Why This Matters?
Most airline apps treat delay states as a variation of normal states:
The same layout
The same hierarchy
With only a status label changed
If the interface doesn’t answer these questions immediately, users feel lost, even if the information technically exists.
02 Problem Framing & Analysis
Key Insight
Flight delays aren’t just scheduling problems. They’re emotional ones
When users encounter a delay, their primary concern is rarely why it happened.
What they need most is clarity, reassurance, and a clear sense of what they can do next.
In moments of disruption, users value guidance over information, and certainty over completeness.
Why This Matters?
Most airline apps treat delay states as a variation of normal states:
The same layout
The same hierarchy
With only a status label changed
If the interface doesn’t answer these questions immediately, users feel lost, even if the information technically exists.
02 Problem Framing & Analysis
03 Executing the Vision
Design Implementation
The following concepts explore how an airline experience can adapt to different levels of disruption.
Rather than treating delays, schedule changes, and cancellations as isolated scenarios, the design approaches them as a progression of uncertainty.
As disruption increases, the interface gradually shifts its role:
From providing awareness
To supporting evaluation
To enabling resolution
Each case is designed around a different user mindset, ensuring that information, hierarchy, and actions evolve alongside the user's needs.
Case 1: Flight Delayed (Short Delay)
A short delay is rarely a decision-making moment.
Users are not looking for alternatives yet. They are trying to understand whether the change is significant enough to affect their plans.
The design therefore prioritizes awareness over action, helping users acknowledge the delay without feeling that something has gone seriously wrong.
Implementation Decisions:
Delay is acknowledged immediately
The updated status appears directly within the primary flight card, ensuring users recognize the change as soon as they open the application. This eliminates unnecessary scanning and reduces the time required to understand what happened.Core flight information remains dominant
Route, destination, and departure details retain visual prominence. The delay is presented as an adjustment to the journey rather than a disruption that replaces the journey itself.Secondary content is intentionally de-emphasized
Promotional and non-essential content remains accessible but visually subdued. This preserves context while preventing unnecessary competition for attention.No premature actions are introduced
Because the delay remains relatively minor, the interface avoids presenting recovery options that may not yet be relevant. Users are not encouraged to solve a problem that may resolve itself.Calm microcopy reinforces confidence
Supporting messages acknowledge the delay while reinforcing that the flight remains active. The tone focuses on reassurance rather than urgency.
Design Rationale
When disruptions are still manageable, excessive information and early decision prompts can increase stress rather than reduce it.
The goal of this screen is not to encourage action. It is to restore orientation.
By maintaining familiar flight context and limiting unnecessary choices, the experience allows users to remain confident while waiting for further updates.
“Good design is actually a lot harder to notice than poor design, in part because good designs fit our needs so well that the design is invisible.” — Don Norman
Case 2: Helping Users Evaluate Schedule Changes
Unlike a short delay, a schedule update introduces a meaningful change to the user's plan.
At this point, users move beyond awareness and begin evaluating consequences.
Their primary questions become:
What changed?
How different is it?
Do I need to do something?
The design shifts from simply informing users toward helping them compare and assess impact.
Implementation Decisions:
Change is communicated without alarm
The updated status uses neutral language rather than warning-oriented terminology. This helps frame the event as a change requiring evaluation rather than a failure requiring panic.Comparison becomes the primary interaction
The original and updated schedules are presented together inside a dedicated comparison view. Users can immediately understand the difference without relying on memory.The new schedule receives visual emphasis
The updated itinerary is highlighted while the previous schedule remains visible for reference. This preserves context while clearly indicating the recommended path forward.Impact is translated into understandable terms
Rather than requiring users to calculate differences themselves, the interface explicitly communicates the estimated delay. The system performs the interpretation work on behalf of the user.Actions are presented as equally valid options
Users can either accept the updated schedule or explore alternatives. Neither action is visually framed as the "correct" choice.
Design Rationale
Most schedule changes are not difficult because users lack information.
They become difficult because users must interpret information before they can decide.
By transforming raw schedule updates into a clear comparison experience, the interface reduces cognitive effort and supports confident decision-making.
Users should spend their mental energy deciding what they want to do, not figuring out what changed.
Case 3: Guiding Resolution During Flight Cancellation
A cancellation represents a fundamentally different state from a delay or schedule adjustment.
The uncertainty phase is over.
Users no longer need awareness or evaluation. They need a path forward.
The design therefore shifts its focus toward resolution, helping users quickly understand available options and regain control.
Implementation Decisions:
Cancellation is communicated with clarity
The flight status clearly indicates that the journey can no longer proceed as planned.
The language is direct and unambiguous, eliminating uncertainty about the current state.Eligibility information is surfaced immediately
Refund eligibility and reimbursement details are presented directly within the disruption flow.
Users do not need to search through policies or support pages to understand their position.Alternative expectations are managed honestly
When no suitable replacement flight is available, the interface communicates this directly.The system avoids creating false optimism or forcing users through unnecessary comparison flows.
Recovery actions become the primary focus
The experience is narrowed to two clear outcomes:Change Flight
Get Refund
Everything else becomes secondary.
Financial implications are made visible
Relevant refund amounts and compensation details are surfaced within the same decision space.
This reduces uncertainty and helps users make informed choices faster.
Design Rationale
In cancellation scenarios, users are not looking for flexibility.
They are looking for certainty.
The most effective experience is not the one that offers the most options, but the one that makes the next step unmistakably clear.
By focusing on clarity, eligibility, and resolution, the interface helps users move from disruption to recovery with minimal friction.
People can tolerate bad outcomes more easily than uncertain outcomes. What increases anxiety is not knowing what happens next.
03 Executing the Vision
Design Implementation
The following concepts explore how an airline experience can adapt to different levels of disruption.
Rather than treating delays, schedule changes, and cancellations as isolated scenarios, the design approaches them as a progression of uncertainty.
As disruption increases, the interface gradually shifts its role:
From providing awareness
To supporting evaluation
To enabling resolution
Each case is designed around a different user mindset, ensuring that information, hierarchy, and actions evolve alongside the user's needs.
Case 1: Flight Delayed (Short Delay)
A short delay is rarely a decision-making moment.
Users are not looking for alternatives yet. They are trying to understand whether the change is significant enough to affect their plans.
The design therefore prioritizes awareness over action, helping users acknowledge the delay without feeling that something has gone seriously wrong.
Implementation Decisions:
Delay is acknowledged immediately
The updated status appears directly within the primary flight card, ensuring users recognize the change as soon as they open the application. This eliminates unnecessary scanning and reduces the time required to understand what happened.Core flight information remains dominant
Route, destination, and departure details retain visual prominence. The delay is presented as an adjustment to the journey rather than a disruption that replaces the journey itself.Secondary content is intentionally de-emphasized
Promotional and non-essential content remains accessible but visually subdued. This preserves context while preventing unnecessary competition for attention.No premature actions are introduced
Because the delay remains relatively minor, the interface avoids presenting recovery options that may not yet be relevant. Users are not encouraged to solve a problem that may resolve itself.Calm microcopy reinforces confidence
Supporting messages acknowledge the delay while reinforcing that the flight remains active. The tone focuses on reassurance rather than urgency.
Design Rationale
When disruptions are still manageable, excessive information and early decision prompts can increase stress rather than reduce it.
The goal of this screen is not to encourage action. It is to restore orientation.
By maintaining familiar flight context and limiting unnecessary choices, the experience allows users to remain confident while waiting for further updates.
“Good design is actually a lot harder to notice than poor design, in part because good designs fit our needs so well that the design is invisible.” — Don Norman
Case 2: Helping Users Evaluate Schedule Changes
Unlike a short delay, a schedule update introduces a meaningful change to the user's plan.
At this point, users move beyond awareness and begin evaluating consequences.
Their primary questions become:
What changed?
How different is it?
Do I need to do something?
The design shifts from simply informing users toward helping them compare and assess impact.
Implementation Decisions:
Change is communicated without alarm
The updated status uses neutral language rather than warning-oriented terminology. This helps frame the event as a change requiring evaluation rather than a failure requiring panic.Comparison becomes the primary interaction
The original and updated schedules are presented together inside a dedicated comparison view. Users can immediately understand the difference without relying on memory.The new schedule receives visual emphasis
The updated itinerary is highlighted while the previous schedule remains visible for reference. This preserves context while clearly indicating the recommended path forward.Impact is translated into understandable terms
Rather than requiring users to calculate differences themselves, the interface explicitly communicates the estimated delay. The system performs the interpretation work on behalf of the user.Actions are presented as equally valid options
Users can either accept the updated schedule or explore alternatives. Neither action is visually framed as the "correct" choice.
Design Rationale
Most schedule changes are not difficult because users lack information.
They become difficult because users must interpret information before they can decide.
By transforming raw schedule updates into a clear comparison experience, the interface reduces cognitive effort and supports confident decision-making.
Users should spend their mental energy deciding what they want to do, not figuring out what changed.
Case 3: Guiding Resolution During Flight Cancellation
A cancellation represents a fundamentally different state from a delay or schedule adjustment.
The uncertainty phase is over.
Users no longer need awareness or evaluation. They need a path forward.
The design therefore shifts its focus toward resolution, helping users quickly understand available options and regain control.
Implementation Decisions:
Cancellation is communicated with clarity
The flight status clearly indicates that the journey can no longer proceed as planned.
The language is direct and unambiguous, eliminating uncertainty about the current state.Eligibility information is surfaced immediately
Refund eligibility and reimbursement details are presented directly within the disruption flow.
Users do not need to search through policies or support pages to understand their position.Alternative expectations are managed honestly
When no suitable replacement flight is available, the interface communicates this directly.The system avoids creating false optimism or forcing users through unnecessary comparison flows.
Recovery actions become the primary focus
The experience is narrowed to two clear outcomes:Change Flight
Get Refund
Everything else becomes secondary.
Financial implications are made visible
Relevant refund amounts and compensation details are surfaced within the same decision space.
This reduces uncertainty and helps users make informed choices faster.
Design Rationale
In cancellation scenarios, users are not looking for flexibility.
They are looking for certainty.
The most effective experience is not the one that offers the most options, but the one that makes the next step unmistakably clear.
By focusing on clarity, eligibility, and resolution, the interface helps users move from disruption to recovery with minimal friction.
People can tolerate bad outcomes more easily than uncertain outcomes. What increases anxiety is not knowing what happens next.
03 Executing the Vision
Design Implementation
The following concepts explore how an airline experience can adapt to different levels of disruption.
Rather than treating delays, schedule changes, and cancellations as isolated scenarios, the design approaches them as a progression of uncertainty.
As disruption increases, the interface gradually shifts its role:
From providing awareness
To supporting evaluation
To enabling resolution
Each case is designed around a different user mindset, ensuring that information, hierarchy, and actions evolve alongside the user's needs.
Case 1: Flight Delayed (Short Delay)
A short delay is rarely a decision-making moment.
Users are not looking for alternatives yet. They are trying to understand whether the change is significant enough to affect their plans.
The design therefore prioritizes awareness over action, helping users acknowledge the delay without feeling that something has gone seriously wrong.
Implementation Decisions:
Delay is acknowledged immediately
The updated status appears directly within the primary flight card, ensuring users recognize the change as soon as they open the application. This eliminates unnecessary scanning and reduces the time required to understand what happened.Core flight information remains dominant
Route, destination, and departure details retain visual prominence. The delay is presented as an adjustment to the journey rather than a disruption that replaces the journey itself.Secondary content is intentionally de-emphasized
Promotional and non-essential content remains accessible but visually subdued. This preserves context while preventing unnecessary competition for attention.No premature actions are introduced
Because the delay remains relatively minor, the interface avoids presenting recovery options that may not yet be relevant. Users are not encouraged to solve a problem that may resolve itself.Calm microcopy reinforces confidence
Supporting messages acknowledge the delay while reinforcing that the flight remains active. The tone focuses on reassurance rather than urgency.
Design Rationale
When disruptions are still manageable, excessive information and early decision prompts can increase stress rather than reduce it.
The goal of this screen is not to encourage action. It is to restore orientation.
By maintaining familiar flight context and limiting unnecessary choices, the experience allows users to remain confident while waiting for further updates.
“Good design is actually a lot harder to notice than poor design, in part because good designs fit our needs so well that the design is invisible.” — Don Norman
Case 2: Helping Users Evaluate Schedule Changes
Unlike a short delay, a schedule update introduces a meaningful change to the user's plan.
At this point, users move beyond awareness and begin evaluating consequences.
Their primary questions become:
What changed?
How different is it?
Do I need to do something?
The design shifts from simply informing users toward helping them compare and assess impact.
Implementation Decisions:
Change is communicated without alarm
The updated status uses neutral language rather than warning-oriented terminology. This helps frame the event as a change requiring evaluation rather than a failure requiring panic.Comparison becomes the primary interaction
The original and updated schedules are presented together inside a dedicated comparison view. Users can immediately understand the difference without relying on memory.The new schedule receives visual emphasis
The updated itinerary is highlighted while the previous schedule remains visible for reference. This preserves context while clearly indicating the recommended path forward.Impact is translated into understandable terms
Rather than requiring users to calculate differences themselves, the interface explicitly communicates the estimated delay. The system performs the interpretation work on behalf of the user.Actions are presented as equally valid options
Users can either accept the updated schedule or explore alternatives. Neither action is visually framed as the "correct" choice.
Design Rationale
Most schedule changes are not difficult because users lack information.
They become difficult because users must interpret information before they can decide.
By transforming raw schedule updates into a clear comparison experience, the interface reduces cognitive effort and supports confident decision-making.
Users should spend their mental energy deciding what they want to do, not figuring out what changed.
Case 3: Guiding Resolution During Flight Cancellation
A cancellation represents a fundamentally different state from a delay or schedule adjustment.
The uncertainty phase is over.
Users no longer need awareness or evaluation. They need a path forward.
The design therefore shifts its focus toward resolution, helping users quickly understand available options and regain control.
Implementation Decisions:
Cancellation is communicated with clarity
The flight status clearly indicates that the journey can no longer proceed as planned.
The language is direct and unambiguous, eliminating uncertainty about the current state.Eligibility information is surfaced immediately
Refund eligibility and reimbursement details are presented directly within the disruption flow.
Users do not need to search through policies or support pages to understand their position.Alternative expectations are managed honestly
When no suitable replacement flight is available, the interface communicates this directly.The system avoids creating false optimism or forcing users through unnecessary comparison flows.
Recovery actions become the primary focus
The experience is narrowed to two clear outcomes:Change Flight
Get Refund
Everything else becomes secondary.
Financial implications are made visible
Relevant refund amounts and compensation details are surfaced within the same decision space.
This reduces uncertainty and helps users make informed choices faster.
Design Rationale
In cancellation scenarios, users are not looking for flexibility.
They are looking for certainty.
The most effective experience is not the one that offers the most options, but the one that makes the next step unmistakably clear.
By focusing on clarity, eligibility, and resolution, the interface helps users move from disruption to recovery with minimal friction.
People can tolerate bad outcomes more easily than uncertain outcomes. What increases anxiety is not knowing what happens next.
03 Executing the Vision
Design Implementation
The following concepts explore how an airline experience can adapt to different levels of disruption.
Rather than treating delays, schedule changes, and cancellations as isolated scenarios, the design approaches them as a progression of uncertainty.
As disruption increases, the interface gradually shifts its role:
From providing awareness
To supporting evaluation
To enabling resolution
Each case is designed around a different user mindset, ensuring that information, hierarchy, and actions evolve alongside the user's needs.
Case 1: Flight Delayed (Short Delay)
A short delay is rarely a decision-making moment.
Users are not looking for alternatives yet. They are trying to understand whether the change is significant enough to affect their plans.
The design therefore prioritizes awareness over action, helping users acknowledge the delay without feeling that something has gone seriously wrong.
Implementation Decisions:
Delay is acknowledged immediately
The updated status appears directly within the primary flight card, ensuring users recognize the change as soon as they open the application. This eliminates unnecessary scanning and reduces the time required to understand what happened.Core flight information remains dominant
Route, destination, and departure details retain visual prominence. The delay is presented as an adjustment to the journey rather than a disruption that replaces the journey itself.Secondary content is intentionally de-emphasized
Promotional and non-essential content remains accessible but visually subdued. This preserves context while preventing unnecessary competition for attention.No premature actions are introduced
Because the delay remains relatively minor, the interface avoids presenting recovery options that may not yet be relevant. Users are not encouraged to solve a problem that may resolve itself.Calm microcopy reinforces confidence
Supporting messages acknowledge the delay while reinforcing that the flight remains active. The tone focuses on reassurance rather than urgency.
Design Rationale
When disruptions are still manageable, excessive information and early decision prompts can increase stress rather than reduce it.
The goal of this screen is not to encourage action. It is to restore orientation.
By maintaining familiar flight context and limiting unnecessary choices, the experience allows users to remain confident while waiting for further updates.
“Good design is actually a lot harder to notice than poor design, in part because good designs fit our needs so well that the design is invisible.” — Don Norman
Case 2: Helping Users Evaluate Schedule Changes
Unlike a short delay, a schedule update introduces a meaningful change to the user's plan.
At this point, users move beyond awareness and begin evaluating consequences.
Their primary questions become:
What changed?
How different is it?
Do I need to do something?
The design shifts from simply informing users toward helping them compare and assess impact.
Implementation Decisions:
Change is communicated without alarm
The updated status uses neutral language rather than warning-oriented terminology. This helps frame the event as a change requiring evaluation rather than a failure requiring panic.Comparison becomes the primary interaction
The original and updated schedules are presented together inside a dedicated comparison view. Users can immediately understand the difference without relying on memory.The new schedule receives visual emphasis
The updated itinerary is highlighted while the previous schedule remains visible for reference. This preserves context while clearly indicating the recommended path forward.Impact is translated into understandable terms
Rather than requiring users to calculate differences themselves, the interface explicitly communicates the estimated delay. The system performs the interpretation work on behalf of the user.Actions are presented as equally valid options
Users can either accept the updated schedule or explore alternatives. Neither action is visually framed as the "correct" choice.
Design Rationale
Most schedule changes are not difficult because users lack information.
They become difficult because users must interpret information before they can decide.
By transforming raw schedule updates into a clear comparison experience, the interface reduces cognitive effort and supports confident decision-making.
Users should spend their mental energy deciding what they want to do, not figuring out what changed.
Case 3: Guiding Resolution During Flight Cancellation
A cancellation represents a fundamentally different state from a delay or schedule adjustment.
The uncertainty phase is over.
Users no longer need awareness or evaluation. They need a path forward.
The design therefore shifts its focus toward resolution, helping users quickly understand available options and regain control.
Implementation Decisions:
Cancellation is communicated with clarity
The flight status clearly indicates that the journey can no longer proceed as planned.
The language is direct and unambiguous, eliminating uncertainty about the current state.Eligibility information is surfaced immediately
Refund eligibility and reimbursement details are presented directly within the disruption flow.
Users do not need to search through policies or support pages to understand their position.Alternative expectations are managed honestly
When no suitable replacement flight is available, the interface communicates this directly.The system avoids creating false optimism or forcing users through unnecessary comparison flows.
Recovery actions become the primary focus
The experience is narrowed to two clear outcomes:Change Flight
Get Refund
Everything else becomes secondary.
Financial implications are made visible
Relevant refund amounts and compensation details are surfaced within the same decision space.
This reduces uncertainty and helps users make informed choices faster.
Design Rationale
In cancellation scenarios, users are not looking for flexibility.
They are looking for certainty.
The most effective experience is not the one that offers the most options, but the one that makes the next step unmistakably clear.
By focusing on clarity, eligibility, and resolution, the interface helps users move from disruption to recovery with minimal friction.
People can tolerate bad outcomes more easily than uncertain outcomes. What increases anxiety is not knowing what happens next.