ALL WORK

LVL 05 — MCDELIVERY

From ‘what should I eat?’ to ‘order placed.’

Simplifying the path from browsing and customisation to checkout and order visibility.

ROLE
Product Design
TIMELINE
Historical project · timeline not listed
PLATFORM
Mobile
TEAM
Cross-functional team · details not listed
DOMAIN
Consumer
Pixel-art illustration of a delivery scooter with food and an order tracker
CONCEPTUAL PIXEL-ART ARTWORK — NOT AN ORIGINAL PRODUCT SCREEN. REPLACE WITH APPROVED PROJECT SCREENS.

01 / CONTEXT

The problem

Food ordering needs to support quick browsing, confident customisation and an efficient path to purchase.

02 / TENSION

The challenge

Keep choice useful without letting menus, options and checkout steps slow down a high-intent task.

I know I'm hungry. Help me get to food quickly.

03 / PROCESS

The approach

DESIGN FOCUS — THE WORKFLOW BELOW SHOWS THE INTENDED PATH THROUGH THE PRODUCT.

  1. 01Browse
  2. 02Choose
  3. 03Customise
  4. 04Cart
  5. 05Checkout
  6. 06Track
  • Content hierarchy
  • Customisation
  • Cart clarity
  • Checkout efficiency
  • Post-purchase visibility

04 / RATIONALE

Key decisions

DECISION 01

Make browsing scannable

Why it mattered
Users often begin with appetite, not a precise item name.
Design response
Use clear categories, familiar product cues and concise choices.

DECISION 02

Keep customisation understandable

Why it mattered
Options can quickly create uncertainty about the final item and price.
Design response
Show selections, constraints and price changes in one place.

DECISION 03

Treat tracking as part of checkout

Why it mattered
The need for clarity continues after payment.
Design response
Maintain a visible order state from confirmation to delivery.

05 / EXPERIENCE

The experience

KEY CONSIDERATION — VISUALS ARE CONCEPTUAL PLACEHOLDERS, NOT ORIGINAL PROJECT SCREENS.

Pixel-art illustration of a delivery scooter with food and an order tracker
PLACEHOLDER ARTWORK — REPLACE WITH APPROVED PROJECT SCREENS.

06 / OUTCOME

Opportunity

OUTCOME DATA WAS NOT PROVIDED FOR THIS PROJECT.

This case study documents the design focus and intended experience without making claims about measured results, stakeholder feedback or usability findings.

07 / REFLECTION

What I would revisit today

Validate how returning users balance speed, repeat orders and discovery across different ordering contexts.