AutoVerify

How to Build an Efficient Data Import Platform That Meets User Needs, Business Goals, and Technical Requirements?

Connecting Hearts and Wallets: Is It Possible to Redesign Dating Apps for Singles While Supporting Business Profits?

Role

Sole UX Designer and Researcher

Timeline

August 2024 - Present (Ongoing)

Team

Cross-Functional (Engineering, Product, Support/ Onboarding)

Role

Sole UX Designer and Researcher

Timeline

August 2024 - Present (Ongoing)

Team

Cross-Functional (Engineering, Product, Support/ Onboarding)

Role

Sole UX Designer and Researcher

Timeline

August 2024 - Present (Ongoing)

Team

Cross-Functional (Engineering, Product, Support/ Onboarding)

I collaborated with a cross-functional team to tackle the inefficient data mapping process. Together, we developed AV Inventory, an internal tool that empowers non-technical teams to configure data mappings. This tool reduces the time needed for customization by 71-97%.

Context

An Essential But Inefficient Data Import Process

Context

An Essential But Inefficient Data Import Process

Context

An Essential But Inefficient Data Import Process

AutoVerify provides automotive dealerships with a suite of technology to improve their sales process from merchandising to transaction. 

When onboarding new car dealerships, AutoVerify needs to import their data. Each dealer has unique needs. Therefore, customized data mapping is required. However, this process is inefficient and required developer intervention.

The Existing Process was Cumbersome

Initial Onboarding

Data Mapping Customization

The onboarding/ support team starts onboarding a new dealership.

A developer customizes data mapping for dealership (7-20 hours).

Initial Onboarding

Data Mapping Customization

The developer customizes data mapping for dealership (an additional 7-20 hours).

The onboarding/ support team facilitates the onboarding process for a new dealership.

Initial Onboarding

Data Mapping Customization

The developer customizes data mapping for dealership (an additional 7-20 hours).

The onboarding/ support team facilitates the onboarding process for a new dealership.

This bottleneck takes away valuable engineering resources and delays client onboarding, impacting both the business and clients.

How can we improve this process so that the non-technical onboarding/support team members can complete the onboarding seamlessly, without relying on developers?

How can we improve this process so that the non-technical onboarding/support team members can complete the onboarding seamlessly, without relying on developers?

How can we improve this process so that the non-technical onboarding/support team members can complete the onboarding seamlessly, without relying on developers?

Discovery

Stakeholders Have Different Priorities

Discovery

Stakeholders Have Different Priorities

Discovery

Stakeholders Have Different Priorities

Principles

Bridging the Gap

Principles

Bridging the Gap

Ideate

What is a "Template"?

Ideate

What is a "Template"?

As this tool intersects multiple facets of the business, I actively gathered insights from stakeholders.

Product Management

We need to reduce setup time to free up engineering resources and enhance dealership satisfaction.

Product Management

We need to reduce setup time to free up engineering resources and enhance dealership satisfaction.

Product Management

We need to reduce setup time to free up engineering resources and enhance dealership satisfaction.

Engineering

We prioritize technical feasibility and a functional minimum viable product (MVP).

Engineering

We prioritize technical feasibility and a functional minimum viable product (MVP).

Engineering

We prioritize technical feasibility and a functional minimum viable product (MVP).

Users (Support/ Onboarding Teams)

We require a user-friendly tool that considers diverse use cases to perform our jobs.

Users (Support/ Onboarding Teams)

We require a user-friendly tool that considers diverse use cases to perform our jobs.

Users (Support/ Onboarding Teams)

We require a user-friendly tool that considers diverse use cases to perform our jobs.

Dealerships

We would like customizable data mapping and a seamless and quick onboarding experience.

Dealerships

We would like customizable data mapping and a seamless and quick onboarding experience.

Dealerships

We would like customizable data mapping and a seamless and quick onboarding experience.

Principles

Principles That Guide Our Decisions

Principles

Principles That Guide Our Decisions

Balance Stakeholder Goals

While everyone wanted to improve the onboarding experience, the definition of MVP differed. The Product Manager and I bridged the gap between engineering's lean MVP and the onboarding/support team's comprehensive needs.

Balance Stakeholder Goals

While everyone wanted to improve the onboarding experience, the definition of MVP differed. The Product Manager and I bridged the gap between engineering's lean MVP and the onboarding/support team's comprehensive needs.

Balance Stakeholder Goals

While everyone wanted to improve the onboarding experience, the definition of MVP differed. The Product Manager and I bridged the gap between engineering's lean MVP and the onboarding/support team's comprehensive needs.

Keep It Simple and Iterate Often

I prioritized a simple, testable prototype, conducting multiple rounds of user testing and incorporating feedback at each stage. This iterative approach ensured the final design met the goals of all stakeholders.

Keep It Simple and Iterate Often

I prioritized a simple, testable prototype, conducting multiple rounds of user testing and incorporating feedback at each stage. This iterative approach ensured the final design met the goals of all stakeholders.

Keep It Simple and Iterate Often

I prioritized a simple, testable prototype, conducting multiple rounds of user testing and incorporating feedback at each stage. This iterative approach ensured the final design met the goals of all stakeholders.

Have Strong Design Rationale

Effective design requires considering diverse perspectives and feedback. However, there will always be different opinions. As the design decision maker, I need to clearly articulate and justify my design decisions.

Have Strong Design Rationale

Effective design requires considering diverse perspectives and feedback. However, there will always be different opinions. As the design decision maker, I need to clearly articulate and justify my design decisions.

