Carvana internal document tracking tool
2022

Empowering Carvana employees to track 1M papers and save $4.5M

Drove the design of a web application for 250 employees to track 1M documents annually. After it is built, it is projected to save the business $4.5M.

Case study Employee tools Enterprise
Impact · cost savings
$4.5MSaved for business
2xFaster workflows
01 · Overview
Role
Junior product designer
Scope
Product design, Prototyping, Research and interviews, Strategy, UiUx, User testing
Team
Data analysts, Product manager, Senior designer, Software engineers

Design 0–1 on Carma

I drove end-to-end experiences on Carma, Carvana's internal employee software, working on a highly agile team to build asset tracking tools within Titles, a suite of applications used by specialists to track the assets that enable Carvana to legally sell cars.

Business goals

Carma needs car titles to resell cars that we acquire from customers. This is called “Sell to Carvana” (STC). An important part of the business, STC powers about 90% of Carvana's inventory acquisitions. It's the second highest revenue stream for the business!

Carvana's STC web experience
Carvana's STC web experience
User goals

Specialists (users) focus on tracking legal documents (assets), to obtain a title. A title is a legal document that establishes proof of ownership. In this case, we needed titles that listed Carvana as the owner.

Example of a car title
Example of a car title
02 · Opportunity

Digitize the tracking of 1M papers

While shadowing users, the team saw specialists physically tracking the movement of a high volume of documents daily, sent and received from company buildings, financial institutions, and customers. Annually, this amounted to 1M+ papers, moved through a tedious, slow, error-prone process.

Outbound paper assets, ready for pick-up
Outbound paper assets, ready for pick-up
Challenge
How might we create a more reliable, efficient, digital way for specialists to move assets?
Framing
Assessment criteria
User value
Something users and operations leaders requested.
Viability
Scalable, with potential to drive significant operational savings.
What would success look like?

I made design decisions to optimize efficiency for users.

Fulfillment time
Time (hours) from request to delivery.
Failure rate
Percentage of unworkable assets.
MVP would offer 3 key experiences

After doing a MoSCoW exercise, the team scoped three key experiences:

1. Work
The ability to view and fulfill requests.
2. Request
The ability to request the movement of assets.
3. Manage
The ability to view or delete requests.
Design constraints to consider

Users' workflows were highly physical, so I had to factor this into design decisions:

Hand scanner device
Hand scanners
Users use hand scanning devices to complete work.
QR code label
QR codes
Every label has a QR code with embedded metadata.
Scanning labels
Scanning labels
Users scan labels to provide updates to system.
Interviewing users

I conducted remote interviews on current workflows and needs. Two themes emerged:

1. Performance
“I want to be able to track my personal progress”
2. Data preferences
“We have unique preferences when it comes to viewing data”

These insights shaped ideation, alongside design reviews and stakeholder discussions.

Key flows

While workflows involve physical tasks, for simplicity purposes, I am only showing digital flows:

Work flow diagram, happy and unhappy path
Work
Key flow: create request
Create request
Add an entry point to the main navigation
Previous vs. proposed nav bar, adding a Pull tab
Labelled “Pull” (the nomenclature used by employees) for a discoverable, one-click entry point to the new experience.
Insight
It's important to be able to track work progress.

Users wanted to see the total number of assets per category, not a single % of work completed.

Iterations and final: showing total assets per category
I like seeing the totals because it'll help me divvy up and track work. To me this feels like it naturally fits into our current process.
Team Lead at Carvana
03 · Solutions

Optimizing efficiency and reliability

Originally I envisioned 3 separate screens. Manage would act as the landing page with 2 modes to access the different experiences. However, the potential user value did not seem to be greater than engineering lift. So, I decided to locate Work within Manage. Therefore, MVP would consist of 2 screens.

Since the views are nearly identical for each mode, see this single visual:

Manage and work screen, annotated key interactions
Manage and work
Request screen, annotated key interactions
Request
Key screens

The below diagram shows key screens in high-fidelity, along with key interactions and screen functionality.

Manage, work and create-request screen map
Flows and prototypes
Work · Happy path
Work, happy path — 1
Work, happy path — 2
Work · Unhappy path
Work, unhappy path — 1
Work, unhappy path — 2
Request · Happy path
Request, happy path — 1
Request, happy path — 2
04 · Impact
Shipped

Delivering measurable savings and efficiency

This solution is projected to save ~$1.61/employee. Since each employee pulls thousands of documents daily, this totals ~$4.5M in annual cost savings for Carvana. Additionally, employee speed is projected to increase. Ideally, with more time, users are empowered to spend their time and energy on higher-value tasks.

Designs in development

As of November 2022, the designs were delivered to be built by our engineers.

Positive user signal

We received positive signal during our final rounds of user testing. Users were excited for this to launch:

I'm so excited for this to go live. We can pull thousands of documents daily, so this will be a game changer.
Senior Specialist at Carvana
Next steps

Since designs were being built as I left Carvana, I'd be curious to assess performance against fulfillment time and failure rate, then explore extending this thinking to other tools in the app as new data becomes available.

Powering a crucial part of the business

While at Carvana, I:

01Optimized efficiency across workflows that power 90% of inventory acquisition.
02Designed to drive cost saving initiatives.
03Strived to imbue joy for ~250 daily users, simplifying work tasks.

By the time I left, design had made progress digitizing work that directly impacts the bottom line, amplifying a previously unheard part of an org of ~18k employees.

I designed for 250 specialists whose work still ran on paper, in an org of ~18k

If you're designing for the people who keep a business running, let's chat.

Get in touch ↗
Samantha Samuels Resume ↗ LinkedIn ↗ Email ↗