Jetstar Mobile App Redesign to Reduce Cost to Serve

Role

Project leadership, project management, hands-on research and design

Duration

Phase 1 : 4.5 months

Organisation type

Agency

Context

Business goals for the app redesign
  • Reduce costs by increasing self service for the Manage My Booking experience
  • Update technology (API) to improve performance
  • Integrate tracking & analytics
  • Update the visual design
Redesigned Jetstar mobile app

Design approach

Define scope, requirements and business goals with the client

I created a story map to define scope based on a requirements document from the Business Analyst. There were 50+ epics present in the initial documentation.

The client and I decided to focus on the "Manage My Booking" theme first. It encompassed all tasks that occurred after a flight had been booked.

Previous research had recommended to focus on reducing the cost to serve for tasks like finding boarding passes and changing flights, which happened post-booking.

Desk research review to build context

To make sense of the landscape, I reviewed the existing research and mobile app. This included:
Existing contextual inquiry and landscape review insights
Complaints data
Live chat data
Stakeholder interviews with the client

Some key insights:
• A surprisingly large volume of customers use the contact centre to confirm their flights prior to travel (esp first-time flyers)
• Many customers turn up on the day of flight, unaware that they have missed a critical step prior to flight (e.g., check-in)
Complaints and live chat data that reveal the tasks customers struggled with the most.
This would inform changes to the information architecture and page layout hierarchy.
A strategy document that highlighted the need to increase self service for Manage My Booking.

Relationship building with client

I met with the Product Owner and Business Analyst each week to discuss timelines and progress made during the sprint, to download domain knowledge and to educate them on preferred ways of working. It was time allotted to build trust.

Project management & negotiation

I took on detailed project planning so that the UI designer and I could orchestrate multiple activities in sequence and at speed.
We shared the high level project plan with stakeholders in weekly stand ups with 2-3 weeks of buffer built in after our first 2 epics were scheduled to finish.

Map and wireframe a complex array of use cases

View a scrappy example of the wireframing space. It was a thinking space more than just a deliverable space. I used it to map out the array of use cases and attach questions for the client to answer in our 1:1s.
Some mobile app-based considerations when wireframing were:
• Apple Wallet integration for boarding passes
• Asking to use the device location when finding my gate
• Designing for ergonomics so that all primary buttons were located in the bottom half of the screens
• Push notifications for instructions for check-in and getting boarding passes.

Facilitate workshop to increase traffic to Manage My Booking

I ran an ideation workshop to uncover how we'd drive more traffic to Manage My Booking and away from the contact centre.

Research indicated that it was rare for customers to login to Manage My Booking unprompted.

An email and push comms journey was a clear winner from the workshop.

Usability and concept testing

Previous research had suggested to concept test a “trip hub” that focussed on creating the trip as an experience rather than a flight to catch. This looked like a timeline of all related activities to the flight e.g. airport transfers, hotel bookings, meals.

We also usability tested with customers who had low tech savviness and low familiarity with managing flights.
Ideation workshop comms journey sketch
Manage My Booking trip hub concept that tested with a high likelihood to recommend

Determine feasibility with developers

Our development partners came onboard about 2 months after we started design. We sense checked feasibility with them throughout the process.

One feasibility issue was not being able to pull in all of the trip add-on data from the current legacy system into the new API.
Data would either be missing or return strange formatting due to the time needed to migrate all data.  

80% of the essential data could still be surfaced for the customer e.g. some facilities from hotels would be missing but could be included in a fast follow release.

Outcomes

To make sense of the landscape, I reviewed the existing research and mobile app. This included:
Existing contextual inquiry and landscape review insights
Complaints data
Live chat data
Stakeholder interviews with the client

Some key insights:
• A surprisingly large volume of customers use the contact centre to confirm their flights prior to travel (esp first-time flyers)
• Many customers turn up on the day of flight, unaware that they have missed a critical step prior to flight (e.g., check-in)
• The Jetstar mobile app was launched and has an average 4.8 star rating on the App Store.

• Positive task completion scores for key tasks provided confidence to the reduce cost to serve.
Customers with low tech confidence and little booking experience could complete high usage tasks with ease using the new solution.

• Concept-testing for new Manage My Booking experience was well-received by research participants.  

• We hit all design milestones agreed to at the start of the initiative.
• The Jetstar mobile app was launched and has an average 4.8 star rating on the App Store.

There were positive task completion scores for key tasks using new information architecture and page hierarchy
Customers with low tech confidence and little manage my booking experience could complete high usage tasks with ease using the new solution.

An email and push comms journey was conceptualised to drive people to do self service tasks that had previously created the highest call centre traffic.
 
• Concept-testing for new Manage My Booking experience was well-received by research participants.
 
• We hit all design milestones agreed to at the start of the initiative.

Reflection

The team structure needed to include a Lead Designer who built relationships with key stakeholders while Senior Designer’s heads were down in delivery mode.

I would've delegated uncovering the current state mobile app to the Business Analyst to free up my time for stakeholder relationship building and a more focussed literature review.

Epics could’ve been grouped into focus areas and assigned a Lead each. That way, parallel streams of work could run to hit milestones more effectively and there’d be less pressure on a single team of designers to deliver everything.

I'd use analytics data for desktop as a proxy for some mobile app based decisions given the absence of mobile app analytics.
The team structure needed to include a Lead Designer who built relationships with key stakeholders while Senior Designer’s heads were down in delivery mode.

In a perfect world, I would've completed a much more detailed story map to scope all of the stories that came out during the scrappy wireframing phase.

Epics could’ve been grouped into focus areas and assigned a Lead each. That way, parallel streams of work could run to hit milestones more effectively and there’d be less pressure on a single team of designers to deliver everything.