Popeyes UX Case Study

Christopher Barajas
Popeyes UX Case Study
8 min readJun 12, 2020

The following are the results of a 10 week project course in Human Computer Interaction at the University of California, Irvine. Students Christopher Barajas, Aleen Kiledjian, Matthew Alen Olitoquit, and Anqi Zhong all collaborated on evaluating and redesigning a prototype of an interface of their choosing.

Love that chicken from Popeyes!

Project Summary

Popeyes is a mobile application used for ordering food for take out or delivery from the restaurant. For those unfamiliar with the Popeyes corporation, they specialize in fast food fried chicken and some of their most popular dishes consist of chicken, tenders, chicken sandwiches, and Cajun-style side dishes. While we would agree that Popeyes food is rather enjoyable, their mobile app is everything but.

Our goal was not only to identify key user experience issues within the app and suggest methods of improvement but also to determine the reason that drives the user base to download and use restaurant specific mobile applications. We accessed both direct and indirect competitors of Popeyes to determine the features that incentivize users not only to use such restaurant specific applications, but to return to them frequently. Doing so allowed us to correct UI/UX limitations and suggest improvements within the app for a more streamlined and enjoyable user experience.

High Level Objectives

Before conducting any research, we came up with 4 high level objectives to help guide us:

1. Understand the purpose of people downloading restaurant-based mobile applications

2. Explore the user experience of using fast food mobile applications created by the restaurant industry

3. Recognize the features that incentivize people to download an application from a specific business

4. Detect possible flaws or limitations in an interface that may drive the user away from using the app

User Stories/Interviews

In order to get an understanding and identification of our user base, we conducted interviews with 8 users and surveys with 20 users of restaurant-based applications. These mobile applications weren’t specific to Popeyes and the data gathered here was meant to be a general overview of the habits of our user base. Interview questions were created to answer our high-level objectives. Some example questions revolve around asking users about their eating habits, preferences, and experiences with food service mobile applications. Our main takeaways from interviews:

1. Third party applications have the upper hand when it comes to ordering food online.

2. Customizing online food orders is important.

3. 80% of consumers are more likely to download food applications when incentivized to do so.

4. Main reason for ordering delivery or take-out is convenience.

Additional Data

Respondents’ willingness to download an application due to the reward program. Strong results indicating reward program incentivizes customers.
Respondents’ level of confidence on navigating websites and applications. All of them are at some level of confidence.
Number of restaurant based mobile applications respondents have used within the past six months. Only 5% have not used any of these applications. Should be noted that 90% of our respondents are within the 18–24 years old age range.

Personas

Based on our user interviews and surveys, we created various personas that are fully research-based and data-driven. Here are two:

Usability Testing and UX Evaluation

We used both remote user testing and a heuristic evaluation to help identify usability issues and concerns in the Popeyes app. 5 participants were involved in the remote user testing activity and were each given 7 tasks to complete. These tasks were believed to be the main functions of the app and would help discover possible usability issues:

1. Searching and viewing the menu on the Popeyes mobile app

2. Search for the “trending” section of their application

3. Looking for the nutritional information of a specific dessert item

4. User adjusts the visuals of the application to cater to their preferences when performing a task.

5. Exploring the menu without signing in

6. Ordering from the application

7. Finding the contact information link for web and app support

We used 4 metrics to measure participant success per task:

1. Time

2. Number of clicks

3. Completion rate

4. Number of errors

Pain Points/Usability Issues

The first impression of the Popeyes mobile app was mostly positive but usability testing made it clear that most of the participants had a negative user experience when having to navigate the interface. Participants felt the application was frustrating to navigate through compared to previous experiences with other food ordering applications.

One notable example of this is the difficulty experienced in simply locating the menu within the application. Only 40% of the participants believed searching and viewing the menu was easy and 20% agreed they could predict where it was located. More pain points and usability issues are as follows:

1. Lack of User Control

It’s very clear that Popeyes lags behind competitors as the mobile application lacks a simple back button that allows them to undo their actions. It’s mind boggling to us that such an application lacks a basic universal need.

