Clicars is the leading online concessionaire in Europe. We buy cars to official providers, we certify and repare them on our lean garage and finally we put them on sale as “good hand” cars in our web and classiffied partners.
All the company work with our internal web app that helps workers to administrate, control and manage every single aspect of a car flow: from certificators, to garage workers, to the buyers, sales, finances, documentation and financings. We have an in-house agile IT team of developers to constantly upgrade the product and the web to the next level.
User Research | UX Design | Interaction design | Visual design | Prototyping | User testing
Product ManagerPrioritazing | Defining and Validating the Product Lifecycle & Roadmap
March 2019The Purchasing team daily spent more than 2h per day batching cars by manually comparing prices in other platforms to set up our car prices according to the market. We wanted to improve the current car batching functionality that would authomatically collect the daily data they needed to analyse and set the prices based on IA.
I base my process on the Double Diamond Theory and Lean UX process. I aim to incorporate the key phases of Discovery, Definition, Ideation and Implementation in all of our projects.
I conducted a focus group and interviews with our primary users (purchasing analysts) to uncover any pain points that they were experiencing with the V1 release of the quotation tool.
My research encompassed:
From these findings, we decided as a product to identify key business goals:
As a starting point, we did a market research to compare the current quotation tools offer in the market and take inspiration from particular features that we liked about each product.
I then conducted a crazy 8 session to encourage each member of the team to draw out their vision of the solution.
Based on the sketching sessions, it was revealed that there were commonalties in the product vision. We identified the following key user stories:
Building a batch quotation tool had a strong Data Base developing logic. In order to validate the front-end idea with the engineers on the architecture, I mocked up the main screens divided on 3 easy steps for the MVP based off the sketches created by the team and came up with the following:
1. Step 1: Selecting the provider and updating the excel template
2. Step 2: Validating each car version
3. Step 3: Batch result list
4. Extra functionality: Creating one or many new purchases on the app
As the application is an internal web app used by Clicar’s workers on a daily basis, the UX has to provide calm, consistency, its information architecture must be homogeneous, and to enhance to navigate as less as possible to reach a goal.
We decided to also re-design the UX/UI of the existing car quotation tool in order to upgrade the product pricing tools.
Quotation tool re-designI redesigned the graphics and the way of showing the results of a single vehicle divided on selling and purchasing tabs
Users would start the batch quotation at this point by selecting the provider, uploading the template and naming the quotation so it can be easily found on the historical tab.
The second step would be the validating the versions of template uploaded on the previous step
The final step is the result of the quotation batch, where if it fits, users can also create the purchase selecting the final purchased cars
