I design systems that make
complex, regulated products
usable by non-experts.

I am a product designer who thinks in systems. My strongest work happens at the intersection of domain complexity and user clarity — where the product has to handle expert-level logic while being operated by people who are not experts in that domain.

For the past [X] years, I have been the first and only designer at Carboledger — an early-stage B2B SaaS platform for sustainability compliance and carbon data management. I joined when the product had no defined UX direction. I left that ambiguity with 11 interconnected platform modules, structured supplier response workflows, a role-based access model that encoded regulatory accountability into the product experience, and a contribution analysis tool that cut expert analysis time from half a day to under an hour.

What that environment actually meant: 4-person team. No design manager. No design system inherited from a previous team. Requirements that arrived as compliance framework references and vague stakeholder notes. Every major UX decision — what to build, how it should work, what trade-offs to make against regulatory constraints — was mine to own. That is what "founding designer" means in practice.

How I work

I learn by wrestling with real complexity, not by waiting for well-formed requirements. I read domain documentation before I open Figma. I write decision logs — what alternatives I ruled out and why — before I ask engineers to build anything. I treat session recordings and user conversations as primary data, not decoration.

My strongest design decisions have come from noticing what is broken in the structure of a problem, not just in its surface. The alias system at Carboledger looked like a naming problem. It was four problems: cognitive recall, record-keeping consistency, data searchability, and supplier power dynamics — all requiring different solutions held simultaneously in one data model.

I also build. I use Cursor, Vercel v0, and AI tools to prototype and test ideas without waiting for engineering cycles. That has consistently helped me make better, faster decisions about what is worth building at all.

What I am looking for

[Placeholder — Describe the type of company and role you want. Example: "I am looking for founding designer or senior product design roles at early-stage B2B SaaS companies — particularly in AI, compliance, supply chain, or regulated domains. I want to be the person who defines the product's design direction, not someone who inherits it."]