Process — Priya Gupta

My Process

Design that starts

with a diagnosis.

Most designers start with wireframes. I start with a

hypothesis. Every project begins by understanding what's broken —structurally, not just visually — before a single frame is drawn.

This approach means slower starts and faster endings. Fewer revisions.Decisions that hold up six months later.

Diagnose

Understand the problem before touching the UI.Break down requirements, user needs, and constraints. Use ChatGPT and Claude to explore edge cases, clarify gaps, and structure thinking.Every decision starts with a clear diagnosis.

Problem framing

User flows

AI exploration

Edge cases

Define

Turn insights into a clear solution direction.Map flows, define features, and structure interactions.

Leverage UX Pilot along with AI agents to validate patterns and refine logic.Focus on what to build—and why.

Flow mapping

Feature definition

UX patterns

Strategy

Design

Translate structure into UI.
Use Stitch to generate layout directions, then refine in Figma.Prioritize clarity, hierarchy, and usability over decoration.
Every screen should reflect the defined solution.

Figma

Layout systems

Components

Prototyping

Validate

Test against the original problem.Check if all requirements, features, and edge cases are covered.Use AI for critique and iteration where needed.Ensure the solution is complete, usable, and effective.

Review

Iteration

Usability

Completion

Principles

What drives every decision

Clarity over decoration

A polished UI can’t fix a broken structure.I define the problem, map the system, and use AI tools like ChatGPT and Claude to remove ambiguity before designing.Strong foundations drive good design.

Invisible execution

Good design feels effortless.
I use AI-assisted thinking and structured flows to reduce friction—so users complete tasks without thinking about the interface.

Decisions with reasoning

Every design choice is intentional.
From AI-assisted exploration to final UI, decisions are traceable to user needs, constraints, and logic—not guesswork.

System thinking

I don’t design screens—I design systems.Using tools like UX Pilot and Figma, I ensure consistency, scalability, and patterns that hold across the product.

Validate, not assume

Design isn’t finished at delivery.
I validate against requirements, test edge cases, and use AI for critique to ensure the solution actually works.

Design within constraints

Time, scope, and engineering limits are real.I use AI to explore possibilities—but design solutions that are practical, buildable, and aligned with reality.

In Practice

From a simple idea to a scalable system

Virtual Waiter started as a simple product — allowing users to book resort seating, order food & beverages, and access amenities.Over time, the product expanded with layers like inventory, service providers, and dynamic offers.

As complexity increased, the system became harder to manage and less intuitive for staff. This is where my process came in — understanding the system, identifying gaps, and bringing structure to make it clear, usable, and scalable.

Turning growing complexity into a system that’s easy to understand and operate.

How I approach it

UNDERSTAND

Started with the core — seating, food, and amenities.

TRACK THE CHANGE

Noticed how inventory, providers, and offers added

complexity.

SIMPLIFY

Connected the system and clarified how everything

works together.

IMPROVE

Made the experience easier to use and manage at