I designed and built websites for clients worldwide.
Front-end development, visual design, changing content, and real handoffs taught me how products behave outside the mockup.
I design products by figuring out the system first.
- Designing workforce systems at TCP.
- Studying design at BNU.
- Reworking this portfolio one page at a time.
I'm Ahmed, a product designer in Lahore. I started in code and found my way into design. I design complex products by understanding their workflows, rules, and edge cases, then turning them into clear interfaces.
The work starts before the screen.
Before I draw a screen, I want to know what people are carrying in their heads, where the work changes hands, and what breaks when the happy path ends. I use research and prototypes to make one useful change at a time, without throwing away what already works. I studied computer science, and it helps me understand how a product is built. I am studying design, and it helps me question whether it should work that way.
I began designing around workflows, ownership, and systems.
One collection case moved through calls, spreadsheets, and several teams. I designed for continuity: what happened, who owns the work, and what comes next.
I improve complex products one useful change at a time.
I work with years of rules and customer habits. Research, systems, interface craft, and code help me make the next change clearer without forcing customers to relearn everything.
Different products. The same urge to look underneath.
Debt collection, time clocks, analytics, and food all hide a lot of rules. I like finding the thread and making the next step easier to understand.
I brought case work, calls, follow-up, and reporting into one debt collection platform.
Read case study
I redesigned a shared Android time clock for frontline workers. The work covered fast taps, gloved hands, bright spaces, low-spec hardware, and a component system the Android team could build.
Read case studyA freelance product design project for a self-serve analytics tool. I designed the path from spreadsheet upload to chart building, dashboards, and sharing.
Read case study
A Fall 2025 course project exploring how AI could interpret incomplete menu information without pretending it knew more than it did.
Read case study
How I work
I work from the problem outward.
I find where the work gets stuck, understand what surrounds it, then test the smallest useful change.
I ask where the work gets stuck.
The brief tells me what the team wants. The people doing the work show me where the real problem lives.
I map the boring states.
Permissions, empty screens, errors, and old rules are rarely the exciting part of a project. They are often the part that makes it believable.
I build before I am comfortable.
A working prototype exposes the awkward questions a polished frame can hide. I use code when it helps me reach those questions sooner.
I stay after the handoff.
I want to see what changes in the build, what engineering discovers, and what real use proves wrong. The Figma file is not the finish line.
I keep the rules within reach.
The UX laws, heuristics, and principles I use are printed and displayed on my desk. When I work through a problem, I look at them and ask: what am I missing? Is there a simpler way to help? Am I making the interface harder to use?
Read my notesSay hello.
Reach out if you are hiring for product design, working through a complex workflow, or trying to make an old product easier to change. I like problems that need patient thinking and practical design.
hello@ahmedqureshi.com