Have Strong Design Rationale

Effective design requires considering diverse perspectives and feedback. However, there will always be different opinions. As the design decision maker, I need to clearly articulate and justify my design decisions.

Ideate

What is a "Template"?

Ideate

What is a "Template"?

To streamline data mapping and eliminate repetitive work, we introduced "templates" .

After linking a data vendor to the AutoVerify database and defining the data mapping, the settings are saved as a template.

After linking a data vendor to the AutoVerify database and defining the data mapping, the settings are saved as a template.

After linking a data vendor to the AutoVerify database and defining the data mapping, the settings are saved as a template.

Using a template is simple: after initially linking a vendor database and defining the data mapping, you save these settings as a named template. Subsequently, when setting up new dealerships using the same vendor, you simply select the appropriate template and customize if needed.

Iterations

Refining the Design Based on Feedback

Iterations

Refining the Design Based on Feedback

Iterations

Refining the Design Based on Feedback

Several key iterations stemmed from stakeholder feedback:

Add the Ability to Import Data from Various Sources

1

Old Version:

At first, the design assumed single-source data imports.

User can select one template and then customize the data mapping.

1

Old Version:

At first, the design assumed single-source data imports.

User can select one template and then customize the data mapping.

1

Old Version:

At first, the design assumed single-source data imports.

User can select one template and then customize the data mapping.

Simplify Custom Fields

1

Old Version:

Initially, the onboarding/support team requested the ability to create custom data fields.

For example:

  • New price field = manufacturer's suggested retail price + admin fees

1

Old Version:

Initially, the onboarding/support team requested the ability to create custom data fields.

For example:

  • New price field = manufacturer's suggested retail price + admin fees

1

Old Version:

Initially, the onboarding/support team requested the ability to create custom data fields.

For example:

  • New price field = manufacturer's suggested retail price + admin fees

Who Creates the Template?

1

Old Version:

Originally, to eliminate development dependency, our initial thought is to have our support/onboarding team create these templates.

We will create the ability to do so as part of the product.

1

Old Version:

Originally, to eliminate development dependency, our initial thought is to have our support/onboarding team create these templates.

We will create the ability to do so as part of the product.

1

Old Version:

Originally, to eliminate development dependency, our initial thought is to have our support/onboarding team create these templates.

We will create the ability to do so as part of the product.

Solution

How to Use AV Inventory to Customize Data Mapping

Solution

How to Use AV Inventory to Customize Data Mapping

Solution

The dating app that WANTS you to be in a relationship

AV inventory is a tool that enables non-technical onboarding and support team members to customize data mapping for imports.

AV inventory is a tool that enables non-technical onboarding and support team members to customize data mapping for imports.

AV inventory is a tool that enables non-technical onboarding and support team members to customize data mapping for imports.

Initial Onboarding

Data Mapping Customization

The onboarding/ support team starts onboarding a new dealership.

The onboarding/ support team uses AV Inventory to customize data mapping (0.5-2 hours).

Initial Onboarding

Data Mapping Customization

The user selects the vendor template(s) and customizes the data mapping (0.5-2 hours).

The onboarding/ support team facilitates the onboarding process for a new dealership

Initial Onboarding

Data Mapping Customization

The user selects the vendor template(s) and customizes the data mapping (0.5-2 hours).

The onboarding/ support team facilitates the onboarding process for a new dealership

Data Mapping Customization

Please note: All data used in the design is fictional to protect company confidentiality.

Step 1: Select the dealership you are setting up from the list. The dealer code will auto-populate based on your selection.

Step 2 (Part 1 of 2): For easier editing, users requested that template selection and data mapping be combined on a single page, called "import settings." Choose a default vendor template to start with, and add additional vendor templates if needed.

Step 2 (Part 2 of 2): The second part of the import setting process is data mapping. The default template's data mapping will be applied. You can import data from other sources by selecting a different template, which will apply the closest matching mapping. These fields can be further edited as needed.

Step 3: If you want to import specific data, such as only certified pre-owned (CPO) and used vehicles, you can apply filters.

Step 4: Review and verify all information to ensure accuracy before completing the dealership setup.

Impact

From Days to Hours

Impact

From Days to Hours

Impact

From Days to Hours

While final impact data is still being collected, initial user testing reveals a dramatic improvement:

✏️

71-97%

Time Reduction for Data Mapping Customization

Without AV Inventory (7-20 hours) vs. With AV Inventory (0.5-2 hours)

✏️

71-97%

Time Reduction for Data Mapping Customization

Without AV Inventory (7-20 hours) vs. With AV Inventory (0.5-2 hours)

✏️

71-97%

Time Reduction for Data Mapping Customization

Without AV Inventory (7-20 hours) vs. With AV Inventory (0.5-2 hours)

Reflection

Top 2 Learnings

Reflection

Top 2 Learnings

Reflection

Top 2 Learnings

Importance of User Advocacy

Originally, this was a product/ engineering driven project. I actively involved and advocated for the needs of the tool users, which significantly contributed to the project's success.

Involve Stakeholders Early

The project underscored the importance of cross-functional collaboration and iterative design. The involvement of stakeholders from the beginning was crucial to the success of the project.

Interested in learning More About My Process?

I typically share this during coffee chats or interviews. Don't hesitate to reach out!

Interested in learning More About My Process?

I typically share this during coffee chats or interviews. Don't hesitate to reach out!

Interested in learning More About My Process?

I typically share this during coffee chats or interviews. Don't hesitate to reach out!