{"id":150,"date":"2024-07-17T04:46:51","date_gmt":"2024-07-17T04:46:51","guid":{"rendered":"http:\/\/katelane.com\/ux\/?page_id=150"},"modified":"2024-07-17T05:32:34","modified_gmt":"2024-07-17T05:32:34","slug":"case-study-cart-checkout","status":"publish","type":"page","link":"http:\/\/katelane.com\/ux\/case-study-cart-checkout\/","title":{"rendered":"Case Study: Cart\/Checkout"},"content":{"rendered":"\n

Project:<\/strong> SquadLocker Cart\/Checkout
Summary:<\/strong> When I started, the SquadLocker app was forcing users into a checkout flow that looked like a totally different site. It didn\u2019t have a cart. It had no transparency about subtotals\/fees\/tax\/charges, making it impossible for the user to figure out how exactly things added up. There weren\u2019t basic standards in place, such as a review step or onsite confirmation post-order. Users weren\u2019t even being asked for things like their billing address, which caused order problems right and left. The interface was buggy and often unresponsive, resulting in users who were not sure whether their order had been placed at all or what was going wrong. It was, in short, a disaster. So I cleaned it up.
My Responsibilities:<\/strong> UX Evaluation, Mockups, UX QA during the build phase
Worked With:<\/strong> Product Manager, Dev team, QA<\/p>\n\n\n\n

<\/div>\n\n\n\n

1. Cart Page<\/strong><\/p>\n\n\n\n

    \n
  • implemented a separate cart page that served as a gateway to the checkout flow<\/li>\n\n\n\n
  • gave users an overview of their items and totals (this was, astoundingly, something that had been missing from the site \u2014 users were presented with a total but it was not broken down with any real transparency)<\/li>\n\n\n\n
  • language clarified: previously, a user who had added multiple colors of the same shirt would be told they had one item in their cart. Item definition was based on product itself, not on the number of product instances. I added the QTY [x] @ [price] = [product subtotal] line to help ease user confusion about how things added up, and we had to come to a company consensus about product vs. item (the warehouse, the product catalog and accounting all used slightly different systems, contributing to the muddle)<\/li>\n\n\n\n
  • moved coupon handling to the cart so users could have an accurate total before they entered the checkout flow. We also had lots of different discount combinations to consider \u2014 for example, shown below is an order that both qualifies for free shipping and is using a 10% off coupon<\/li>\n<\/ul>\n\n\n\n
    \"\"<\/figure>\n\n\n\n
    <\/div>\n\n\n\n

    2. Guest Checkout<\/strong>

    We added a guest checkout option for users who didn’t want to create an account. Previously, we’d been forcing account creation and experiencing a high rate of dropoff and checkout abandonment.<\/p>\n\n\n\n

    \"\"<\/figure>\n\n\n\n
    <\/div>\n\n\n\n

    3. General Streamlining and Evolution<\/strong><\/p>\n\n\n\n

      \n
    • improved the visuals so that the user was unaware that they’d entered a separate part of the site and were now operating within a streamlined flow that minimized distraction (minimal headers and footers in the checkout funnel)<\/li>\n\n\n\n
    • updated and improved the forms<\/li>\n\n\n\n
    • added more options to shipping (smarter dropdowns, PO Box, APO and Canada form shifts)<\/li>\n\n\n\n
    • implemented a stepped flow in the mobile cart so that users weren’t asked to do several things at once on a small screen \u2014 unlike on the desktop, mobile flow presented shipping and payment on separate screens<\/li>\n<\/ul>\n\n\n\n
      \"\"<\/figure>\n\n\n\n
      <\/div>\n\n\n\n

      4. Address Verification<\/strong>

      We added this step (which was missing from the site entirely before).<\/p>\n\n\n\n

      \"\"<\/figure>\n\n\n\n
      <\/div>\n\n\n\n

      5. Error Handling<\/strong>

      We examined error handling and messaging for things like:
      \u2022 fields required
      \u2022 shipping issues
      \u2022 billing issues like incorrect cards and invalid coupons

      Previously, the site would rarely communicate errors, often timing out or becoming completely unresponsive, so this one was a particular triumph for me as far as improved user experience!<\/p>\n\n\n\n

      \"\"<\/figure>\n\n\n\n
      <\/div>\n\n\n\n

      6. Improved Post-Order Experience<\/strong><\/p>\n\n\n\n

        \n
      • implemented appropriate confirmations \u2014 previously users were getting an email but no confirmation within the app<\/li>\n\n\n\n
      • provided users with an order summary, including product thumbnails and subtotals<\/li>\n\n\n\n
      • added an option for authenticated users to look up their order history<\/li>\n<\/ul>\n\n\n\n
        \"\"<\/figure>\n\n\n\n
        <\/div>\n\n\n\n

        7. Account Creation<\/strong>

        Non-authenticated users were invited to create an account. We found that users were much more likely to do this after placing an order than they were at the beginning of the checkout flow.<\/p>\n\n\n\n

        \"\"<\/figure>\n\n\n\n
        <\/div>\n\n\n\n

        In summary<\/strong>, the creation of the cart was a significant improvement to the checkout flow and vastly improved both the user experience and several flows under the hood. As users, we take a lot of e-commerce site behaviors for granted, so it was a relief to implement what has become commonplace functionality within a long-neglected product.<\/p>\n","protected":false},"excerpt":{"rendered":"

        Project: SquadLocker Cart\/CheckoutSummary: When I started, the SquadLocker app was forcing users into a checkout flow that looked like a totally different site. It didn\u2019t have a cart. It had no transparency about subtotals\/fees\/tax\/charges, making it impossible for the user to figure out how exactly things added up. There weren\u2019t basic standards in place, such […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-150","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"http:\/\/katelane.com\/ux\/wp-json\/wp\/v2\/pages\/150","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/katelane.com\/ux\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"http:\/\/katelane.com\/ux\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"http:\/\/katelane.com\/ux\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/katelane.com\/ux\/wp-json\/wp\/v2\/comments?post=150"}],"version-history":[{"count":6,"href":"http:\/\/katelane.com\/ux\/wp-json\/wp\/v2\/pages\/150\/revisions"}],"predecessor-version":[{"id":172,"href":"http:\/\/katelane.com\/ux\/wp-json\/wp\/v2\/pages\/150\/revisions\/172"}],"wp:attachment":[{"href":"http:\/\/katelane.com\/ux\/wp-json\/wp\/v2\/media?parent=150"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}