← Back to Work
Product ManagementBusiness Analysis

MenuCard — Digital Ordering & Pilot Validation

Restaurant ordering and table-side payments suffered from manual communication friction and slow turnaround times during peak dining periods.

Project Metadata

Verified Evidence
Industry Context
Hospitality Technology
Timeline / Year
2024–2025
JCA Role
Assistant Lead Product Manager
Contribution Lens
Supported
Printed process flow document and gold pen on a warm ivory desk in daylight
01

Organizational Setting

Context

MenuCard was developed to streamline in-restaurant ordering and table payments, eliminating manual ordering bottlenecks for restaurant operators and patrons.

02

The Core Obstacle

Problem

Diners faced delayed service during peak dining hours, while restaurant staff struggled with manual order taking, order entry errors, and fragmented payment handoffs.

03

Research & Investigation

Discovery

  • Contributed to discovery interviews, surveys, and workflow observation with restaurant owners and front-of-house staff across pilot locations.
  • Mapped the end-to-end dining experience from table seating to bill settlement.
  • Contributed to UX research and usability activity, synthesizing pilot feedback from surveys and direct observation.
04

Diagnostic Findings

Analysis

  • Identified ordering latency and bill settlement friction as primary service bottlenecks.
  • Analyzed operational dependencies between kitchen workflow and digital order receipt.
  • Separated core ordering MVP requirements from secondary loyalty and marketing features.
05

Strategic Methodology

Approach

  • Adopted a rapid prototyping and pilot-validation methodology to test digital menu usability in live restaurant environments.
  • Structured iterative feedback loops between restaurant operators and technical delivery teams.
06

Designed Future-State

Solution

  • Contributed to the end-to-end digital ordering flow covering QR code menu access, cart selection, and table payments.
  • Contributed to functional requirements, business rules, user stories and acceptance criteria, including edge-case handling for split payments and offline menu states.
07

Artifacts Produced

Deliverables

  • Business & Functional Requirements, User Stories and Acceptance Criteria
  • UX / Product Flows and User Journey Maps
  • QA Test Participation & Pilot Rollout Guide
  • Pilot Feedback & Measurement Synthesis Report
08

Delivery & Transition

Outcome

Successfully completed and validated the pre-launch pilot across live dining environments. The product had not proceeded to commercial launch as of the evidenced period.

09

Measurable Change

Impact

Validation Status

Pre-launch pilot reached 20+ restaurants and 100+ users, generating 180+ QR scans and 50+ orders. 65%+ of qualified menu sessions progressed to a completed order, with an approximate 40% reduction in average order-completion time across qualified ordering sessions (pilot-reported). These are pre-launch pilot results; commercial launch had not yet occurred.

10

Learnings & Future Iteration

Reflection

Confirmed that real-world pilot validation with live users reveals critical operational edge cases far more effectively than theoretical design reviews alone.

Professional Feedback

What collaborators say about working with me.

Selected professional feedback connected to real working relationships, projects and capability areas.

Temporary / unverified placeholder state

How did this resonate with you?