UX Portfolio

Continente Online Checkout

By João Telo · 15 October 2020
Continente Online Checkout
Methods
Empathise, Define, Ideate, Prototype, Test
Tools
Axure RP
Timeline
2014, checkout upgrade

Continente is the largest retailer in Portugal and Continente Online is the company's e-commerce website. Due to its multi-store nature and wide range of products, in 2014 the Continente Online checkout needed an upgrade to provide a more intuitive and efficient user experience, while delivering more functionalities required by customers and business.

Empathise

— E-commerce stores benchmark, with similar and different businesses.
— Customer support contacts, either suggestions or complaints, to identify and understand pain points.
— Web analytics data, to understand the user shopping behavior.
— Customer journey mapping with the full website flow, core metrics and pain points.

Define

Point of View — Problem Statement (dummy data used for illustration)

UserNeedInsight
A customer with a full time job and two young children. To fill the pantry with food and buy medicines without prescription for his children. He doesn't know food and medicines have different lead times until the checkout delivery page, generating dissatisfaction and abandonment.
An executive that travels quite often and buys all his clothes, shoes, electronics and groceries online. To buy his groceries quickly to fit this task in his busy schedule. He expects the site to remember his usual options, like payment method and delivery address, to keep the checkout precise and efficient.
A customer that follows weekly promotions and has a tight budget. To know how much money she can save with the loyalty card coupons. Knowing which products have a coupon and how much she can save makes her feel more confident about her choices.

Ideate

"How Might We" questions

— How might we inform customers about different lead times before and after adding products to the cart?
— How might we improve the checkout to make it more efficient and quick?
— How might we turn the order sum parcels easier to comprehend?
— How might we highlight the advantages of the loyalty card?
— How might we improve the loyalty card coupons selection and benefits?
— How might we provide an easier way to select payment methods and use loyalty/gift card balance?
— How might we improve the order submitted page to give relevant information and options?

Brainstorming and challenge assumptions

The brainstorming technique was used multiple times to gather new ideas and challenge assumptions — whenever possible we talked with team members or other departments who knew these topics better, and questioned whether we could follow another path. Most of the time we found the initial assumptions didn't hold, or the experience could be improved.

Sketches

I can't show the dozens of sketches that were made on paper and whiteboard, but this was crucial to explore better solutions and approaches that wouldn't work further ahead, before starting to prototype.

Checkout sketch

Prototype

Typography and color

Trebuchet MS font Color palette

User flow

Although the main focus was the checkout, we wanted to test the prototype with real customers. This way, to put the user in context, we needed a product grid page, to allow adding products to the cart before moving on to the checkout. After submitting the order, customers could also check the order confirmation email and order detail page in the account.

Checkout flow

Prototyping

Axure RP was the tool of choice because I needed to build a fully functional cart and checkout for desktop (the site was not responsive at the time). These were the requirements for the prototype:

— A working cart and checkout that calculates totals as products are added, removed, or changed, and coupons and loyalty/gift card balance are applied.
— Order summary shown throughout the checkout.
— Delivery detail: single or multiple shipments, delivery method (address or pickup point), address creation and selection, delivery slot selection, loyalty card association.
— Payment: loyalty coupons, manual coupons, loyalty/gift card balance redeem, payment method selection, saved cards, billing address.
— Checkout confirmation summarizing products, delivery and payment.
— Order submitted page with confirmation link, pickup point map, calendar add, and NPS rating.
— Orders history and order history detail.
Axure prototype Watch the Axure prototype walkthrough →

Test

We tested the prototype during days with real customers, in a one-way mirror lab, recording screen and audio, and using eye-tracking technology to measure eye movement while interacting with the prototype. I attended all the usability tests, making real-time changes to fix issues pointed out by users and testing them again with the following customers.

This prototype was also used as a deliverable to the development team, making it a lot easier to understand the requirements and specificity of some interactions. Despite the high complexity of this checkout process, development went smoothly. After development, I made extensive usability tests to guarantee the final experience followed the defined requirements.

End result

In the end, customers had a better understanding of all the options and order values, and quicker access to the core options of the checkout, providing a more efficient, trustful, intuitive, and pleasing buying experience. Since the deployment, we saw a big improvement in customer satisfaction, a substantially higher conversion rate, and a reduction of the time spent on the checkout pages.

This project was very challenging but really satisfying:

— In Empathise, I did the benchmarks, gathered all the web analytics data, contributed to the customer journey construction, and analyzed the data to understand our customers and their problems.
— In Define, I worked with my area manager to identify the core problems and needs of customers and business.
— Ideation was mainly done with my area manager, across dozens of sessions, with paper/whiteboard sketches whenever needed to test feasibility.
— Prototyping was all done by me — a very complex prototype with dynamic data and dozens of variants across multiple pages.
— Testing methodology was defined by market research; my role was to clarify doubts during tests and implement fixes.
— After delivering the prototype to development, my role was to clarify doubts for the tech team and test after go-live.