I Design Systems,
Not Screens
Complex workflows, structured thinking, and scalable product decisions.
Built For
Real Outcomes
Improving conversions, reducing operational load, and driving product impact.
Product Designer (March 2024 - Present)
Own end-to-end design for Zenda’s Parent App and School Portal, ensuring a seamless user experience across both platforms. Redesigned the apps from the ground up, built a scalable design system, and contributed to product improvements supporting customer growth across the Middle East and Singapore.
Systems before screens
When a new feature lands on my desk, my first move isn't a wireframe — it's a mind map. Who uses it, how often, what does it touch upstream and downstream, what breaks if it doesn't work right? Only once I can see where something sits in the whole organism do I start designing. By the time I open Figma, flows, constraints, and edge cases are already resolved.
Outcomes over aesthetics
The best interfaces are boring to look at and invisible in practice. Nobody notices them because there's nothing to notice — things just work, reliably, every time. I optimise for the fifth session, not the first impression. What I care about is whether it still makes sense on day 200, when the novelty is gone and the user just needs to get something done.
Human judgement, AI speed
I use AI at every stage — to pressure-test flows, surface edge cases, and generate rough visuals that help stakeholders see how the final product might feel, the way an architect uses a sketch model before building anything real. That's not the finished design. Significant manual refinement happens after. But it compresses the distance between idea and alignment, so my Figma time goes where it actually counts.