Blue Nile - Checkout Optimization
Optimizing the checkout path has so far led to a 2% increase in conversion for users in the treatment group. We still have a lot of work to do and this project is ongoing.
GOAL
Optimize the checkout process to reduce effort for the user while gathering the same information, keeping accuracy high and errors low for the user.
We want to incorporate best practices and improve conversion. Keep accessibility at the forefront and ensure optimizations include international customers.
PROCESS
1. Discovery
2. Best practices research
3. Ideate on preferred state
4. Determine a series of MVP features, develop, and A/B test
5. Iterate
DISCOVERY
It had been many years since updates were made to the checkout flow, so I began Discovery by doing a current state exploration and documentation.
To understand the current state, I started by creating a user flow and doing an inventory of components. At this time I also tried to identify obvious opportunities to simplify the flow. For example, I noticed that we had gift messaging on the review page, which felt removed from the area where the user would input the recipients shipping information. There was also an optional customer survey on the review page that prompted the user to enter information just before purchasing. I advised that asking for this information post-purchase could improve the number and quality of surveys received, as well as remove distraction for the user.
2. I also watched numerous checkout sessions using Fullstory to better understand how our users were navigating and interacting within the checkout path. One problem area I began to notice was our Gift Certificate input. I narrowed in on one session where the user was so confused that they called our Customer Service to place the order via phone.
3. To better understand the utilization of the design system and where the checkout path stood as far as consistency, I conducted a visual audit of the obvious form fields, modals, and interactions within the flow. Every page had differences, as no real design system was utilized. There was immense opportunity to get these elements consistent and build trust for the user.
4. After this initial discovery, I went on to conduct more in-depth research so that I could be better informed when beginning to ideate on possible versions of an improved checkout. Several notes from discovery that I wanted to carry through in design were:
Make form fields and related elements consistent
Improve gift card/certificate functionality
Improve gift messaging location
Eliminate or relocate unused or unimportant fields
RESEARCH
While going through the more detailed reports, I started with Baymard’s overview of checkout UX and developed a list of key findings that we could incorporate into the optimizations:
Present “Store Pickup” Within the Shipping Selector Interface (63% of retailers Don’t). Blue Nile currently only has this functionality for internal users.
Make It Easy to Compare “Store Pickup” to Shipping Options (75% of retailers Don’t).
Allow Users to Edit Data Directly at the Review Step (80% of retailers Don’t). Blue Nile has this functionality but it is several extra steps. This could be simplified.
Provide Separate “Edit” Links for All Distinct Information Groups (49% of retailers Don’t)
Avoid Jargon in the Checkout Microcopy (45% of retailers Don’t)
Mark Both Required and Optional Fields Explicitly (85% of retailers Don’t)
Support the “Back” Button for Navigating To Any Previous Checkout View (57% of retailers Don’t)
Auto-Update and Highlight Changes Rather Than Using “Apply” Buttons (82% of retailers Don’t)
Choose the Right Interface Type for Optional Inputs (81% of retailers Don’t)
Use Localized Input Masks for Restricted Inputs (56% of retailers Don’t).
Competitive Analysis
Since I knew I would be addressing the order of elements and the gift card input, I also conducted a few competitive analyses using two direct competitors and several other e-commerce retailers that scored well on the Baymard Institute checkout benchmarks and had smooth checkout flows.
IDEATION
I began ideation by working with the product manager to create a feature prioritization canvas so that we could get started on some A/B Tests and learn from the findings. We identified some smaller updates that the team could quickly begin: improving the address verification modal, applying an input mask to the phone number field, and improving the PayPal redirect by using a PayPal branded CTA.
Meanwhile, I also began working on a prototype of the checkout flow that was more in line with a preferred state. This incorporated more of the best practice research and desired visual consistency updates so that we could have a vision of where we were headed and how to set up tests to get there.
MVP TESTS
Working with the Product Manager and the Checkout Engineering team, we developed a road map of enhancements and tests so that we could test our way into a better experience. We started with a small address verification modal and then worked our way through the various checkout pages with the goal of arriving at a user-validated two-page streamlined checkout.
MOBILE MVP REDESIGN WIREFRAMES
NEXT STEPS/ITERATIONS
The next steps in optimizing this checkout flow could include the following tests:
Update the address entry to a single line address search utilizing Google API so that the user can select their address and avoid any address verification. This will also result in less clicks and entry for the user, as well as cut down on any errors that might involve a customer service follow-up.
Move the gift messaging to the shipping page so that the user can enter all recipient information at the same time.
Research the order information section and improve on how we display the specific details of the purchase and the itemized cost section.
Remove the review page so that the checkout flow now becomes a two-page process and the user can easily view their purchase details as they are entering important information. Conduct more user tests at this stage while A/B Testing to get a better understanding if this layout is better and easier for users.