Skip to content

Earlier work · Custom Point-of-Sale Solution

Service Point Flex

Role
Lead designer
Context
Consulting for one of the top quick-service restaurants
Team
Product owner, business analyst, scrum master, frontend and backend developers, QA engineer
Platform
Android tablet app for 2,000+ franchise owners and operators

Overview & Context

While consulting at one of the top quick-service restaurants, I was the lead designer for an enterprise point-of-sale (POS) solution. The initial solution's primary focus was on sales outside the restaurant and will be used by over 2,000 franchise owners/operators. Eventually, the solution will account for all order creation use cases. Each use case will be supported with its own Android app, and SP Flex is the first in this suite of products.

In the current state of outside sales, the employee is required to manually enter all reporting information once returning to the restaurant. The new solution aimed to remedy this by linking directly to the same servers used by the restaurant, resulting in a truly mobile point-of-sale that could be used anywhere.

Another added business value of the project was to eliminate a dependency on an external vendor. With their own custom solution, it would not only benefit the users but eliminate an unnecessary cost.

Besides myself, the team consisted of a product owner, business analyst, scrum master, multiple frontend and backend developers, as well as a quality assurance engineer.

Getting to Pilot: Surveys & Contextual Inquiry

When I joined the project, the team had already begun developing a solution based on another enterprise tool. Due to this, I knew I had to get up to speed quickly. I researched the current POS solution by looking at existing survey data and set up "field trips" in order to watch employees work in real-time.

The existing data showed redeeming digital offers and gift cards, deferred ordering, and modifying transactions were the most significant challenges using the current POS solution. Another common theme from the data showed an intense desire for simplicity. Operators and employees needed an application that would decrease training time and organize information more intuitively.

I also learned during two four-hour contextual inquiry sessions that users needed something that was extremely fast and reliable. Outside sales employees took great pride in their sales each day, and how it compared to other days they worked. They viewed their distribution point as their own personal business. Lastly, the sessions reinforced the need for increased flexibility while modifying transactions.

After reviewing the data and contextual inquiry sessions, I created my own survey using Google Forms in order to gain more insights.

  • MVP user journeys

    MVP User Journeys

User Journey & Screen Flows

Once I had a clear idea of the current POS solution and the pain points of the users, I began creating screen flows to review with the team. After initially creating user journeys, I learned the frontend developers preferred a more visual way to review flows.

I worked with the project owner to define which flows and functionality needed to be prioritized, and each sprint I collaborated with the development team to build screen flows. Then I reviewed the screen flows with the team either mid-sprint (if I had urgent questions) or during our sprint reviews.

In order to keep the user and business goals in mind during each step, I partnered with another designer to write a mission statement. The mission statement was, "As a Team Member I want to feel confident I can handle any customer order and prepared for any issues during or after the order creation process."

The screen flows helped us make quick decisions as a team and identify key areas that needed further research or user testing.

  • Order creation screen flow

    Order Creation Screen Flow

User Testing

Method

Before piloting the product, I did a testing round in order to reveal possible usability problems. I used Validately to conduct an unmoderated usability test with 5 end users, restaurant employees.

Goals

  • Test the product concept with the target audience. This allowed us to get the most accurate and relevant feedback. Restaurant employees are the primary users so their feedback was prioritized.
  • Reveal friction points and confusing experiences. While we wanted to utilize recognition over recall as much as possible, we also wanted to take the opportunity to make improvements to the current POS.
  • Identify issues with the product. Fixing a problem in development costs 10 times as much as fixing it in design, and 100 times as much if you’re trying to fix the problem in a product that’s been released.

Insights

  • Participants did not always know POS server status was located in Device Settings.
  • Participants had issues finding POS server status below the fold due to low affordance.
  • Participants always tried to select "Scan" before "Pay" when the guest paid with the mobile app.
  • The "Mobile Pay" button text was not clear to all users.
  • Participants expected to be immediately directed to modifier screens when selecting certain menu items.
  • The average SUS score was 92.5!

Recommendations & Action Items

  • Conduct more research on POS server status.
  • Use scrolling affordance on screens with the information below the fold.
  • Ensure scanning QR codes is functional and a priority before payment.
  • Edit the "Mobile Pay" button text to "Mobile App Pay."
  • Take users directly to modifiers for other service selections and future product releases.

Phase One / Pilot UI Design

After user testing, we decided to pilot the application with actual users. We chose to pilot with the Additional Distribution Point (ADP) located at the Support Center. This gave us easy access to gather contextual feedback as we could stop by anytime we liked during lunch two days a week.

In order to release the pilot and gather additional feedback quickly, we decided to have the user take payment off the device using Square. The final goal was to have the user take payment on the device.

As a tablet Android application, the design follows Material Design Guidelines and incorporates the strict brand standards of the client.

Functionality included

  • Cash & Credit Payment (On Separate Square Device)
  • Reward Redemption
  • Manual Text Modifiers
  • Error Reporting / Support
  • Location Settings
  • Printer Settings
  • Pilot home page

    Pilot Home Page

  • Pilot payment flow (off device)

    Pilot Payment Flow (Off Device)

  • Sync pending transactions

    Sync Pending Transactions

Interactive prototype (Figma)
Pilot Payment Prototype

Phase Two UI Design

Phase two of the design focused on giving the user the ability to take payments on the device using the Square SDK. I worked with developers to refine the device setup and payment flow.

Additionally, we introduced Offline Mode, Refunds, and a Quantity Modifier based on feedback from users during the pilot.

Functionality included

  • Mobile App, Cash & Credit Payment (On Device Using Square SDK)
  • Offline Mode
  • Refunds
  • Quantity Modifier
  • Reward Redemption
  • Manual Text Modifiers
  • Error Reporting / Support
  • Location Settings
  • Printer Settings
  • Phase two payment flow

    Phase Two Payment Flow

  • Portrait layout

    Portrait Layout

Phase Three UI Design

The chief goal of phase three was to give users the ability to receive payments on the device, without using Square. The client wanted to eliminate as many third-party vendors as possible.

Additional improvements were also made to Offline Mode based on user feedback. Operators requested the ability to set limits to the number and amount of transactions that could be accepted while offline.

In order to add more flexibility to refunds while at an ADP location, users requested a refund mode where they could select menu items to refund, rather than having to find the previous transaction or enter a transaction number.

Lastly, the vast majority of users preferred landscape, but in order to satisfy the needs of the minority, I added designs for a portrait layout.

Functionality included

  • Portrait Layout
  • Mobile App, Cash & Credit Payment (On Device)
  • Improved Offline Mode - Set Transaction Limits
  • Refunds - Custom Menu Items or Amount
  • Quantity Modifier
  • Reward Redemption
  • Manual Text Modifiers
  • Error Reporting / Support
  • Location Settings
  • Printer Settings
Interactive prototype (Figma)
Phase Three Prototype

What I Learned

Overall this was one of the most professional, enjoyable, and impressive clients to work for. The team I was a part of had some truly brilliant individuals who were not afraid to challenge my designs. Through this project, I learned everyone is a designer, and when everyone is aligned on a specific goal, there is no limit to what the team can achieve.

92.5
Average SUS Score
3
Phases
10+
Field Studies
1
Satisfied Client
“With the right training, I think people would pick this up on the first day.”
Restaurant Employee

See more of my work