Find consistency in flight information (workshop)

[leeejune]

General Support Request

There are inconsistencies about how flight details are displayed across the guest journey and across platforms:

• Tail image
• Flight number
• Departure/arrival time
• Departure/arrive city
• Airport name
• Airline name
• Stops
• Flight status

Possible Solution

We have fully documented these inconsistencies, so progress toward common solutions are in the works.

THE PLAN

1. Identify inconsistencies (complete)
2. Define information needed when displaying a flight
3. Educate all designers on how flight information should be displayed
4. Collaborate with product teams to ensure consistency needs are planned for and prioritized in efforts moving forward
5. Guidelines can either be in text form or exist as Auro components (e.g. flight card).

Context

There are a number of reasons for these inconsistencies.

Up until recently... Product teams have worked in silos and did not have opportunities to share their work across other teams to ensure consistency.

Currently... Making enhancements across product and platforms to bring consistency tends to be a lower priority or is deprioritized to meet deadlines.

Today... Many team members are new and are still learning about their product areas, beginning to discover inconsistencies across experiences.

The Auro team, having a developing design system, needed to prioritize designing components and tools over creating guidelines for smaller details. There are Auro components that can be leveraged for consistency, but we need to develop additional patterns to cover all use cases.

[blackfalcon]

@leeejune this has to do with the auro-flight element, right?

[leeejune]

@blackfalcon Yep!