Quest customers have a hard time finding the right product licensing and savings suites for their needs. They find the content on the e-commerce website confusing. A single mistake during the purchase can lead to calls to sales and affect missing savings they could make during their online shopping.
We redesigned the website to guide choosing the right product that fits the expectations of our customers so that they can benefit from promotions during the purchase journey without having to call sales and avoid extra work for the return process. Here are some of our high-level goals:
UX/UI Designer
4 Months (2018)
Designer, Stakeholders, Product Manager, Project Manager, 3rd-party Developers, Sales Team
Sketch, Frontify, InVision, Zeplin
During the research phase, I worked closely with our data scientist to capture issues based on existing data in Google analytics. I contributed to stakeholders and user interviews. Plus, I did a literature review to understand e-commerce best practices and created a task analysis based on research results.
I created low-fidelity wireframes based on our findings in the research phase and moderated user feedback and brainstorming sessions. I then designed the user interface for the entire website using Sketch and created a prototype using InVision.
During the development phase, I was in charge of handing over UI specifications to our third-party vendor using Zeplin. I also contributed to UI testing and provided feedback to developers.
During the evaluation phase, I moderated usability testing sessions and was in charge of analyzing the data and deriving design recommendations accordingly.
I started my journey by using the platform with fresh eyes to have a deeper understanding of the current flow and potential areas of improvement.
Following are some of my initial findings:
Initially, I started by looking at iPerception survey results that we conducted last year at the end of the shopping journey. My goal was to capture both negative and positive feedback from customers to start brainstorming ideas for improvements.
Main findings in the survey include:
To better understand our customers and their issues, I took the lead to conduct several semi-structured phone interviews with the sales team to collect direct input from our customers. Following are some of the main findings (highlighted items are overlapping with survey result) :
I couldn’t tell the difference between RemoteScan enterprise and RemoteScan enterprise user edition, I had to call sales to get a better understanding of the features to make a decision.
Besides, we had a few phone interview sessions with different business unit stakeholders. Our primary goal was to understand the business needs and how we could leverage them with our customer needs and kill two birds with one stone. Here are some of the concerns and needs we identified:
Metrics show over 50% of customers purchasing RemoteScan on shop enter from a generic RemoteScan buy page that does not provide any product content or comparison. We need a solution for this within the shop to insure a clean and informative customer journey to purchase.
I looked into studies that focus on all aspects of designing a smooth checkout user experience from Baymard Institute. This would help me learn from industry mistakes and apply best practices to my design.
Auto-update quantity dropdown as soon as it changes and allow “quantity 0” as a way to delete products
Optimize the number of form fields to avoid checkout abandonment
Minimize the amount of typing by auto-filling form fields & eliminate typos
One page with accordions along with accordion steps collapsing to summaries can help ease of review and edit of order information in checkout
Gain trust by visually satisfying customers security perception of a secure payment
Based on the data we collected we created a task analysis for each customer journey to better understand user pain points when shopping through several channels.
As a team, we conducted a design-studio workshop to come up with as many ideas as we can to solve existing issues. We discussed our ideas afterward and offered critique to each other’s ideas. Similar color notes belong to an individual team member.
I then created an affinity diagram based on our ideas:
I created the following mid-fidelity wireframes using Sketch to share with the team and potential users. At this stage, my primary goal was to focus on the flow and the functionalities rather than visual design.
Hero area displays any new releases or promotions. Customers can filter or search the list to find products. Card view layout used to reduce cognitive load on users for quicker discovery.
Once customers land on this page they can watch a demo about a product or view features on the tour section if they are not ready to buy yet. Key information is shown in a separate paragraph for better clarity.
I've added a dropdown for the licensing option and tagged the recommended option using a different style.
If the product has different editions the user will land on this new page which includes a comparison chart to show different functionalities come with each edition. The goal is to provide a faster way to choose a certain edition based on needs.
I ran an split campaign previously on marketing site using this matrix and got positive result as follows:
Once products are added to the shopping cart, customers would land on this page where they can see the summary of the items they have in the cart and any additional savings they may make based on their items in the cart.
On the checkout page, customers can clearly see how many steps involved in completing their purchase along with a summary of their order. This will create a simplified linear flow. Step 1 will ask for their shipping address.
In the second step, customers will enter their payment information. Based on my literature review adding a padlock icon along with a different background color will improve the security perception of the customers and will help to build trust. I also recommended an interactive plugin for credit card information to avoid errors while inputting the card details.
In this step, customers will review their orders and need to accept the terms and conditions to place their orders. I got rid of the summary box at this stage thinking they have all the information on previous steps present on the page at this point.
I created a click base prototype in Frontify to evaluate the flow. During each evaluation session with users, I explained the task scenario and asked them to speak out loud while going through the flow. I also asked them a few follow-up questions and encourage them to provide feedback.
I've also presented the wireframes to developers and walked them through the process to make sure what we design is feasible to implement. They provided great insights that made me rethink some of the functionalities based on platform limitations and effort required for customization.
Based on the feedback I received I created the following design recommendations:
I created high-fi mockups using a mini style guide from Quest design library (Sketch symbols) applying the recommendations I captured from our evaluation session. I also took the lead to create a prototype for our next revision using Frontify.
Similar to our previous user testing session, I conducted several moderated usability testing sessions with some of our customers. Here are some additional feedback and revisions accordingly:
Customers found it hard to change the filters while scrolling down the listing page. I made the filter area fixed position on the page to make it always available to them while scrolling.
Customers ignored the information related to quantity limitations or other selling conditions regardless of having them in a separate paragraph. Based on the principle of proximity (Gestalt theory) I put this information right below the items they related to.
Most customers ignored the license guide link to view additional information about licensing options & savings and therefore missed the savings. I created a section on the page to display all the options and put the action button below each option to grab their attention.
Customers tried to add multiple editions to the cart and taking them to cart page after adding the item to the cart made them frustrated. I created a dropdown button instead of a default button with the option of:
Or
Since I used Sketch to create all the mockups for this project I exported all of them to Zeplin to hand over the CSS specs to developers along with the final prototype.
The redesign of Quest e-commerce website had a positive impact on the checkout experience and content organization in general. It helped:
However, the conversion rate has not been significantly increased which means we have more things to do. Here are some ideas for future phase improvement: