top of page

FORDPASS

OVERVIEW

Drivers can unlock and start select Ford and Lincoln vehicles using their phones, or a keycard, as a key. As part of a multi-team project, I designed the Android and iOS screens for this feature in the FordPass and LincolnWay apps.

DOUBLE DIAMOND PHASES

FordPassDoubleDiamond.png

KEY CONTRIBUTIONS

  • Designed wireframes and high-fidelity screens for android and iOS with cross-functional teams using FDS (Ford Design System) and LDS (Lincoln Design System).

  • Contributed to other features like 'Remote Park Assist,' 'Can I Tow This?,' and 'Climate Control' to enhance smartphone and vehicle integration.

SKILLS DEMONSTRATED

  • User Experience Design: Expertise in creating user flows, wireframing, and developing high-fidelity designs.

  • Collaboration: Worked closely with cross-functional teams, including engineers, project managers, and other designers.

  • Advocacy for Usability Testing: Strong proponent of research-based design, ensuring user feedback is incorporated early in the process.

  • Proficiency with Design Tools: Skilled in using the Ford Design System (FDS) and various design tools beyond Figma.

  • Attention to User Journey: Considered both on-screen and off-screen user interactions to create comprehensive user flows.

"USE YOUR PHONE TO UNLOCK AND START YOUR CAR"

Since its debut in 2016, the FordPass™ mobile app has evolved to offer users unprecedented control over their Ford vehicles via their smartphones. My contributions include features like 'Remote Park Assist,' 'Can I Tow This?,' and 'Climate Control,' all designed to enhance smartphone and vehicle integration

​

PROJECT SCOPE

​

NFC technology allows users to access and start their vehicles with a keycard resembling a credit card, much like the keys used in hotels. While the feature and engineering requirements were set before I joined the team, I took the project through the following stages:
 

  1. Defining the User Journey

  2. Creating Wireframes

  3. Building High-Fidelity Screens

  4. Usability Testing

​

​

​

​1. DEFINING THE USER JOURNEY

​​

There was a quasi-user journey available when I joined the team, but it was geared towards the technical functionality of the feature and didn't take into account the individual users' journey when using the feature. This flow was refined through collaboration with engineers, project managers, and experience designers, and took into account both on-screen and off-screen interactions.​​

​​​

​

Screenshot of Existing User Journey

​

​

Screenshot of Developed User Journey​

​​

Icon 3.png
Icon 2.png
Screen Shot 2021-11-24 at 2.51.06 PM.png
Icon1.png

Sample of Key from User Journey

I used this finalized user flow to define the feature's functionality across devices.Although my primary responsibility was creating mobile screens, I recognized the importance of understanding the entire user journey.

It is easy to overlook the entire user journey when designing wireframes. "If a user action is not on-screen, how can we have a screen for it?" As product designers, it is part of the job requirement to fully define the context in which a given user is interfacing with the product. Are they hungry? What time of day is it? What else is competing for their attention at that moment? What would they expect to happen next? 

 

Hence, the need in this project to catalogue that. In setting up a new key, users were switching between the app, their text messages, their physical vehicle, and potentially other household members (who may or may not be physically present). 

​

Since we were able to define the total user journey, I began creating wireframes.

Step up Authentication.png
FP Home.png
Add Key with Owner Device.png
Name Owner Key.png

​​​​2. CREATING WIREFRAMES

​

During wireframing, multiple screen designs were reviewed, vetted by iterated upon with various stakeholders. The team needed screens for Android and iOS, and for LincolnWay. ​

​

Screen Shot 2021-11-24 at 3.29.15 PM.png

​During wireframing, multiple screen designs were reviewed, vetted by iterated upon with various stakeholders. The team needed screens for Android and iOS, and for LincolnWay. ​

​

​​

3. HIGH FIDELITY SCREENS

​​

During wireframing, multiple screen designs were reviewed, vetted by iterated upon with various stakeholders. The team needed screens for Android and iOS, and for LincolnWay. ​

​

Error State_ Authentication Denied Copy 4.png

FordPass Wireframe

Error State_ Out of Range Copy.png

FordPass iOS Light 

Error State_ Out of Range Copy 2.png

FordPass iOS Dark 

Error State_ Out of Range Copy 3.png

LincolnWay iOS

​The screens were then uploaded to Invision where they were built out by the developer team and implemented into both apps. ​

© 2023 by My Site. All rights reserved.

bottom of page