During my tenure at Getsurance, I launched products and web applications from scratch, built and maintained the entire overarching design system, and constantly iterated on designs to improve the customer experience. Below is a deeper look into how I solve design problems.

The first steps to developing the design system was to take an inventory of what exists, what is missing and systematically work through these while testing as I delivered. I started with the foundations of the system, typography, colours and spacing. Which then filter down to the rest of the components and compounds - also known as Atomic Design. This is not a new concept, however it is crucial for a robust user interface library.

Understanding how a web application is built is key to ensuring designs are communicated and implemented successfully. I collaborate closely with the dev team to understand the nuances of our technology, so that right from inception, the designs are technically feasible. This also makes handover and QA more efficient.

Prototyping is an integral part of my design process and in this example I was able to simulate the claims workflow and gain stakeholder approval. The module has now been launched, and was so successful we replicated for cancellations. In doing so, we were able to stem the flow of cancellations by 33%.

Testing can, and should, always be done at any stage. Prototypes are the perfect vehicle to test before needing any technical implementation. Below explores multiple approaches of the checkout whilst in its infantile stage. And once products or features have launched, continuing with small A/B tests of more granular but high impact improvements.

I have launched multiple projects from scratch within my company. The latest one being a migration of the website to a new CMS. It involved collating and streamlining components, defining new breakpoints. This was informed by our data we've collected on users devices, as well as meeting Google’s page speed requirements.