Arnab Mathur

How I work

How I work beyond screens and designs

I tend to start with the system behind the screen: who is involved, what can happen, what constraints exist and where the process can break.

  1. 01

    Understanding the system

    I start with the people, business rules and workflow behind the interface.

    Where you can see it

    RinovaWhat the platform is forDeepamDesigning for both sides of the bookingTractoThe architecture
  2. 02

    Define the states

    Before designing screens, I map what can happen, who owns each step and what happens when things go wrong.

    Where you can see it

    RinovaA shared review experienceRinovaDesigning for partial failureDeepamDesigning for failure
  3. 03

    Make decisions explicit

    I document trade-offs so product, design and engineering can understand why something works the way it does.

    Where you can see it

    TractoThe decision behind "no streaks"RinovaChoosing where the loan is sanctionedTracto4 rules I set before designing
  4. 04

    Design for the build

    I hand off states, components, behaviours, edge cases and interactive prototypes rather than just static screens.

    Where you can see it

    RinovaWhat the developers built againstDeepamOne provider system, three specialised appsDeepamWhat changed after the client's review
  5. 05

    Using AI in my workflow

    I use AI for research preparation, sample data, exploration and a second pass on my thinking. Product decisions still come from the problem, the people using the product and the team building it.

    Where you can see it

    RinovaWhere I used AIDeepamWhere I used AITractoWhere I used AI
See the case studies Experience and background

Need someone to make a complex product easier to use? Let's talk.

Email LinkedIn Behance