Case Study: Asana

Asana is a project management software that allows teams to coordinate their workflow in real time. In 2015, they took on a massive redesign of their website. This redesign would impact everything from their brand identity to marketing and their product’s functionality, so there was a great deal riding on the project. To reduce risk, they took an iterative approach to the redesign, experimenting on the various elements over a period of ten months. By the time their process had ended and they were ready for launch, Asana had experimented on over 50% of the website’s new form and functionality.

In a project with this kind of scope and impact, QA is particularly important. Ensuring that the site or app runs and looks the way you want it to and that your experiment is collecting all the relevant data before it launches will help you feel confident in your results. A solid QA approach will give you feedback that will allow you to accurately iterate to other experiments and build the best redesign possible, because you’ll have hard data that will back up each phase of the process.

When they rolled out the final product, Asana’s redesigned website was incredibly well-received by users and reviewers in the press. In fact, it was so well-received that launch day of the new design resulted in the largest number of single-day sign-ups in the company’s history.

And what else did experimentation and solid quality assurance do for Asana? It made that launch day significantly easier!. Ashley Kemper, Websites Program Lead for Asana said, “On launch day, we could focus on making sure everything went smoothly and not worry as much about how our metrics would be impacted.”

Can you imagine being that confident about your next website rollout? If you knew you could trust your data, you could rest much easier when you want to execute your next redesign. This course will show you how to design and execute a QA process that will help ensure you’re not tossing and turning the night before your next launch.