Purplebricks

I was employed by Purplebrick in 2021 and joined a large UX & Design Team to help develop their design system and improve their products. Here are some examples of work and other areas where I have helped improve the company products/processes:

The design system

On joining Purplebricks, one of my first tasks was to help develop the Purplebricks design system (known as Blueprint) from scratch: https://www.purplebricks.design/ – (using zeroheight.com)

Introduction to Google Optimize and Firebase

The Purplebricks design team had a very strong approach to Qualitative research (great access to interviews, questionnaires, focus groups, participant-observation and so on…).

But when it came to Quantitate research, there were many areas which needed improvement. Early into joining the team, I wanted to ensure that we use more of the numerical data we have available through Analytics and also introduce Google Optimize and Firebase.

By introducing these products and training other team members how to use them we have revolutionised the way we do A/B and Variant testing. Every new design can be rolled out slowly and tested against the old variant with minimal fuss, saving the company time and valuable resources.

Conversion Rate Optimisation

Using Google Optimize and working closely with the Marketing and Growth departments, we have produced some fantastic increases in our conversion rate. Here are some notable examples:

Finding the best H1

We wanted to quickly test the most effective Homepage Title. There were four options to choose from, but rather than leave it to a vote (how it was done in the past) we tested the four variants with “Looking to sell your property?” winning with a slight 0.17% lead:

Adding a friendly face

When a customer books a valuation, we wanted them to see the local agents that they’d be working with. The hypothesis being, that they would be more likely to complete the process if they could see friendly faces and reinforce the idea that we have local experts in the customers area.

It seems like a simple change, but it would cost a lot of dev resources to implement, so it was important that we test it first. And here are the results: