Design
“A user interface is like a joke. If you have to explain it, it’s not that good.”
I start by trying to empathise with the user: what they are trying to achieve, what gets in the way, and what would make the next step feel clearer.
My development background keeps the work grounded. While shaping a journey or layout, I am also thinking about components, data, validation, responsiveness, and edge cases.
A redesign of my personal site around a sharper UX/product direction, with work on information architecture, visual identity, theme behaviour, and a clearer design and development narrative.
A product concept for tracking job applications, statuses, notes, and follow-ups. The design focus is reducing friction, making progress visible, and helping users manage a tiring process with more clarity.
A review of a customer and account management interface from a usability perspective, looking at how technical workflows can be translated into clearer user-facing screens.
Before thinking about the screen, I want to understand the purpose of the product, the user goal, and the friction that needs to be reduced.
I map the main user flow, the information that needs to appear, and the decisions the interface needs to support.
I turn the structure into screens, components, states, and interactions that are clear before they are visually impressive.
I look for friction, unclear hierarchy, missing states, weak copy, and places where the interface could better support the user.
I want design decisions to start from what the user is trying to achieve, not from what would look good in isolation.
Technical limits, time, data, accessibility, and edge cases all shape whether a design can become a reliable product.
The visual layer should support the user’s understanding. A strong aesthetic is useful only if the product remains readable and usable.