I chose design because I couldn't stop asking why things work the way they do.
Hi, I'm Himanshi. I'm a Senior Product Designer based in Delhi NCR, and I specialise in making enterprise software feel human.

I've been a creative enthusiast since I was a kid. Long before I knew what design was, I was the kid redrawing logos from cereal boxes and rearranging furniture just to see if the room felt better.
That instinct grew into a career in graphic design. Branding, packaging, illustration. The kind of work where every choice is visible and everything is felt before it's understood.
But at some point, I started asking a different question. Not "does this look right?" but "does this actually work?" That question pulled me into product design, and I haven't looked back.
My first role was at Stayr, a B2B travel startup in Singapore. Sole designer. Two platforms. Founders and engineers on one side, real users on the other, and me in the middle figuring it out as I went. No playbook, no design team to ask. Just the work, and the deadline.
Then came Cyware Labs, and with it, one of the most humbling problem spaces I've encountered. Enterprise cybersecurity. Users who were security analysts, not browsing for fun but tracking real threats, making real calls, on platforms processing 15 billion objects. One confusing UI pattern wasn't an inconvenience. It was a liability. I spent 2.5 years there leading design across threat intelligence workflows, building a system that scaled across six product modules, and quietly cutting customer support dependency by 20%. Not through new features. Through clarity.
Things I've learned
Complexity is a product problem
When enterprise software is confusing, the instinct is to add a tooltip. That just treats the symptom. The real fix is upstream, in the structure of the information or the flow of the workflow.
Trust is a design surface
In AI products, trust isn't a feeling. It's something you architect. Where does the model show its reasoning? What happens when it's wrong? These are design decisions, not engineering details.
Design systems are culture, not code
A design system only works if the people using it understand why it was built the way it was. Adoption isn't a technical problem. It's a question of trust, clarity, and shared decisions.
…and then there's Hiymara.
I built it from nothing. A journaling brand. The products, the identity, the writing, all of it. 600+ units sold, 900K+ organic impressions, an Amazon India expansion in year one, on zero paid ads. It taught me things no job ever could: how to price something, how to read conversion data, how it feels when copy flops and how it feels when a launch lands better than you planned.
When I'm in a room with a PM anxious about a deadline or an engineer questioning scope, I'm not just nodding along. I've been that person. I know what it costs to make a call with incomplete information.
The graphic design roots, the enterprise systems work, the brand I'm still building: they look like different things. But they're the same curiosity, just applied at different scales.
What I care about
Clarity over cleverness.
The best solutions feel obvious in retrospect. The goal isn't to impress. It's to remove friction so quietly the user never notices it was ever there at all.
Honesty over comfort
I'd rather surface a concern early than stay quiet to keep the peace. The best product decisions come from people who trust each other enough to push back.
Depth over
speed
Time spent understanding a problem well always saves more time downstream than it costs upfront. I move fast, but never before I know what I'm solving.