In short.
Curiosity about how things and systems work drives most of what I do. My instinct is technological - I reach for whatever lets me build solutions, from a CNC machine and a 3D printer to Figma and code - and I’m as comfortable in the workshop as in the browser. Across every discipline, the aim is the same: take something complicated and make it make sense, and make it well.
What I do.
I work across disciplines rather than inside one. The common thread is a hands-on, technological approach - reaching for whatever tool builds the idea best.
Data Visualisation & Information Design
Making complex data navigable for people who aren’t specialists. Turning dense datasets and technical literature into visual systems you can read, explore and trust - drawn in Illustrator, then built interactive in code.
Web Design & AI-assisted Development
Designing and building interactive sites end to end - HTML, CSS and JavaScript, with AI as a collaborator rather than a crutch. The approach behind both this site and thenuclearquestion.com.
UX / UI & Interaction Design
Apps and interfaces built around how people actually move through them. User journeys, flows, wireframes and prototyping in Figma - from a productivity app to interactive data tools.
Product & Industrial Design
Where I trained, and still how I think. Physical objects from lamps to speaker enclosures - modelled in Rhino and Blender, then made real with CNC machining, 3D printing and hands-on fabrication.
Brand & Communication Strategy
The professional thread: positioning, narrative, market research and paid media, from brand-strategy work at Big Fish and others. The same instinct - shaping how something is understood - from a different angle.
Approach.
I start by understanding the thing itself - the system, the problem, how it works - before designing anything around it. Research first, opinions second. From there I dive in headfirst, reaching for whatever technology the problem demands: a CNC router, a 3D printer, Figma, an AI coding agent. I’d rather build a rough prototype and learn from it than theorise, and a tool I’ve never touched is a reason to start, not a reason to stop.
- Research first
- Understand the system before designing for it.
- Build to learn
- Prototype early with whatever the work needs - CNC, 3D printer, Figma, AI.
- Translate, don’t decorate
- Make the technical legible, not just pretty.
- Add meaning, not clutter
- Improve people’s lives rather than adding to them.
Beginnings.
I didn’t arrive at design the usual way. I studied History, Art History and Maths, spent a foundation year at the City & Guilds of London Art School, and only then found product design at IE University in Madrid. That detour is the point: it taught me to see design as something that sits inside the world - history, systems, people - rather than floating above it. Somewhere along the way, an interest in technology and AI turned a product designer into a multidisciplinary one.
Writing.
Alongside design, I write about technology, communication and how complex subjects reach a wider audience - what makes a message clear, credible and honest. It started with my thesis on nuclear energy and is turning into something ongoing.
Read the writing →Colophon.
This site was designed and built by me, with AI as a collaborator rather than a crutch. It’s built with Astro - component by component, no template and no page builder - its WebGL hero and 3D work hand-written in three.js, the layout and interaction iterated through Claude, version-managed on GitHub and deployed on Cloudflare Pages. The images are my own work, served at full resolution.
I built it this way on purpose. AI has lowered the barrier for designers working close to technology, and this site is one small proof of it: hand-built rather than dropped into a template, every decision still mine. That’s exactly the point I’d want a portfolio to make.
Contact.
Got a role, a project, or just want to talk about design? Drop me a line.
Download CV ↓