Amit verma

Amit vermaAmit vermaAmit verma
  • Home
  • Case studies
    • Meeting summary
    • Metrics
    • Messages
    • Design process
    • Compass
  • Resources
  • About me
  • More
    • Home
    • Case studies
      • Meeting summary
      • Metrics
      • Messages
      • Design process
      • Compass
    • Resources
    • About me

Amit verma

Amit vermaAmit vermaAmit verma
  • Home
  • Case studies
    • Meeting summary
    • Metrics
    • Messages
    • Design process
    • Compass
  • Resources
  • About me

Design process


Understanding the process

Empathize | Define

 

Deeply understand user needs through research and interviews, then synthesise findings into a clear problem statement.


Conduct interviews, observe users, and map pain points. Synthesise insights into a sharp "How might we…" problem statement that anchors everything that follows. 

Ideate | Prototype | Test

Generate ideas, build rough prototypes, and test them with users. The feedback loop arrows show this is non-linear — you cycle back and forth between these steps. 

The loop

What makes this phase powerful is that it cycles. A round of testing rarely ends with "ship it" — it ends with new insights that send you back into ideation. Each loop is smaller and faster than the last: the first prototype might be paper, the third might be a high-fidelity clickable flow. You're converging on a solution through evidence, not intuition alone.

A useful mental model: every prototype is a hypothesis. Every test is an experiment. You're doing science with sticky notes.

Rethink | Refine | Ship

Apply learning to challenge earlier decisions. Polish for edge cases, accessibility, and performance. Ship when the product solves the core problem reliably. 


2025-26

This website uses cookies.

We use cookies to analyze website traffic and optimize your website experience. By accepting our use of cookies, your data will be aggregated with all other user data.

Accept