Open to work Local time in Amman:
العربية

Process // 2026

How I use AI in my design process (and where I don’t)

Lessons from building Rawaa: AI is great for speed and drafts, and bad at deciding what the product should be.

From the project: Rawaa

How I use AI in my design process (and where I don’t)

Where it helped

  • Going wide

    Fast first drafts of layouts so I could compare directions before committing.

  • Testing behaviour

    Turning static screens into a clickable prototype to feel the flow.

  • Scaling the boring parts

    Repetitive, large-scale work inside Figma, like wiring links and fixing overflowing text.

Where I don’t use it

The research, the persona, the design principles and every final call stay with me. Anything AI produces is a first draft, and it only stays in the product if it passes the same principles as everything else.

AI makes confident mistakes: overflowing text, broken links, uneven spacing. Every screen still needs a human review.

My wireframe came first…
…then the final UI, reviewed by hand.

The project behind this post

  • Live prototype
    B2B SaaS · Web + mobile2026

    Rawaa

    A WhatsApp-first loyalty and reputation tool that helps restaurants keep the guests they already won.

More posts

  • Banana
    Process2 min read

    Why I still start on paper

    Pencil sketches from the Banana platform, and why ten minutes on paper saves an hour in Figma.

  • Rawaa
    Product thinking2 min read

    Why Rawaa lives inside WhatsApp

    The biggest decision in Rawaa wasn’t a screen. It was choosing not to build an app for guests at all.

Keyboard shortcuts
Single-key shortcuts

Turn off if you use speech input or find them getting in the way.