EasyEat Self-Ordering Kiosk

EasyEat Self-Ordering Kiosk

A kiosk experience designed around speed, clarity, and scalable restaurant operations.

kiosk cover

Context

  • Company: EasyEat Indonesia, a company that supports restaurant operations including POS systems, QR orders, inventory, purchasing etc.

  • Existing system: QR-based self-order (customer scans, orders from phone).

  • New product: Kiosk — a physical, stand-alone ordering point in the restaurant.

  • My role: Product Designer, competitor researcher.

  • Scope: Competitor research to pilot design.

  • Collaborated with

    • Product

    • Engineering

    • Business/merchant stakeholders.


Problem Map

Three merchant problems drove this, each with a different reason to adopt:

Merchant Problem

Who this is for

Evidence

Long queues at peak hours

High-traffic outlets

We observed that the restaurant had a high volume of customer orders while they had a limited number of cashiers.

No cashier, cut labor cost

Small/medium merchants

Several merchants have operations running without a cashier, they only put 1-2 people as maker and server. This scheme is usually used in small stores with a takeaway system.

Need to scale operations consistently

Enterprise merchants (multi-branch)

Due to the long queues, we wanted to provide another platform to open more ordering channels without adding new manpower for cashiers.


Why a kiosk?

EasyEat already supported QR-based self-ordering. The kiosk introduced a second self-service channel for customers who may not want to use their own phone.

Current self-order ecosystem
Expected to extend the self-order ecosystem

The goal wasn't to create another ordering experience. It was to extend the existing ordering ecosystem into a new physical context.


Discovery & Competitive Research

At this stage, direct merchant and usability research was not available. I therefore used competitor analysis, existing EasyEat behavior, business requirements, and platform constraints to establish the MVP direction.

Competitor audit: McDonald's and IKEA kiosk systems.


McDonald's

IKEA

EasyEat opportunity

Navigation

✓

△

Simple hierarchy

Customization

✓

△

Easy customization

Confirmation

△

✓

Reduce unnecessary steps

CTA visibility

✓

△

High contrast

First-time user

✓

△

Guided flow

Repeat user

✓

✓

Fast path

Common opportunities found across both:

The opportunity wasn't to copy either kiosk. It was to combine their strengths while removing the friction we identified.

Design principles set from this research:

  • Low cognitive load, speed, and clarity first

  • Customization should be easy to reach, not buried

  • Cut unnecessary confirmation screens

  • Strong CTA contrast for touchscreen readability

  • Flow must serve both guided (first-time) and quick (repeat) users.


Design Decisions

1. Mirror the existing QR ordering flow

  • Problem it solves: #1, #2, #3 — all three merchant problems depend on customers trusting and completing orders fast, on any device.

  • What I did: Kept the kiosk flow structurally identical to the existing QR ordering platform, same step order, same menu logic, same payment step, instead of designing a new pattern.

  • Why: A customer who has ordered via QR before should feel zero relearning switching to the kiosk. It also let the kiosk reuse the platform's existing backend and data, no new API needed.

2. MVP feature set kept tight

  • Problem it solves: #2, #3 — cashier replacement and scalable operations both depend on a flow merchants can trust without extra complexity at launch.

  • What I did: Locked MVP to promotions (banner + recommendation), dine-in/takeaway selection, item customization, online payment, and promo code entry.

  • Why: These directly map to the research-backed principles (speed, clarity, easy customization) without adding scope that wasn't validated yet.

3. Button size and placement based on standing posture

  • Problem it solves: #1, #3 — queue speed depends on how fast a standing user can find and hit the right action; scalability depends on the design working for a broad range of users (age, height, tech familiarity) across many outlets.

  • What I did: Set primary action buttons to 88×88px, with 44×44px as the accessibility floor for any smaller controls. Placed key actions (Add, Proceed, Pay) in the center-to-bottom zone of the screen, where a standing user's eyes and hands naturally land, not top of screen.

  • Why: A kiosk is used standing, at arm's length, often mid-decision different ergonomics from a seated mobile/desktop screen. Eye line falls center-to-bottom, not top-down like a phone. Bigger targets in that zone cut mis-taps and hesitation, which directly shortens time per order, the core lever for reducing queues. 44px follows WCAG/Apple-Google accessibility minimums, so users with less precise motor control aren't excluded.


Reasoning chain:

  1. Physical constraint, kiosk is used standing, at arm's length, mid-decision. Eye line lands center-to-bottom, unlike a phone's top-down scan pattern.

  2. Consequence, if key actions sit outside that zone or are too small, users hesitate or mis-tap, adding seconds per order.

  3. Design response, 88×88px primary buttons placed center-to-bottom; 44×44px as the accessibility floor for secondary controls, following WCAG/Apple-Google minimums.

  4. Link back to business problem — fewer seconds per order compounds across peak hours, which is the actual mechanism behind reducing queues (#1) and behind the flow holding up consistently across many outlets and user types (#3).

Three features were scoped in early, then intentionally held back from MVP:

  • Customer membership, held to keep the checkout flow lean at launch.

  • Table number input, held; not essential to place a valid order at this stage.

These weren't dropped outright, they're deferred, pending more requirement-gathering after the MVP is in the field. Cutting scope here kept the first release focused on proving the core flow works, not on covering every edge case upfront.


Conclude MVP Features

Order Page
Cart & Payment Method
QR Payment and Success Feedback


Validation

Merchant-facing validation had not yet taken place at this stage of the project. Design decisions were grounded in competitor research and alignment with existing platform behavior rather than direct testing. Merchant and usability validation is planned as a follow-up step once the MVP is deployed.


Outcome

What was delivered

MVP product direction

The kiosk experience aligns with the existing EasyEat ordering ecosystem, expanding business opportunities and helping restaurants extend their ordering touchpoints.

Problem

Solved by

Queue length

Decision 1 — familiar, fast flow

Cashier cost

Decision 2 — lean MVP scope

Scalability

Decision 1 — reuse of existing ecosystem data

The kiosk had not launched by the end of my time on this project. This case study reflects the research-to-decision stage of the work; quantitative impact isn't available yet, and the outcome will depend on the merchant pilot once it ships.

Create a free website with Framer, the website builder loved by startups, designers and agencies.