Achieving a 100% adoption rate on the Guest Migrations feature at Lunchbox

Achieving a 100% adoption rate on the Guest Migrations feature at Lunchbox

Achieving a 100% adoption rate on the Guest Migrations feature at Lunchbox

Achieving a 100% adoption rate on the Guest Migrations feature at Lunchbox

The building blocks of a restaurant loyalty program, Guest Migrations allow a restaurant to carry over their guest list and points information from an external loyalty provider when they deploy to Lunchbox Loyalty. As the lead product designer, I led a cross-functional team effort to reduce friction and improve the error handling experience

The building blocks of a restaurant loyalty program, Guest Migrations allow a restaurant to carry over their guest list and points information from an external loyalty provider when they deploy to Lunchbox Loyalty. As the lead product designer, I led a cross-functional team effort to reduce friction and improve the error handling experience

The building blocks of a restaurant loyalty program, Guest Migrations allow a restaurant to carry over their guest list and points information from an external loyalty provider when they deploy to Lunchbox Loyalty. As the lead product designer, I led a cross-functional team effort to reduce friction and improve the error handling experience

Achieving a 100% adoption rate on the Guest Migrations feature at Lunchbox

The building blocks of a restaurant loyalty program, Guest Migrations allow a restaurant to carry over their guest list and points information from an external loyalty provider when they deploy to Lunchbox Loyalty. As the lead product designer, I led a cross-functional team effort to reduce friction and improve the error handling experience

Objective

Make it easy for Onboarding team users to fix guest migration error uploads, track status of their uploads, and clearly know what is acceptable file formatting

Make it easy for Onboarding team users to fix guest migration error uploads, track status of their uploads, and clearly know what is acceptable file formatting

Problem

Error-filled migration lists were continually being uploaded, at the cost of the Onboarding team spending days per week to troubleshoot and manually find errors, creating hiccups in customer loyalty programs going live

Error-filled migration lists were continually being uploaded, at the cost of the Onboarding team spending days per week to troubleshoot and manually find errors, creating hiccups in customer loyalty programs going live

Time frame

May – Jun 2024

May – Jun 2024

Personnel

Product Manager

Engineering Team

Onboarding Team

Product Manager

Engineering Team

Onboarding Team

Objective

Make it easy for Onboarding team users to fix guest migration error uploads, track status of their uploads, and clearly know what is acceptable file formatting

Problem

Error-filled migration lists were continually being uploaded, at the cost of the Onboarding team spending days per week to troubleshoot and manually find errors, creating hiccups in customer loyalty programs going live

Personnel

Product Manager

Engineering Team

Onboarding Team

Time Frame

May – Jun 2024

Macbook showing new dashboard design
Macbook showing new dashboard design
Macbook showing new dashboard design
Macbook showing new dashboard design
Macbook showing new dashboard design

Business Objectives

Business Objectives

Business Objectives

Business Objectives

Business Objectives

Business Objectives

Lunchbox was investing in larger bets and needed to be ready to onboard larger enterprise clients. Moving up market would require greater efficiency and better solutions with less errors and quicker completion times

Lunchbox was investing in larger bets and needed to be ready to onboard larger enterprise clients. Moving up market would require greater efficiency and better solutions with less errors and quicker completion times

Lunchbox was investing in larger bets and needed to be ready to onboard larger enterprise clients. Moving up market would require greater efficiency and better solutions with less errors and quicker completion times

Sweet, Sweet Insights

Sweet, Sweet Insights

Working within the time constraints, I used a combination of surveys and user interviews with several folks from the Onboarding team (the core user) to gather insights for the redesign. Key takeaways included:


  • Users were spending several hours a week troubleshooting file errors

  • Most of the time spent on migrations was figuring out why a file failed

  • Uploading was confusing (there was only 2 file statuses; uploaded or failed)

  • There was a general distrust of the new admin dashboard

  • The correct formatting that’s needed from a file wasn't clear

Sweet, Sweet Insights

2 people speaking on google meets video call
2 people speaking on google meets video call
2 people speaking on google meets video call
2 people speaking on google meets video call
2 people speaking on google meets video call
2 people speaking on google meets video call
Old dashboard design with annotated callouts
Old dashboard design with annotated callouts
Old dashboard design with annotated callouts
Old dashboard design with annotated callouts
Old dashboard design with annotated callouts

Design Audit & Building a Hypothesis

Design Audit & Building a Hypothesis

