AutoVerify

How can we design 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

Lead Researcher and Designer

Timeline

August 2024 - Present (Ongoing)

Team

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

Role

Lead Researcher and Designer

Timeline

August 2024 - Present (Ongoing)

Team

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

Role

Lead Researcher and Designer

Timeline

August 2024 - Present (Ongoing)

Team

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

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 powerful digital retailing and merchandising tools throughout the entire sales process from merchandising to transaction. 

Data plays a crucial role in using these tools. However, the data import system was inefficient and required developer intervention, hindering new client onboarding.

The Existing Process was Cumbersome

Initial Onboarding

Database Integration

Data Mapping Customization

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

A developer links each vendor to the AutoVerify database, doing this once per vendor.

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

Initial Onboarding

Database Integration

A developer links the vendor database to the AutoVerify database (20-35 hours).

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

Database Integration

A developer links the vendor database to the AutoVerify database (20-35 hours).

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 from the technical backlog and delays client onboarding, impacting both the business and clients.

How can we improve this process so the non-technical onboarding/ support team can complete the onboarding process seamlessly without developer dependency?

How can we improve this process so the non-technical onboarding/ support team can complete the onboarding process seamlessly without developer dependency?

How can we improve this process so the non-technical onboarding/ support team can complete the onboarding process seamlessly without developer dependency?

Discovery

Stakeholders Have Conflicting Priorities

Discovery

Stakeholders Have Conflicting Priorities

Discovery

Stakeholders Have Conflicting 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 various stakeholders.

Product Management

Need to reduce setup time to free engineering resources and improve dealership satisfaction.

Product Management

Need to reduce setup time to free engineering resources and improve dealership satisfaction.

Product Management

Need to reduce setup time to free engineering resources and improve dealership satisfaction.

Engineering

Prioritize technical feasibility and a functional MVP, focusing on essential features.

Engineering

Prioritize technical feasibility and a functional MVP, focusing on essential features.

Engineering

Prioritize technical feasibility and a functional MVP, focusing on essential features.

Dealerships

Would like customizable data mapping and a seamless and quick onboarding experience.

Dealerships

Would like customizable data mapping and a seamless and quick onboarding experience.

Dealerships

Would like customizable data mapping and a seamless and quick onboarding experience.

Users (Support/ Onboarding Teams)

Require a tool encompassing diverse use cases to effectively perform their jobs.

Users (Support/ Onboarding Teams)

Require a tool encompassing diverse use cases to effectively perform their jobs.

Users (Support/ Onboarding Teams)

Require a tool encompassing diverse use cases to effectively perform their jobs.

Principles

Bridging the Gap

Principles

Bridging the Gap

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 the process of connecting and configuring external vendor databases for the non-technical users, we came up with the idea of "templates":

Templates are saved settings for database links and data mappings, eliminating repetitive work when onboarding new dealerships.

Templates are saved settings for database links and data mappings, eliminating repetitive work when onboarding new dealerships.

Templates are saved settings for database links and data mappings, eliminating repetitive work when onboarding new dealerships.

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 AV inventory.

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 AV inventory.

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 AV inventory.

Solution

The New Process with AV Inventory

Solution

The New Process with AV Inventory

Solution

The dating app that WANTS you to be in a relationship

AV inventory is a tool that empowers non-technical onboarding/ support team members to easily set up data mapping for imports and exports.

AV inventory is a tool that empowers non-technical onboarding/ support team members to easily set up data mapping for imports and exports.

AV inventory is a tool that empowers non-technical onboarding/ support team members to easily set up data mapping for imports and exports.

Initial Onboarding

Database Integration

Data Mapping Customization

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

A developer links each vendor to the AutoVerify database, doing this once per vendor.

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

Initial Onboarding

Database Integration

If the vendor database isn't in the system, the user creates a vendor template (1-3 hours).

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

Database Integration

If the vendor database isn't in the system, the user creates a vendor template (1-3 hours).

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: Data used in the design is fictional to protect company confidentiality.

Step 1: Enter the necessary data to set up the dealership.

Step 2: Select the appropriate vendor template(s).

Step 3: Customize the data mapping as needed.

Step 4: Add filters to import only certain data if needed.

Step 5: Review and verify 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. Actively involving and advocating for the needs of the tool users was critical to the project's success.

Involve Stakeholders Early

The project underscored the importance of cross-functional collaboration and iterative design. The involvement of all 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!