Raid provides insecticide products and educational knowledge to protect people from bugs globally. The website serves as the center of Raid's digital ecosystem across 30 markets with 6 brands. However, due to the limited investments from past years, customers cannot find complete information of what they are looking for and the load speed is slow.
Based on the stakeholder's interviews and the original site analysis, our goal is to make the content easy to navigate and modernize the look and feel. Through it, customers can find answers to their bug problems and trust Raid's expertise to use the products.
UX Design
UI Design
Prototyping
Style Guide
Through an end-to-end design process, focusing on moodboard, editorial, bug finding tool experience, and site pages design.
Energy BBDO
Crista Conaty
(Experience Director)
Cori Johnson (UX)
People had issues finding their bug solutions because the original navigation dropdown directly listed all product names. The whole navigation became overwhelming. After competitive research, brainstorming, and internal discussion, we decided to have “bugs” on the navigation, and a person can learn more about the bug and find the product solutions.
Also, we needed to consider localization for the site to work in 30 markets, in 15 languages, and with 6 brands. Last, we needed to increase the site speed performance by optimizing image sizes.
Bug finding tool helps people identify the bug they see. During the ideation phase, we explored an option that people can take a picture or upload their bug photo to identify the bug. However, one big issue would lead to a failure result. The issue was the bug photo's resolution and clearness considering a bug normally moves, flies, the size might be very small, or during the evening time with a low-light environment.
The most essential insight was to provide a way to show all the bug pictures at first while giving helpful filtering options to narrow down the selections.
There were two parts to create the editorial experience: site page templates (landing & details page) and content creation. We needed to adopt/adapt 38 articles and create 10 new articles.
In order to make the process smoother across the internal team, clients, and the development partner, we created a modular content system to support all types of content on the site and used collaborative well-structured copy decks that included developer tags (like H tags, links, section module). This helped us efficiently build large amounts of articles without mocking up all the pages.
The site initially launched in Argentina and the US markets. Although other market launches will be implemented based on the local teams’ priority, it’s still important to consider all the goals and variations when designing the site.
There was a development pause due to a switch of the development company. With the transferring process, we needed to communicate clearly about the site structure, detailed designs, and what was already developed. During the UAT (User Acceptance Testing) phase, it was crucial to point out staging links to show the detailed issues and use image annotations to help communicate and provide a solution, especially since the development team was working remotely with us.