[ Strategic Thinking ]COMPLETED

Dishcision.

From craving to cuisine.

Project

Dishcision

Type

UX/UI Mobile App Design

Role

Product Designer

Duration

1–2 months

The Framework

01 — What I Observed

Urban professionals open 3+ food apps before deciding what to eat. Decision fatigue is real. No platform helps users decide what to eat only where to order.

02 — What I Questioned

Why does every food platform start with restaurants? Users think need-first. Need → Dish → Best way to have it.

03 — What I Changed

Decision-first experience. Two paths per recommendation: Make at Home or Find Nearby. 5-tab IA. Food Passport for exploration not calories. MVP scoped deliberately: no delivery, no reservations, no calorie counting.

04 — What Happened

Validation ongoing. Early testing shows reduced decision time and increased dish exploration. Future scope mapped: Leftovers Meal Planner, Smart Recipe Scale-Down.

The Story

The problem: users don't lack food options. They lack confidence in choosing the right one.

The insight: every food platform is restaurant-first. Users think dish-first. That gap is the product.

Key decision: MVP scope cut deliberately. One job help users decide what to eat today.

Research: 10+ users. JTBD framework. Empathy mapping. Primary persona: Rahul, a busy professional who repeats meals out of convenience and wants to eat better without the overwhelm.

Feature prioritization: MoSCoW method. Must have / Should have / Could have / Won't have.

What this proves: a product built on a clear insight, with deliberate scope decisions, full IA, two user flows, and a validation plan.

Design System