Testimonials
What teams say afterwards
Quotes are attributed by role rather than by name. Clients get referenced publicly only once they have agreed to it in writing — which is the same courtesy I would want.
He asked harder questions in the kickoff than we had asked ourselves in three months of planning. Half the features we thought we needed never made it into the design, and the product is better for it.
Our engineers stopped filing 'what happens if this is empty' tickets. Every state was already designed and annotated. That alone took a week out of the sprint.
The usability sessions changed our roadmap. Watching five people fail at the same step was more persuasive than any deck could have been.
We had a design system on paper. He turned it into something the team actually uses — components with rules, not a colour palette in a slide.
He stayed through the build. When our implementation drifted from the design he flagged it with specifics and a screenshot, not a vague complaint.
Clear communication, delivered on the dates he gave us, and explained every decision in language our non-technical stakeholders understood.
Recognition
Published work & milestones
Where the work lives publicly, and the moments worth marking.
Portfolio published on Behance
2023 — presentOngoing case study and UI showcase collection, updated as projects clear client approval.
ViewShots published on Dribbble
2023 — presentInterface explorations, interaction studies and design system fragments.
ViewPromoted to Senior UI/UX Designer
2024Moved from associate to senior in under two years, then took design ownership of 100+ product surfaces at 724.ONE.
What to expect
The things clients mention most
Consistent themes across feedback — worth knowing before we start, so you can hold me to them.
Questions before pixels
The kickoff is uncomfortable on purpose. Better to find the disagreement in week one than in week seven.
No surprises on dates
If something is slipping you hear it the week it starts slipping, not the week it was due.
Engineers are not an afterthought
Feasibility gets checked while designing. I would rather change a screen than hand over something expensive to build for no user benefit.
Decisions come with reasons
Every meaningful choice arrives with the problem it solves and the option it beat. You can disagree with the reasoning — that is the point of showing it.
Feedback gets absorbed, not defended
It is your product. My job is to make the best case for a direction, then get out of the way of a decision.
It ends when it ships
Design QA on staging is included in every engagement. Adnan is still around when the release lands.
Want to be the next one of these?
Tell me what you are building. If it is a fit, you will get a scoped proposal within a couple of days.
madnansakhi@gmail.com