This product was launched before I joined the team in 2016, and a proper design process was not followed creating an interesting situation: How do you make a success of a product that is based on what I always thought was a fundamentally flawed idea: Why would I want WiFi in my car when I have my phone? Seriously, when I started on this project no one could answer that question for me. Whenever I talked to friends or family about the product they asked me the same question, it felt like it had been conceived by someone locked away Monte Cristo style and prevented from discussing the idea with a single human being.
First things first: Research. I set up Google Analytics and Hotjar to help analyse our users behaviour. We also had a PowerBi dashboard that was underused. I had the data team put together a custom view for the UX team to showcase the key statistics that we were interested in. There was no real concept of KPI’s beyond data plan sales at that time, but I wanted to focus on user growth, overall data use and data use per user, all of which would lead to better sales in the future.
On the UI design I worked in an Agile environment with our dev team with design running one sprint ahead of dev to ensure that blockers were minimised. We organised our work in Jira and used Invision for handing over assets to dev. The challenge here was to build four separated branded versions of the site at the same time (VW/Audi/Skoda/Seat) finding a base design language that was consistent enough to make development and the future onboarding of other partners easy while giving the partners enough flexibility to feel like their branding was fully on show.
The new version of the site launched in January of 2019 and we saw a change from a small stagnant userbase to steady, if unspectacular, growth that gradually increased over time to the point where now sales have increased by 300% compared to this time last year, and that’s in the context of a global pandemic where people are driving far less than they were before.
This growth is not entirely driven by the 2019 redesign. Our last major release in 2020 brought in a free trial feature for Audi and VW users. We identified this as a priority because of the aforementioned disconnection between user expectations and the quality of the product that showed in my user research. It took a while to bring to fruition (No one wanted to pay for it), but when we were finally able to get it designed and developed in late 2020 we saw an additional boost in user & sales growth.
Monthly Sales Growth of 750% (600 p/m to 4,500 p/m)
Active User growth of 430% (3.3k to 14.2k)
Data usage growth of 400% (4.1 TB to 16.6 TB)
I had a month or two when the product wasn’t being given much dev resources and with no pressing work to do I decided to investigate the registration flow. Our on-site registration flow was quite standard, account creation, link your vehicle and complete an ID check (A legal requirement in some of our markets), but when you take into account the process of setting up and connecting to WiFi within the vehicle it became a very difficult task for users and a very difficult process document as there were so many different vehicles to cover.
I conducted a number of straightforward user tests, I sat with them in a car and asked them to set up the WiFi and create an account. On average it took users 45 minutes (!) from turning the car on to connecting to the WiFi. Trying to solve this problem lead to so many of dead ends. I tried to work with our partners on the parts of the flow in their HMI (the in-car computer display), redesigning it to be simpler and more efficient, but found that in most cases HMI’s can’t be updated after the car leaves the assembly line. With that option out, I instead produced a series of videos for each vehicle guiding users through the registration process.
In user tests I found that after watching a 2 minute video users could now complete registration in under 10 minutes compared to 45 minutes before. I produced a few of these (there are so many vehicle variants it’s hard to produce them all without a proper budget) and shared them with partners, hoping that they would link to them through their portals and improve registration that way. They didn’t. It may seem odd to include a big dose of failure in a portfolio (please employ me), but I think this communicates as much about my approach as my (many) successes.