About
I like the hard problems — the screens with too much data, the flows with too many edge cases. The job is to make those feel simple without dumbing them down, and to leave enough warmth in the details that the thing doesn't read like a spreadsheet. I also build what I design, so the thinking has to hold up in code, not just in a Figma frame.
Structure first — and honest about what I haven't proven.
I start with structure. Before anything gets styled, I want to know what question each screen answers, in what order, and what happens when there's no answer. That usually lands on a simpler layout than starting from a moodboard would — and simpler layouts survive real content.
I also don't invent numbers. Anything untested in my case studies is labelled an assumption — it makes the work easier to argue with, which is the point.
I start with structure — what question each screen answers, in what order, and what happens when there's no answer. That lands on simpler layouts than a moodboard would, and simpler layouts survive real content.
What the business wants and what the user wants rarely line up perfectly. I name where they pull apart before any screen exists — that tension is the thing the design is actually solving.
A layout can look finished in Figma and fall apart when real data arrives — a name twice as long, a missing image. I build what I design, so I catch those while they're still cheap to fix.
The CV has the long version. This is the part worth reading.
Product and e-commerce work, taken from first research call to shipped front end. Most recently a Shopify storefront for a boutique audio-software company — the information architecture, the product template, the visual design, and the Liquid section library underneath it.
Selected: Klein Soundworks · DogFile
[EDIT — two or three lines: what the team did, what you owned, and one specific thing that changed because of your work. Keep a number in it only if you can stand behind it.]
[EDIT — if it wasn't design, say what it taught you that design uses: client work, operations, teaching, support. Career changes read as strength when they're explained.]
[EDIT — degree, course or certification, plus any training worth naming: UX programmes, accessibility, front-end.]
Everything here has shipped something real.
Next
I take on a small number of projects at a time — product work, design systems, or a front end that needs to actually ship. Tell me what you're building and where it's stuck.
Get in touch →
A
na Gj.Senior UX and product designer. I make complicated things feel simple.