Approach

I’m the designer you bring in when a system is too complex, too important, and too public to get wrong.

For 8+ years I’ve worked where complexity, scale, and real consequences meet — government platforms used by millions and enterprise products with demanding workflows. My strength isn’t visual polish. It’s simplifying complexity, aligning stakeholders, and turning ambiguity into measurable outcomes.

I care most about the systems people are required to use and can’t opt out of — where good design quietly removes friction from someone’s day, and bad design quietly costs them.

How I operate

Most of my work happens before anything reaches a screen.

01
Diagnose the structure before the surface.
Before I touch a screen, I map the system — its entities, sequence, and incentives — and look for the part that shouldn't be there. On tangled products, the fix is usually taking something out, not adding more.
02
Align on “good” before pixels.
With competing stakeholders, I get a shared definition of success on the table first, so later decisions have something to resolve against. A lot of design debates are really disagreements about goals nobody wrote down.
03
Make the trade-offs explicit.
I'd rather be proven wrong by the research than win on taste. So I bring it into the room along with the cost of doing nothing, say plainly what we're trading off, and let the evidence take some of the heat out of the hard calls.
04
Build with the people who'll live in it.
Engineers, domain experts, and real users shape the work as it goes. I validate against the hardest cases — the least margin, the worst connection — because if it holds there, it holds everywhere.

The path here

From craft, to leading public systems at national scale.

Over a decade I’ve gone from interface craft to owning design for systems millions of people rely on. The pattern has been fairly consistent: the harder and more public the problem, the more it pulls me in.

Now

Manager, UX & Interface Designer — Digital India Corporation (MeitY)

Owning end-to-end design for national public platforms serving 500k+ citizens — securing leadership buy-in for UX strategy and building design systems and accessibility into civic infrastructure.

2024–25

UX Designer — Ministry of Finance (DPE), via NetProphets Cyberworks

Led the redesign of six core departmental applications to a mandated government identity standard (DBIM), working alongside NIC teams and developers.

2022–24

UX Designer → UX Lead — MelpApp (Sysmind Tech Pvt. Ltd.)

Rose from designer to lead, managing a team of 5–6 and driving B2B product UX with product, engineering, marketing, and data.

2017–22

UX & Interface Designer — Ceekr

Led research, hiring, and stakeholder alignment across web and mobile products in the wellness and self-development space.

2014–17

Interface & Graphics Designer — Studio Mosaic, Diam Resources

Built the craft foundation across 16+ web and mobile projects — including onboarding and booking flows with the Yatra team.

None of it counts until it ships.

Each case study is one of these decisions under real constraints — what I reframed, what I traded off, and what actually changed.

See selected work→Or start a conversation

I’m the designer you bring in when a system is too complex, too important, and too public to get wrong.

I care most about the systems people are required to use and can’t opt out of — where good design quietly removes friction from someone’s day, and bad design quietly costs them.

Most of my work happens before anything reaches a screen.

Diagnose the structure before the surface.

Before I touch a screen, I map the system — its entities, sequence, and incentives — and look for the part that shouldn't be there. On tangled products, the fix is usually taking something out, not adding more.

Align on “good” before pixels.

With competing stakeholders, I get a shared definition of success on the table first, so later decisions have something to resolve against. A lot of design debates are really disagreements about goals nobody wrote down.

Make the trade-offs explicit.

I'd rather be proven wrong by the research than win on taste. So I bring it into the room along with the cost of doing nothing, say plainly what we're trading off, and let the evidence take some of the heat out of the hard calls.

Build with the people who'll live in it.

Engineers, domain experts, and real users shape the work as it goes. I validate against the hardest cases — the least margin, the worst connection — because if it holds there, it holds everywhere.