|OCR

|OCR

Role

Lead UX Designer

Tools

Figma icon
Google Suite Icon
Maze Icon

For this project, the client is a company that serves as an intermediary between car dealers and major banks. They aim to reduce loan application processing costs by over 10% using AI, through a solution that integrates automation with manual processes. To achieve this, our team developed an OCR (Optical Character Recognition) solution that reads and extracts information from documents sent by dealers, quickly determining if customers are eligible for funding.

  • Discovery

  • UX Research

  • Prototyping

  • Testing

  • Design System

  • High Fidelity Prototypes

  • Furhter Testing

  • Hand Off

  • Play Off

DISCOVERY

Project Scope

To become more competitive and appealing to car dealers, the client needs to offer faster loan funding decisions that dealers can present to their customers.

Currently, the screening and loan funding process can take hours due to its manual nature. Screening and funding agents need to manually assess many documents to ensure accuracy. Additionally, most applications contain errors made by dealers, which cause delays.

To address this issue, our company has been hired to develop an AI solution that enables faster document reading and information extraction from dealer submissions, to validate errors and automate the funding process.

Project Goals

To define the scope, features, user interactions and deliverables for the MVP phases and beyond.

UI Icon

To define User Personas as well as their current pain points, expectations, and current workflows.

User Journey Icons

To understand current processes and propose a new User Journey that integrates the AI solution.

Design System Icon

To design a UI that is intuitive and encourages user adoption and is independent of third-parties.

What does success looks like?

User Journey Icons

Application funding approval time is reduced from 10 hours to at least 2 hours

User Journey Icons

80% of the client’s staff is focused on Funding applications as opposed to screening applications for errors

User Journey Icons

Users easily adopt the new solution and prefer to use the new UI as opposed to their previous software and methodologies

Potential Constraints

User Journey Icons

The current LOS (Loan Origination System) software used for application screening and approval is owned by a third party, making integration more challenging both technically and in terms of user experience.

User Journey Icons

Our team has access only to our client’s processes and data and cannot influence the processes of car dealers.

User Journey Icons

For the best experience, our team ideally needs to develop our own document splitting and classification solution. However, this might be beyond the scope of the project.

User Journey Icons

The client hasn’t had previous experience working with UX | UI teams

Deliverables

User Persona Icon

User Personas

User Journey Icon

User Journeys

Sitemap Icon

Sitemap

Wireframe Icon

UI Design

Usability Testing Icon

Usability Testing

Design System Icon

Design System

Design System Icon

Assessment and Recommendations

High Fidelity Prototypes Icon

Front-End Development

RESEARCH

Research Objectives

Broken Link Icon

To identify existing gaps in the user experience

User Icon

To understand users’ motivations and pain points

Process Icon

To clarify processes around application funding

Code Icon

To identify any technical requirements and further potential constraints

Meetings and Existing Documentation

At the start of the project, we did not have direct access to Funding Analysts. Instead, we met with Managers and Technology Advisors to understand the Funding Analysts’ needs, pain points, and current processes, as well as technical options and constraints.

The client also provided demo videos and documentation explaining the application funding process from both the dealers’ and the company’s perspectives. Using this information, I developed user personas and future user journeys.

User Personas

Our research identified four user personas. The primary user of the AI validation tool will be the Funding Analyst, while a Leadership Team Member will oversee the KPI and Resource Planning screens.

Personas

Funding Analyst
Leadership Team
Screening Analyst
Car Dealer

Emerging themes

  • About
  • Responsibilities
  • Goals
  • Pain Points
  • User Needs (Must-haves vs Nice-to-have)
  • Software Integrations
  • Expected outputs and explainability

User Stories

Speed
As a Funding Analyst I need to make sure to achieve the application accuracy standard but I’m required to do many applications in a day, which might make me oversee some details
Meeting the Bank's Gold Standard
As a Funding Analyst I need to make sure to achieve the application accuracy standard but I’m required to do many applications in a day, which might make me oversee some details
Accuracy
As a Funding Analyst I want to make sure that each field of the application is accurate but the process can be tedious and the documentation needed to validate the application can be cumbersome to find within the LOS
Trust
As a Funding Analyst I want to approve applications fast but I don’t always trust that the Screeners reviewed the application properly
Updated
As a Funding Analyst I want to make sure that the application aligns with the Dealer’s latest changes, but the print documents don’t always match the information in DealerApp
Fast Communication
As a Screener, I want to let the Dealer know about Deficiencies in their application as soon as possible, but because of bottlenecks, this can take more than 10 hours

User Journey

I worked alongside the Business, Engineering, and Data Science teams, as well as with the client, to define the following user journey and determine how the new AI solution would be integrated with the client’s current processes and tools.

To define the final version of this journey (as of now) multiple iterations, meetings and testing were required.

The goal was to make the user journey as automated as possible so that Funding Analysts could focus on approving funding as fast and accurately as possible.

Application First Submission User Journey/Flow

Feature Workshop

To determine which features needed to be present and prioritized in each phase of the project, our team conducted a Features Workshop.

The first part of the workshop was conducted in FigJam and the prioritization exercise was conducted on JIRA.

ARCHITECTURE

Sitemap

The original sitemap consisted of a huge amount of pages with repeated, disorganized, and outdated information.

UI DESIGN

Wireframes

One of the challenges was that the client was not internally aligned with the expectations for the UI. Through meetings and multiple iterations, I refined the wireframes for user testing.

The main screem was divided into three simple sections: data entry revisions (where users validate and correct issues detected by the OCR), deficiencies review (validating application business rules), and a final read-only review section. In the future, the plan is to further automate this process as we continue to develop the technology and users gain trust in our solution.

USABILITY TESTING

To do usability testing, I used a combination of unmoderated remote testing by using Maze and moderated remote testing by conducting meetings over Google Meets 6 Participants participated in the first part of the usability test.

Overall, user opinions were divided. Some participants found the process difficult and unintuitive, while others found the new solution easy to understand and helpful for reviewing funding applications.

Many dissatisfied participants felt there wasn’t enough context provided, making the
process confusing.

Despite most users not being previously trained on the platform, screen recordings showed they followed expected behaviours.

FINAL DESIGN