NDA Note: Screens, data, and names have been anonymised per client agreement.

TL;DR

Clunky ERP → Mobile-First Operational Suite
I redesigned a barely-usable restaurant ERP into a streamlined mobile-first product that:

• replaces 17-step modal-heavy flows with in-context, linear UX

• allows owners to go from sign-up to order in under 10 minutes

• reduces support dependence, rework, and time-to-first-order across the board

1. What Was This App, and Why It Needed a Redesign

🔹 The Original App: Good Vision, Poor Execution

The application aimed to provide a full-suite ERP for restaurants — managing menus, printers, staff, taxes, dining areas, and receipt printing.
But it was:

• Built for a few specific clients, and lacked a generalized version

• Filled with nested modals and contextless forms

• Lacked visual structure, leading to error-prone usage

🔹 My Redesign Mission

The client hired me (solo freelance) to:

• Identify and dissolve friction points across the app

• Redesign only what was broken — which were a few, but needed to be fixed

• Deliver a mobile-first product that supported real-time kitchen workflows

2. My Role & Collaboration

3. What Were the Real Problems? (and My Diagnosis)

This was not a feature-enhancement job. It was about uncovering why the app wasn’t usable at all. My approach: use the product like a first-time owner, log friction, and fix holistically.

A small clip of how it was in earlier design to add a menu item.

4. Personas & Environment Considerations

Persona	Needs	Frictions I Designed Around
Restaurant Owner	Set up quickly and bill same day	Was overwhelmed by multi-tab setups
Kitchen Staff	Avoid getting involving too much into using application	1 click actions flows
Waiter/Runner	Faster Order taking and actions.	Long confusing flows

In this particular part of redesign focus was on "Restaurant owner" who would be taking managerial decisions and setting up menus and dining areas etc. on the application.
The "First-Time user experience (FTUE)" was focused on to get more users onboard.

5. Redesign Framework (How I Worked)

1. Discover

   Used the app daily to log friction points; audited competitors like Petpooja, also tried being a Restaurant Owner on "Magic Pin", "Zomato" to understand how they manage Item Listing

2. Define

   Collaborated with client on their feature map; mapped feature → data structure → UI need

3. Ideate

   Sketched flows on Escalator; tested bottom nav vs object-model nav (settled on latter)

4. Design

   Created full atomic system (tokens → atoms → molecules); components built for reuse.

Color Pallet

Font variation

Color pallet into variables	Text elements into variables	Numbers into variables
Using color variables to make color tokens	Using text element tokens to make text Styles	Number variables to make Padding and margin tokens

5. Validate

   Shared clickable Figma prototype with client → tested with their restaurant network → logged usability concerns

Find and run a Prototype on this link here.

6. Solving the Toughest Challenge: Menu Builder

The original flow:
To add 1 dish (e.g. "Paneer Tikka Large + Extra Cheese") required:
→ Create Menu → Add Section → Open Modal → Add Item → Add Variant → Separate Modal → Add Add-on → Assign Add-on

17 modal jumps. No context. Users gave up.

✅ My UX Fixes

7. Results & Business Impact

"Our evening crew went live in one shift. No 10pm panic. That’s a first." — Owner

8. Key Screens & Interactions

9. What’s Next (and Already Happening)

10. Reflection

“I wasn’t just designing a UI—I was dismantling every barrier between a restaurant owner and their first live order.”

• Friction mapping > Feature adding

• Designing for chaos, not calm: real kitchens don’t wait

• Learned how token systems + component libraries de-risk development at scale

• Stakeholder involvement = faster alignment, fewer revisions

11. Credits