47% increase
in album draft to order conversion rate
86% increase
in the number of users who complete & order their album within 24 hours of starting an album
View Full Experience
Visit the website

Company Overview

Birthed as a result of two frustrated wedding guests, Zola.com started as an integrated registry site where engaged or married couples could allow guests to shop several registries, across multiple stores, all in one place. Since its conception in 2013, Zola has since expanded well beyond registry services and has grown into a full, web-based wedding planning platform.

The Zola experience now includes everything from free wedding websites, vendor discovery, and wedding management tools such as a guest address collector and digital seating chart. Aside from specializing in wedding planning, Zola has become a wedding e-commerce giant - selling everything from invitations, wedding bands, and, most recently, custom wedding albums.

Project Specs

  • Team:
    - Kayla Graves (PD)
    - Kemy Lin (Lead PD)
    - Angela Fafard (PM)
    - Emma Skillings (Frontend Dev)
    - Henry Myers (Sr. Developer)
  • My Role:
    - Completing designs for 7 features/improvements
    - Conducting initial user interviews, usability tests, & in-depth competitive research (with the help of Kemy Lin)
    - Completing pre-release design QA for both my and Kemy's features
  • Duration: 10 Weeks
    - 5 Week Design Sprint
    - 5 Week Dev Sprint
  • Platform:
    - Desktop
    - Mobile Web
  • Tools:
    - Figma
    - UserTesting.com
    - Zoom
    - Baymard
    - Google Suite
01 Discover


Zola has become a full wedding ecosystem; but every bride and groom knows the traditions don't end after the DJ spins his last reception track. Realizing the implications of post-wedding traditions and the potential for an additional touchpoint in the post-wedding funnel, Zola decided to provide users with a new, robust nuptial product: custom wedding albums.

Users wanted albums, and they wanted them fast, so the product team quickly cranked out an MVP. However, shortly after launching the MVP, it became clear there were several major pain points and the product was costing the company money. Issues arose relating to everything from order conversion, holes in the overall user flow, and the tech implemented not being up to par. Users were dropping off early in the album customization process and the product pitfalls resulted in a lot of support tickets, credits, an even full refunds.

02 Define

As it became clear (through live-instance metrics and financial reports) Zola Albums had several issues, my teammate Kemy and I set out to find out exactly how users felt those issues could be improved and which were the most frustrating. After all, the technology and internal workflows used to launch Zola Albums was new territory, so we could not afford to fix everything at once nor miss the mark on execution.

After completed a very in-depth competitive analysis, it became apparent we were lacking in several areas; but we didn't find any competitor served as the ideal. We partnered with the business team to pinpoint 7 users to interview, most of whom we could see uploaded photos and dropped off at different points and one user actually ordered and received an album. Kemy and I teamed together to conduct interviews, about an hour long each, via Zoom. These interviews proved to be more valuable than the team could have anticipated, resulting in insights neither us nor our competitors did a great job addressing. We decided to conduct an additional twenty, unmoderated usability tests on the live MVP via usertesting.com.

03 Design

Combining the synthesized insights from our user interviews, user testing, and competitive analysis, the team was able to come up with 6 different user stories, resulting in 6 defined feature sets. I tackled feature sets 1-4, while Kemy tackled 5-6. My overall goals when tackling my 4 sub-projects were to aid user education, manage user expectations, add the ability to make customization edits beyond the landing page, and ensure there was price transparency throughout the customization process.

04 Deliver

As a part of the overall 10 week sprint, I spent 5 weeks designing feature sets 1-4. Once the designs were handed off to engineering, we went through several iterations of both design and technical QA and the features finally went live. The results of these feature updates were almost instantaneous and the team watched in awe as album sales climbed.

Discover

Competitive Analysis

While Zola wishes to be considered a best in class photo album website, it is most definitely not the first. In order to better understand not only what Zola was lacking but  where there were opportunities for us to stand out, we first had to gain an in-depth understanding of the user experience our competitors offered. As a result, I embarked on the arduous journey of creating wedding albums on 10 competitor sites, including, but not limited to: Artifact Uprising, Shutterfly, Minted, & Papier, and compared the experiences to Zola. I quickly felt not only the pain we inflicted upon our happy couples, but the astoundingly frustrating experiences our better-known album competitors provided, which I realized may have pushed customers to try Zola to begin with!

I presented these findings to the team and it was immediately apparent that while we were missing several features, the main areas we were majorly lacking in were user feedback, encouragement, and proactive error handling.

User Research

The competitive analysis gave us a pretty good handle on the what we were missing, but we wanted to talk to couples who had interacted with our existing tool to determine how we would implement. Additionally we needed to ensure we had an answer to the crucial question: why such a high drop-off rate for Zola Albums?

The only way to determine exactly which moments within the album customization flow were frustrating users and why was to speak to them directly. Product partnered with the business team to find 7 users who began customizing a wedding album. All of the users dropped off at different points, and one user actually ordered and received an album. Some of the users interviewed were already a part of the Zola ecosystem, and some had never used Zola products prior to starting an album. We approached writing the script for these interviews looking to answer three concise questions:

  1. Why were some users dropping off immediately after uploading photos before even diving in to customization?
  2. Why were users who uploaded photos and began customizing taking so long to complete the process and order an album?
  3. Why did the user who placed our first album order decide to do so and what did she like/dislike about the process?

Define

Post-Research Game Plan

Many hours of conducting and synthesizing interviews led to 6 core user stories:

Our PM Angela worked to quickly  establish the overall scope and timeline, and Kemy and I excitedly got to work.

Design

Reworking Zola Albums PLP & PDP

Both the PLP (Product Landing Page) PDP (Product Description Page) needed changes; but the PDP seemed to be where most of the confusion and decision fatigue began for our users. By examining funnel drop-off behavior, click rates, time on screen, and heat maps (combined with our in-depth user and competitor research) we could pinpoint several areas for opportunity on both screens:

Deliver

The Final Solution

Insightful Outcomes

Less confusion. Creation to order time decreased. More album orders submitted.

Less Confusion Surrounding Album Options
Adding guidance via social proof callouts and more details surrounding how edits (such as additional pages and changes in material selections) impacted pricing resulted in couples feeling more empowered to make decisions faster and build an album that fit within their budget.
Decrease In Creation to Order Time
Working with development to improve the Album Builder Tool by researching improved auto-photo cropping APIs, reworking the uploaded photo organization tool, and giving couples the ability to edit album style and layout without exiting the Album Builder Tool allowed couples to complete albums faster.
More Album Orders Submitted
Redesigning the album review workflow to include multiple confirmations, an improved album preview, and the ability to easily go back and make changes prior to ordering resulted in more couples getting to the checkout flow and placing an order in significantly less time.
Video Walkthroughs

Future Considerations

While we saw almost instantaneous results and more users coming from outside of the Zola ecosystem, there are some considerations that could have provided an even better experience:

  • A longer project timeline would have allowed development more time to research API's that didn't require such a low threshold for the "low resolution image" flag
  • A non-pdf style review that would allow users to "flip through" album pages
  • A better auto-cropping API that uses a deep learning AI vision model and object detection to detect faces and crop based on relevant objects in the image

This project gave me my first taste of designing for software. I genuinely enjoyed designing beyond standard e-commerce patterns and solving for the multiple complexities that an album builder tool entails - while also providing an intuitive, easy-to-use tool that allows users to build beautiful albums faster..