2.Poor Visibility of System Status

Users seemed to have difficulty tracking their location when searching and viewing the Popeyes food menu. Because of the aforementioned lack of a back button, users often became confused in routing and rerouting themselves through the interface.

3.Difficulty in Finding Critical Information

4 out of 5 participants said that they could not accurately predict the location of various menus during tasks, most notably, the Popeyes food menu. It should be noted that all of our participants had some level of confidence in navigating mobile apps and yet the most important part of the app is not easily accessible.

4.Overbearing Design

The home menu of the Popeyes application presents itself as a long list of information that is just repeated on other menu options creating immediate redundancy. Users are immediately presented with unintuitive and repetitive design.

Solution

It was finally time to start sketching. We prioritized reducing redundancy within the application, adding a cart option to maintain visibility of system status, and most importantly made the Food Menu a clear distinguishable tab on the navigation bar. Oh, and we added a back button…

Compilation of all group members’ sketches

Prototypes/High Fidelity Mockups

After comparing individual sketches, we combined ideas and agreed upon designing consensus sketches that reflected the targeted change best.

Pictured from left to right (top) Target 1, Target 2, and Target 3. Pictured from left to right (bottom) Targets 4 and Target 5.

Before working with a final product, mid-level prototypes were created that consisted mostly of wire framing our targets.

Target 1 — “Reduce Redundancy”
Target 2 — “Add the Cart” part 1
Target 2 — “Add the Cart” part 2
Target 3 — “Group nutritional information, offers, and menu together”
Target 4 — “Redesign Sign In / Sign Up”
Target 5 — “Redesign Order interface”

Finally, we used Figma to develop high fidelity mockups of our proposed solutions. Due to time constraints, these prototypes have not been yet tested on users. Below are the mockups of the final solutions:

Target 1: Reducing redundancy by removing unnecessary information on the home menu and adding “Menu” to the navigation bar.

Target 3: Relocate nutritional information on the same page with the corresponding dish and make this information more organized and neat. Grouped the Offers information, nutritional information and menu together.

A “Menu” button on the bottom navigation bar redirects users to a menu interface that also contains nutritional information and mobile exclusive offers.

Target 2: Adding a cart option to make current system status clearer.

We wanted to add a cart button that was visible on all every page within the application. The original application displayed a visible icon showing only the total price of the cart, but our redesign below shows the amount of items in the cart, similar to what can be found on shopping websites. However, we added a feature to our design that changes the process: holding down the button will pop open a window that shows the item, price, and nutritional information that users can interact with.

The screenshot below displays the redesign target of adding a cart button, which can be pressed and dragged to be positioned anywhere where the user finds most comfortable for their experience. The Menu feature is also implemented on the navigation bar

Target 4: Redesigning the sign up/sign in page. We made the email as optional for creating an account. User has the option to receive verification code through email or phone number. If they choose to sign in via text message verification, the app will be using Apple’s built in iMessages functionality, which allows the user to remain on the same page, simplifying the signup process.

First image shows email as optional. Second image shows the sign in interface, user can sign in via verification code.

Target 5:Redesigning the Order interface and taskbar option. We renamed it as Locations for better understanding and put the List and Map choice together so the user can find the options for how they want to view the search results right away. We also made the change decision for the search result to present all the restaurants, from closest to farthest, so the user would know where the closest restaurant is. We made the same change to the map view, which will present all the restaurants on the map.

Making the taskbar “List” and “Map” more visible. The search result will display all the restaurants, from closest to farthest.

Takeaways/Reflections

We set out on our journey primarily to understand the needs and behaviors behind those who use restaurant based mobile applications. One particular thing that stood out was these application’s reward systems that incentivized users to continuously use these applications and return to said restaurant. Originally, we thought including this feature in the Popeyes would improve both the functionality and user experience of the application.

After conducting usability testing, we scrapped this idea to focus on fixing the smaller and more important details in the app, rather than adding a completely new one to the existing clutter. Sometimes a change as small as adjusting navigation bar layouts or a larger change such as a revamp of the information architecture/layout can make a significant difference in the usability of a product.

--

--