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

I am a product designer who works closest to the problem. The work I do best happens where domain complexity and user reality pull in opposite directions - where the product has to carry expert-level logic without requiring expertise to operate.

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

What that environment actually meant: 10+ person team. No design manager. Requirements that arrived as compliance framework references, half-finished stakeholder notes, and regulatory PDFs. Every major UX decision - what to build, how it should behave, what to sacrifice when usability and regulatory correctness conflicted - was mine to make and defend.

How I work

I start by reading the domain before I open Figma. When you are designing for chemical supply chains or ESG reporting frameworks, the fastest way to make bad decisions is to treat the brief as complete. I write decision logs - what I ruled out and why - before I ask engineers to build anything. Those logs have saved weeks of rework and, more than once, caught an assumption that would have broken something downstream.

My strongest decisions have come from noticing what is wrong in the structure of a problem, not just its surface. At Carboledger, we could not run direct user interviews - GDPR and SOC II compliance constrained how we could capture or store user data. So I worked with anonymized session recordings, sometimes watching a single session on repeat until the behavioral pattern surfaced. One user kept stalling at the same point in a flow. It was not confusion about the feature - they were losing the thread of what they were doing when the page navigated away. The fix was opening the flow in a new tab so the original context stayed intact. No new feature. No redesign. Just understanding how someone holds their attention, and designing to match it.

I also build. Cursor, Vercel v0, and AI prototyping tools have made it possible for me to validate ideas before they reach engineering. That habit has consistently helped me make sharper calls about what is worth building at all.

What I am looking for

I am looking for founding designer or senior product design roles at early-stage B2B companies - particularly in AI, compliance, supply chain, or any domain where the product has to carry real complexity without making users feel it. I want to be the person who defines the product's UX direction, owns the hard trade-offs, and builds the design foundation a team will grow on top of. Not someone who inherits a system and populates it.