I design at the system level, not the interface layer. Most product problems that appear as UX issues are structural in origin — a missing governance model, an undefined runtime contract, or a platform boundary that was never formally specified. My work begins below the surface, where those decisions are made.
I analyze SaaS products architecturally: how session state moves across product boundaries, how coordination breaks down in federated systems, how permission models silently contradict the navigation layer. I build formal frameworks to make these structural properties legible — most notably the Invariant Design Language, a specification system for design that must hold under automated execution, not just human review.
Platform-scale work requires connecting design, architecture, and measurable outcomes. I map system dependencies before proposing surface changes. I treat runtime and governance as first-order design concerns — not backend concerns that design defers to engineering. The output is structural clarity: a product that behaves consistently because its constraints are formally defined, not because a style guide says so.
I work with product teams who are building platforms — not screens. If the problem is below the surface, that is where I start.