
Cinch
Mobile App
Creating a new sales and engagement channel
Leadership · Research · UX
The Project
Cinch, which was launched in 2020, had so far achieved annualised sales of more than 50,000 vehicles and was attracting 30 million unique visitors a year to its website.
Once they’d established significant brand-presence, the time came to delve into other avenues to sell vehicles and to provide added value to existing cinch customers.
The business and it’s investors had ideas for what they wanted the app to do and why, and it was our job to discover what users really wanted from the cinch app and to balance these findings with business objectives.
My Role
I was tasked with leading the UX, design, content, and research and analytics team responsible for the app. This involved working closely with the app product owner, marketing, and development, as well the executive team who had great interest in the project.
Whilst the app was being built, new features and changes were constantly being made to the Cinch website, and new research was being undertaken and actioned. I was accountable for making sure learnings and changes from all areas of the website were fed into the app where appropriate, and that any relevant, successful changes from the app were also fed back into the website.
The problem statement
“How can we make the car buying and ownership experience even easier and more engaging for our users?“
A number of factors have an influence on this. In particular…
Buying a car is usually a large, sporadic purchase.
Cinch is a used car marketplace, that sells various makes and models of vehicles, with varying features, from various suppliers.
Discovery
A lot of research, discovery, design, testing, and data analysis had recently been done on the existing Cinch website and its key journeys.
This insight and information was collated and used together with newly-created, data-driven customer segments, to form the basis for the app MVP.
We also analysed Cinch’s competitor’s apps and other well-designed apps and app features from other industries too.

*Existing website research, analytics, and journey collation, plans, competitor apps and interesting apps from other industries, customer archetypes and behaviours, and Cinch branding samples.
Initial user research, consisting of a series of survey questions using Microsoft forms and Usertesting.com was undertaken to help inform the team…
Who app users are.
What motivates them to use an app.
How we can make their of experience buying and owning a car more seamless.
How we can encourage them to become loyal to Cinch through the app.
The insights from the initial user research helped the team to make more informed decisions about…
The direction of any research going forward.
How we could improve the app experience post launch.
Prioritisation of iterations and features.
The USP’s that could help improve the apps desirability.
The things that might put users off using the app.

*Early stage user research
Using the insights gathered from the initial research, the previous research and testing, and data analysis, and the data-driven customer segments, we launched a design sprint to ideate potential ideas in the following areas:
Pre-purchase – attention, search, select
Buying
Delivery and post-purchase
Ownership
Retention and ongoing engagement

Design sprint to ideate potential ideas

Most voted ideas
Many great ideas came out of the design sprint as well as plenty of questions and assumptions that needed further investigation. The most voted ideas were turned into a visionary prototype.
Prototype/vision presentation for the Cinch C-suite team.
After the C-suite presentation and their feedback, the team held follow-up sessions with other key stakeholders, analysing ideas and planning actions that would lead us to a clear vision for the product.

Prioritisation of features.
Ideating a new concept and system
At this point, it was decided that it made sense, for the business, to use the current website as the basis for the app’s key journeys, and adapt these where necessary for the app, focusing on:
Pre-purchase – attention, search, select
Buying
Delivery and post-purchase
Ownership
leaving retention and ongoing engagement and any major new feature introduction until after the MVP launch and subsequent research had been done, in order to better understand the general usage and uptake of the app, and any further user needs and interests.
In the following 2 weeks, the team further analysed customer archetypes, competitors, and the current cinch website journeys; sketching and wire framing enough concepts to work out how ideas can make sense, and drafted the initial version of IA and flows.
The outcomes were then discussed with the core team and made ready to be challenged by the target users.

Explanation of image goes here
Early test & Iterate
The team spoke to target users with IOS and android mobile phones for several weeks to gather insights that would shape the MVP using a variety of research and testing methods.
GOAL 1 ↓
Search
The app’s search journey, along with the checkout journey, was an area that needed to be tackled early on in order for users to locate their preferred car successful and get through the buying process.
The search journey also provided a starting point for what is displayed on the home screen (if in fact, there was to be a home screen at all), and the product detail pages.
This journey wasn’t designed in isolation. Each of the journeys were thought through at the same time. Some sketched, some made into prototypes and tested, to help make design decisions on a whole.
This approach also helped to make any adjustments as work planned in the website roadmap was released, and it helped us set the future iterations of the roadmap later down the line.

