Skip to content

Under constructionIf something looks broken, that is a bug and not a bold design choice. Tell me at munawarkhel@gmail.com.

( Contact )

Tell me the symptom, not the solution

A symptom is something you can point at: what people do outside the software, what takes longer than it should, what has already been redesigned once without fixing it. Start there and the first reply will be about your product rather than about a process.

munawarkhel@gmail.com

Open to remote, hybrid, on-site, contract, and relocation opportunities globally. Based in Karachi, Pakistan.

( Roles I am open to )

  • Lead / Senior Product Designer
  • Lead / Senior UI/UX Designer
  • Product Design Consultant (contract or fractional)
  • UX Generalist / Design Systems Lead
  • AI Product Designer / Agentic Interface Designer
Phone
+92 321 924 8464
WhatsApp
wa.me/923219248464
LinkedIn
linkedin.com/in/munawarkhel
Dribbble
dribbble.com/munawarkhel
X
x.com/munawarkhel
Facebook
facebook.com/munawarkhel
Upwork
upwork.com/freelancers/~01efd95cfa9295d9bc

( The first message )

It reaches my inbox with your address as the reply-to, so a reply lands with you.

( Where I start )

  1. 01

    Observed behaviour

    What do people actually do, as opposed to what they say?

  2. 02

    Domain

    What world is this, and what do the words in it mean?

  3. 03

    User needs

    Which of those behaviours point at something worth fixing?

Three of seven, and all three are still the problem space. The rest, and what each one produces, are on the process page.