The longer version

What can the gaps in a design system tell you? At Al Arabiya I built Atlas, a multi-platform design system in four languages (Arabic, English, Urdu and Farsi), validated in Figma and then ported to GitHub-managed repos via Tokens Studio. The first working model landed in roughly a month, and a year of validation, testing and research matured it from there. Ownership was mine, with support from one other design contributor. Documentation came later than the build, so the developers worked without it for a stretch, and the inconsistencies that surfaced showed which tokens were under-specified. Those are the kind of findings I look for.

I started working in design in 2013, spent 2016 to 2018 in product management roles (Associate PM and PM at JRD Group), and returned to design in 2018. The two years in PM changed how I read product work. What ships first, and what we measure afterwards to know it is working, now arrive as design inputs, rather than as PM concerns: the Atlas advocacy that earned Tokens Studio adoption was a roadmap argument before it was a design argument. The same behaviour runs through my current self-directed work in Claude Code, where projects begin at the roadmap rather than at the screen.

The work I want to be known for sits in decomposing the product problem, visualizing the direction, and orchestrating the execution.

Outside the day job I keep the craft sharp through reading widely, working from external reference, and recent system-building in Claude Code: a multi-agent workspace that runs the design ops for my own brand, and From The Library Of, a passion project where I own the design, the engineering, and the product strategy. I am looking for a senior product design role at a tech-first organization with mature design leadership.