GOAL 2 ↓
Checkout
.
Checkout was a complex, and vital part of the app as it encompassed so my options and routes, such as part exchange, different types of finance, and delivery information, etc.
Combinations of theses routes and journeys were thought through at the same time. Some sketched, some made into prototypes and tested, to help make design decisions with a more entire picture.
These journeys also required a lot of financial compliance content to be included. The challenge for us was to still remain ‘cinch’ and ‘faff-free’, whilst communicating this important legal content to our customers.
The app’s UX designer, researcher, and content designer worked very closely with Cinch’s regulation and policy team to achieve this balance.




GOAL 3 ↓
Post order management
.
Through discovery and research, we found out more about the user’s needs and desires when using the cinch app, especially when using it for post order management.
One of our biggest challenges for the future was going to be persuading users to keep engaging with the app post-purchase, as many of the users that were interviewed said they expected that they would delete an app like this after delivery unless there was a compelling reason it keep it on their phone.

GOAL 4 ↓
Favouriting and car comparison
The ability to save and favourite cars and to compare different cars spec, features, and information was something we had discovered users wanted through research.
Flows and screens for how this would work were mocked up, tested with users, and subsequently iterated upon.





Product detail
The product detail pages needed to be ‘succinct’ and easy to use, but they also provided the buyer with much needed information that allowed them to understand more about the car they were about to purchase.
The product detail pages would also provide the user with the ability to understand the financial implications of part exchange, the different finance options, and payment structures.

The home screen
Several versions of the home screen were created and tested. A version of the app that went straight into the search journey without a home screen was also tested.
Although some of the features could not make the MVP, this work gave us a good, solid foundation for the app’s home screen roadmap.
Launching the MVP (Pilot)
Tasks
Create landing page and links to Play and App Store in collaboration with marketing.
Working with the developers to ensure designs are built accurately and that interactions and accessibility ids implemented as per our spec.
Discussing the pilot details with the researcher and the data analyst eg. research, themes, questions, and use of analytics tools.
Fleshing out the homepage and creating the onboarding experience, in collaboration with the marketing team.
Pilot Objectives
To test the technical delivery of the app and the reliability to the API and services provider by third-parties.
To get feedback on the experience and features of the app, so that we have more of an idea which improvements to design and prioritise in the next phase.
To refine our knowledge of our users and their needs.
On-site signposting
Whereabouts to put the links to the app.


Various options for placement of app signposting
Apply learnings to native app design
The longitudinal study for the MVP ran for 3 months. We used adobe analytics for behavioural data in-app, regular surveys and interviews for attitudinal data, and a tree test for IA validation.
Onboarding

Help me choose




Native search
Using the apps native functionality to improve search

Home screen
Various tests were run, and features added to the homepage, such as shop by budget, shop by budget, returning user views, promotion info, and different sized car cars with various types of information.



Notifications
The business and marketing wanted to use push notifications. There was also an appropriate user-driven application for push notifications, such as when car finance was approved or car deliveries had arrived.
Given the responses from users during previous research, which contained valuable insights into users attitudes towards notifications, we thought it appropriate to do some more research into this area.



VQA
During VQA, designers and developers work together to ensure that high-fidelity designs and builds are aligned perfectly, checking for interface bugs and inaccuracies. It’s a crucial time for both parties to collaborate effectively. Make products look good before releasing them to customers with Visual Quality Assurance (VQA)
Designers must communicate their expectations with developers before a build commences to make the VQA process more efficient and establish a better rapport, eliminating assumptions and limiting the number of VQA rounds to a maximum of two. When the designer closes VQA, the product owner approves the solution for release. After launching a solution, it’s also integral for teams to monitor its performance to ensure users are operating it as intended.

Accessibility
It’s essential to ensure that all users, regardless of their abilities, can comprehend, explore, and operate native applications. Following guidelines benefits not only individuals with disabilities but also a diverse range of people who can benefit from these features. Accessibility for native applications varies from that of the web.

Post-build and during QA, developers and designers are jointly responsible for ensuring the documentation is delivered. Before presenting to the product owner for approval and release, ensure the implementation of accessibility features — achieve this by scheduling virtual meetings with developers to run simulations and demonstrate solutions.
Following guidelines benefits not only individuals with disabilities but also a diverse range of people who can benefit from these features. Ultimately, this will positively impact conversion and make your app more marketable.
App store view
The app as it appears on the app store.