I had Onboarding walk me through the process of how they currently were uploading a migration file on the old dashboard. The entire process was recorded for further team review and ingested via Dovetail.

I began with a hypothesis that by a) helping users better understand what is needed for a file upload, b) providing actionable help for navigating upload errors, and c) by better displaying file upload status, we could reduce error troubleshooting time spent by the Onboarding team and improve the experience.

Table showing score results from interviews
Table showing score results from interviews
Table showing score results from interviews
Table showing score results from interviews
Table showing score results from interviews
Table showing score results from interviews

User Desires & Success Metrics

User Desires & Success Metrics

User Desires & Success Metrics

User Desires & Success Metrics

User Desires & Success Metrics

Tracking baseline customer rating scores and following internal stakeholder meetings to surface pain points, we had a clear idea of what the Onboarding team desired:


  • Clear CSV file acceptance criteria

  • Track file upload progress easily at a glance

  • Know exactly why a file upload failed

  • Modern user interface and experience

  • Ability to search/filter for past migrations

After defining the MVP with the team and defining phase criteria, I brainstormed with my PM on how we could determine success for this project: we ultimately decided on tracking 3 key things – adoption rate, error task completion time, and customer satisfaction scores.

User Desires & Success Metrics

CONFIGURATIONS LEAD @ LUNCHBOX • OLD DESIGN

CONFIG. LEAD @ LUNCHBOX • OLD DESIGN

CONFIGURATIONS LEAD @ LUNCHBOX • OLD DESIGN

CONFIGURATIONS LEAD @ LUNCHBOX • OLD DESIGN

Just improving this error handling and helping empower others would save me hours per week… people wouldn't have to rely on me for migrations!

Just improving this error handling and helping empower others would save me hours per week… people wouldn't have to rely on me for migrations!

Just improving this error handling and helping empower others would save me hours per week… people wouldn't have to rely on me for migrations!

Just improving this error handling and helping empower others would save me hours per week… people wouldn't have to rely on me for migrations!

Just improving this error handling and helping empower others would save me hours per week… people wouldn't have to rely on me for migrations!

Engineering Constraints

Engineering Constraints

Engineering Constraints

Engineering Constraints

Engineering Constraints

Engineering Constraints

The backend wouldn't allow for multiple file uploads to occur simultaneously; it was too taxing and costly! We would have to find a solution that would seamlessly allow for one file upload at a time, without adding too many steps or bogging the user down

The backend wouldn't allow for multiple file uploads to occur simultaneously; it was too taxing and costly! We would have to find a solution that would seamlessly allow for one file upload at a time, without adding too many steps or bogging the user down

The backend wouldn't allow for multiple file uploads to occur simultaneously; it was too taxing and costly! We would have to find a solution that would seamlessly allow for one file upload at a time, without adding too many steps or bogging the user down

Insight #1: Users were frustrated by the lack of file statuses

Insight #1: Users were frustrated by the lack of file statuses

Solution: The upload system needs to keep users updated on exactly what is happening.


We created new statuses to clearly label what stage a file was in to deliver a reliable and predictable experience, and to ensure accessibility, buttons were aligned with the strictest WCAG standards for contrast ratios. To improve upload visualization, we introduced a progress bar complete with upload percentage, which users loved!

Insight #1: Users were frustrated by the lack of file statuses

New button designs and file upload progress status bar
New button designs and file upload progress status bar
New button designs and file upload progress status bar
New button designs and file upload progress status bar
New button designs and file upload progress status bar
New button designs and file upload progress status bar
Closeup of Download CSV template button
Closeup of Download CSV template button
Closeup of Download CSV template button
Closeup of Download CSV template button
Closeup of Download CSV template button
Closeup of Download CSV template button

Insight #2: Users weren’t sure what’s needed from a file

Insight #2: Users weren’t sure what’s needed from a file

Solution: What could we create that doesn’t require any backend changes? We came up with the idea to have a downloadable CSV template that would have all the headers correctly formatted so information would be parsed without hiccups.

Users really liked this simple addition that served a couple purposes – it was a training tool for those new to handling migration uploads, but it was also a helpful resource that Onboarding could share with clients to educate them on how the CSV files should be formatted (or if they needed a refresher themselves). A win-win!

Solution: What could we create that doesn’t require any backend changes? We came up with the idea to have a downloadable CSV template that would have all the headers correctly formatted so information would be parsed without hiccups.

Users really liked this simple addition that served a couple purposes – it was a training tool for those new to handling migration uploads, but it was also a helpful resource that Onboarding could share with clients to educate them on how the CSV files should be formatted (or if they needed a refresher themselves). A win-win!

