Bombardier

A phenomenal 8-month experience that involved the creation, development, and testing of a brand-new application geared towards pilots of Bombardier Aircraft for both mobile and tablet.

Leveraging my user experience knowledge, while learning a brand new problem space, I had the opportunity to gain valuable professional experience and prepare to launch the MVP of an application that was ideated from scratch.

Tools Used:

Figman Icon
Jira IconConfluence Icon

Problem Space

Pilots lead fast, action-packed lives, and find themselves navigating potentially high-stakes situations on a daily basis. Assessing their aircraft's performance, figuring out flight plans, and ensuring all passengers are taken care of are just some of the challenges they face, and pilots flying Bombardier business jets are no exception. It's only obvious that there are countless applications geared towards making their lives just a little bit easier, and so our team at Bombardier was tasked with creating an app that provided value and unique insights to the pilots, making use of data that only Bombardier can provide.

Journey Map

As this application is yet to be released, there are limited details I can provide in my portfolio. Instead, I will be illustrating and describing the journey that I (and the rest of the team) took to make an application that is yet to be released as an MVP for validating our hypotheses.

I look forward to taking you along on this journey with me!
Journey Map Illustrating Vladislava's Journey at Bombardier

Tap the tabs to learn more about this journey:

Ideation

While we had a breadth of engineering data to draw on, user insights were more challenging to find, and given a short timeline, might prove even more challenging to collect. We also had to conduct an industry analysis on competitor applications - while we were looking to create something unique, we obviously had to match industry expectations, but provide value by exceeding them and supplementing them with exclusive Bombardier information.
This challenge however, took several attempts to address. While it's well known that iteration is at the heart of UX, it took three Value Propositions before a version of the application was green-lit for development. Furthermore, we weren't able to conduct any user research due to external constraints and had to rely on research that had already been conducted to inform our work. While it's not necessarily a best practice, the realities of a situation are what they are.

Third Time's the Charm

This challenge however, took several attempts to address. While it's well known that iteration is at the heart of UX, it took three different Value Propositions before a version of the application was green-lit for development. Furthermore, we weren't able to conduct any user research due to external constraints and had to rely on research that had already been conducted to inform our work. While it's not necessarily a best practice, the realities of a situation are what they are.
After toying around with different ideas, we settled on one that we would be able to develop into a solution and validate with an MVP release.

Prototyping

Despite the fact that we created wireframes for each stage of ideation, we finally had a strategy to guide some high-fi designs for prototyping. Our prototypes would serve dual purposes at this stage: 1. Guide the development team in how to realize the application we were preparing in tandem with the user stories articulated in Jira; and 2. Prepare a prototype that can be tested with our target users.

Distributing responsibilities, the other UX Designer on the team and I would separate tasks, then come together and discuss them, following an iterative practice of designing the wireframes with regular design reviews with the rest of the team.

Development

Working with developers, we began to prepare an application that was ready for an MVP launch. We collaborated throughout the development process to ensure that design and functionality were aligned, and that the user experience is seamless and intuitive. This involved a lot of communication and feedback between our team and the developers, and a lot of redesign.

As we worked together to find solutions, we found that that balance user needs with technical constraints. By working closely with the development team, we could ensure that the app not only meet the requirements, but also exceeded user expectations and delivered a delightful experience.

User Stories

To make sure we were on the same page, we'd ensure to support the Business Analysts and Product Managers in the refinement of user stories. Touching base several times a week, the user stories would get articulated to best reflect the UX that the other designer and I had prepared.

Usability Testing

There was no way of telling how good our designs were without user testing. At this point, with the prototypes that we had prepared, we deployed a survey, reaching several dozen respondents, from which we were able to engage 3 pilots.

With these insights we were able to refine the user experience of the application before MVP. We discovered that we should rework our terminology, which also helped us get a better sense of our user persona.

Though we didn't have to opportunity to test with many users, Nielsen and Landauer found you only need 5 to find most usability problems, and really, in a way we were past halfway there.

Interviewing

As we reached the close of my internship, I had the opportunity to participate in the interviews for selecting the new candidate. While I was sad for it to come to a close, this was a valuable opportunity to practice my interview skills on the other side of the process. Every interviewee was so capable, it was a matter of selecting from the best, instead of selecting the best. I certainly felt that the pressure was on for me as I would look for my next job 😅.


Final Stretch

With about a month out from the MVP, my internship came to a close. The pressure was on to refine, refine, refine all the design so that it was an app that was ready for a couple test users to onboard. I helped prepare an onboarding flow, including the illustration pictured on the left and left the rest of the app's launch in the (beyond) capable hands of the rest of my team.
Illustration of two pilots created by Vladislava Gorchkova

Lessons Learned

Insights From Everywhere

At the very beginning, as we ideated the app, the entire team would gather for workshops, and everyone's opinion and insights were encouraged. Though we all had different roles, and different professional backgrounds, this intermixing of all of our ideas helped make the application the best we could, and thought it hasn't launched yet, I know it's the better for it. The value of everyone participating in this process, and ensuring that all kinds of insights inform the way I design is something I will take away from this.

Communication Abound

Of course I was already familiar with Figma, but designing so regularly, and ensuring that our work was organized and intelligible for all stakeholders (the product owner, the product manager, the business analysts, the developers, and so on) was critical. Making sure that we had rigorous documentation was paramount, and the preparation of a (albeit rudimentary) design system that could evolve as the application does was important to the success of internal team communication, this helped us be on the same page at any given moment.

My Contribution Counts

As many students in this day and age will tell you, imposter syndrome can be a powerful force, leading one to undervalue their work and contributions. However, with the freedom to act as a full designer, even though on paper I was an intern, lead me to develop my skills, and feel proud of my contributions. This opportunity to grow and to come into my own as a designer has been instrumental to my confidence, and has renewed my desire to go into UX.
Back to Projects