The setup
British Airways need no introduction, but it's worth understanding the team setup to appreciate the challenges involved in creating a successful product for the world renowned airline.
There were three parties involved. BA, Ogilvy One and my team at Imano. Ogilvy One were the client contact and had creative oversight, BA was growing a mobile specialist UX team as the project was ongoing. My team at Imano were involved to spearhead the mobile UX & design.
The front & back end build would be handled by the BA team. In some ways this was an advantage, but it did create the challenge that our team needed to have a thorough understanding of the limitations and potential of the system.
With three separate design teams involved it was very important that my team members were supported in the right way. They needed to be able to take ownership of the project enough to be able to push the concepts, but have the maturity to understand that key decision makers would not be within the Imano team.
The challenge
To re-invent & improve BA's mobile proposition.
The product had to aim high as development times were long and the features & execution of the product had to make headlines when it launched 9 months from the concept phase.
Back end limitations were high. This is because stability is incredibly important for an Airline website or application, and development for these systems are time consuming and expensive.
In short: to Create a news worthy mobile product suite without causing major impacts to the back end systems for launch up to a year from inception.
Consultations & project strategy