Insight #2: Users weren’t sure what’s needed from a file

Insight #3: The backend would only allow one file injection at a time

Insight #3: The backend would only allow one file injection at a time

Insight #3: The backend would only allow one file injection at a time

Insight #3: The backend would only allow one file injection at a time

Insight #3: The backend would only allow one file injection at a time

Solution: Working with the constraints provided earlier from Engineering, we were able to solve for the use-case when a user has multiple files loading into the system at the same time.


To reduce stress on the backend, we would allow multiple files to be able to "pre-verify", but only allow one file at a time to inject into the database.

Insight #3: The backend would only allow one file injection at a time

Closeup showing multiple files uploading to the dashboard
Closeup showing multiple files uploading to the dashboard
Closeup showing multiple files uploading to the dashboard
Closeup showing multiple files uploading to the dashboard
Closeup showing multiple files uploading to the dashboard
Closeup showing multiple files uploading to the dashboard
Tool tip showing more information about a file upload status
Tool tip showing more information about a file upload status
Tool tip showing more information about a file upload status
Tool tip showing more information about a file upload status
Tool tip showing more information about a file upload status
Tool tip showing more information about a file upload status

Insight #4: The layout was confusing and didn't help users easily find a file

Insight #4: The layout was confusing and didn't help users easily find a file

Insight #4: The layout was confusing and didn't help users easily find a file

Insight #4: The layout was confusing and didn't help users easily find a file

Insight #4: The layout was confusing and didn't help users easily find a file

Solution: The layout should highlight essential elements while reducing clutter. We added the file name and file icon to each respective upload, new headers to identify what status a file was in (with a tool-tip for further details) and a file search and sort via status/date functions.


Users really liked these changes as this helped them reduce scrolling and speed up the search in the case that there were multiple file uploads over time, and – instead of just a long list of uploads, the new design improved the hierarchy to give a clearer overview of all file upload statuses at a glance.

Insight #4: The layout was confusing and didn't help users easily find a file

Insight #5: In the case of a failed upload, users weren’t sure how to resolve that file

Insight #5: In the case of a failed upload, users weren’t sure how to resolve that file

Solution: The upload system should provide guidance and actionable steps to help users diagnose errors.


In the instance that a file has errors preventing its upload, we provide an overview of the general formatting errors, how to fix them, and the ability to download the error log for a closer look on what went wrong.

Insight #5: In the case of a failed upload, users weren’t sure how to resolve that file

Error dialog for a failed file upload
Error dialog for a failed file upload
Error dialog for a failed file upload
Error dialog for a failed file upload
Error dialog for a failed file upload
Error dialog for a failed file upload

The Finished Product

The Finished Product

After a few rounds of usability testing and revisions, we arrived at the final approved direction and the onboarding team immediately started putting it to use.


A few features/ideas that weren’t in the MVP but came up through user feedback and were implemented:

  • The ability to cancel and delete migrations

  • Progress loader for upload visualization

After a few rounds of usability testing and revisions, we arrived at the final approved direction and the onboarding team immediately started putting it to use.


A few ideas that weren’t in the MVP but came up through user feedback and were ultimately implemented:

  • The ability to cancel and delete migrations

  • Progress loader for upload visualization

Image showing 100% adoption rate of the design from the onboarding team
Image showing 100% adoption rate of the design from the onboarding team
Image showing 100% adoption rate of the design from the onboarding team
Image showing 100% adoption rate of the design from the onboarding team
Image showing 100% adoption rate of the design from the onboarding team
Image showing 100% adoption rate of the design from the onboarding team

Takeaways

Takeaways

Takeaways

Takeaways

Takeaways

Tracking the success metrics we set early on, we were excited to see that post-launch, we had achieved an adoption rate of 100% by the Onboarding team! Other key wins included:


  • 39% reduction in error task completion time – the new file validation flow catches errors early in the upload process and guides them through error resolution; users spend less time overall troubleshooting files!

  • Increased customer ratings – surveys reported strong gains in ease of use, trust, and feelings of innovation in a cross analysis scoring of the old design vs. the new design

  • Team members felt more empowered – through the new CSV template button and the error log help, the team is able to take troubleshooting matters into their own hands

Takeaways

Just improving this error handling and helping empower others would save me hours per week… people wouldn't have to rely on me for migrations!

CONFIGURATIONS LEAD @ LUNCHBOX • OLD DESIGN