Namaste 👋 I'm Shankar Shrestha, a UI/UX & Product Designer based in Kathmandu. Give me a messy SaaS dashboard, a dense GIS platform, or an AI tool nobody can explain in one sentence. That's exactly the kind of complexity I enjoy untangling.
A designer who ships, not just decorates
00 / AboutI'm Shankar, a UI/UX and product designer in Kathmandu. For about four years my job has basically come down to one thing: take something messy and confusing, and turn it into a screen that just makes sense. I've done that for AI products, enterprise tools, GIS platforms, and the design systems that keep busy teams on the same page.
Honestly, the early chaos is my favourite part, when nobody's sure what the thing should even be yet. I sketch and prototype to think it through, sit next to the engineers instead of tossing files over a wall, and actually read the research instead of nodding at it. And if I add motion, it's to make something clearer, not to look flashy.
A few problems worth solving
Mero Swasthya
A personal health record app that reads your prescriptions for you.
Kikisapo
A consumer app, storyboard to store.
FastCap
The one number that matters, up front.
LMS
I'm still writing this one up. Check back soon.
Yatra
A ride-hailing app built for how Nepal actually commutes.
Every project here started as a mess of requirements and got shipped as something people actually use.
SSMy product design & UI/UX process
Four phases, always in this order, from a messy brief to a shipped product people can actually use without a manual.
Understand & Research
Before I open Figma, I sit inside the problem: business goals, user interviews, competitor reviews, edge cases, and the constraint nobody wants to say out loud in the kickoff call.
Define & Architect
Then I map the structure: user flows, information architecture, content hierarchy. This is where a pile of requirements turns into a plan someone could actually build from.
Wireframe & Design
Rapid low-fidelity sketches first, to get the logic right cheaply. Then high-fidelity UI, components, tokens and rules other screens can reuse and trust.
Prototype & Hand Over
Interactive prototypes to test the real feel of it, a round of tightening based on what breaks, then a clean, documented hand-over so engineering never has to guess.
Four years, four teams
03 / ExperienceA quick scroll through where I've worked. Tap any role to see what I actually did there.
Let's build something
worth remembering.
I'm open to product design roles and a handful of select collaborations. If you're building something ambitious, especially the kind of problem nobody has fully cracked yet, that's exactly where I do my best work. Drop me a line and let's talk.