Writing
Thinking
out loud.
Design decisions I've made, problems I've worked through, and things I've learned building fintech products at scale. No fluff.
Three UX Problems We Fixed in Collect
Collect is a payment collection app for Indian MSMEs. I designed it from zero. These are three real problems users had — onboarding that died on WhatsApp, a call flow that broke context, and a filter that was missing — and what we did to fix each.
The Onboarding Paradox
Most onboarding is designed to teach users your product. That's the wrong goal. Onboarding's real job is to deliver value fast enough that users don't leave before they've decided whether to stay. The distinction changes everything you build.
The Confirmation Screen Nobody Sees
A confirmation that auto-dismisses is designed for the system, not the user. Our MSME users — jewellers, shopkeepers — are serving customers when they tap an action. By the time they look back, the confirmation is gone. We made it wait, and made it show exactly what changed.
Designing for Users You Haven't Met
Most designers default to designing for users who look like themselves. When your users are significantly different from you — different vocabulary, different devices, different relationship with technology — that default breaks everything. What field research revealed building Collect for Indian MSMEs.
What Users Are Actually Doing on Your Page
Nobody reads your page the way you designed it. The F-pattern, banner blindness, the scrolling myth, and the 50ms first-impression study. What decades of behavioral research actually says about how users read, scroll, and judge interfaces — and what it means for how we design.
The Psychology Laws That Quietly Run Every Interface
Hick's Law, Fitts's Law, Miller's Law, the Peak-End Rule, the Serial Position Effect. These are not abstract principles — they are measurable, replicated findings about how human cognition works. The jam study that produced 10x more sales with fewer options. The colonoscopy study that explains why your confirmation screen matters more than your onboarding. All of it, applied.
I Built a Figma Plugin That Doesn't Need an API Key
Every AI design tool requires an API key. Every designer already has ChatGPT open in another tab. I built DesignGen to close that gap — a Figma plugin that uses browser AI as the engine, with no account, no billing, no API key required.