About
I make complexity feel inevitable.
Senior Product Designer, 5+ years in — turning ambiguous problems into interfaces people don't have to think about.
0
Shipped products led end-to-end
0
Active users on a single 0→1 launch
0
Average cut to time-on-task
0
Years in product design
How I think about the work
I care about how something looks — but just as much about how it functions, how it scales, and whether it still makes sense six months after launch.
Most of the projects I take on aren't blank slates — they're products that have outgrown their original assumptions and need someone who can untangle that without starting over.
Based in Lahore, Pakistan — working with teams worldwide.
Principles
Think beyond the screen
A good interface solves a business problem, not just a usability one. I start with what the metric needs to move, then work backward into the screen.
Stay close to the build
Design that never touches engineering reality tends to fall apart at handoff. I stay close enough to the implementation to know what I'm actually asking for.
Move fast, stay clear
Speed without communication just creates rework later. I'd rather ship a rough version with the reasoning attached than a polished one nobody understands.
Own the outcome
I measure success by what happened after launch, not what shipped. If a metric didn't move, that's still my problem to solve.

Background
How I got here
TODO: Write 2–3 short paragraphs on your actual path into product design — the problem that first hooked you, the kinds of teams and products you've worked on, and what's stayed consistent across them. Specifics (companies, industries, turning points) land better than general claims.
Download full résumé →Working together
What it's actually like to work with me
Direct collaboration
No account managers, no game of telephone. You work directly with the person actually doing the design.
Fast feedback loops
Regular check-ins over big-bang reveals, so you see direction early enough to redirect it cheaply.
Flexible setup
Embedded in your team's tools and rituals, or running independently — whatever the engagement actually needs.
Long-term thinking
Decisions that hold up after I'm gone: documented reasoning and systems, not just one-off screens.
Have a problem worth solving?
Let's build something people actually use.
I read every message myself, and reply within a day or two.