I design and ship enterprise experiences where UX decisions must align with engineering realities, from ML configuration workflows to token automation pipelines. I turn structural complexity into usable systems that scale across teams and codebases.
I've spent 25 years building and shipping complex digital products, leading UX strategy at Bidtellect, designing ML-powered workflows at Viant, and writing the front-end architecture that underlies both. I'm most effective at the boundary where design decisions and engineering constraints intersect, turning those constraints into systems that scale.
Based in Delray Beach, FL. Currently UX Designer at Viant, where I own end-to-end design for technically constrained enterprise products. I integrate AI workflows, data-driven research, and design system governance into how I work, not as add-ons, but as core practice.
Restructured ML configuration to enforce signal integrity, making the dependency between measurement events and optimization targets explicit at setup.
Eliminated QA drift with a phased JSON → SCSS token pipeline using Style Dictionary, establishing an enforceable design-to-code contract for the Angular codebase.
Architected a seamless migration of a legacy DSP to React via a parallel runtime for incremental component replacement, with cross-domain auth and a unified design system.
Designed pacing controls and visualization tools for DSP campaign management, translating complex delivery mechanics into an intuitive configuration experience.
View case study →Designed reporting dashboards and visualization tools for a programmatic advertising platform, making complex performance data actionable for advertisers.
View case study →"Constraints aren't obstacles, they're the design brief."
I work best when engineering realities are part of the problem, not separated from it. The best UX solutions come from understanding what's actually feasible."Data informs the shape of the solution, not just its validation."
SQL analysis, usage patterns, and behavioral data aren't just for post-launch measurement; they belong in the discovery phase, before the first wireframe."Systemic problems need systemic solutions, not one-off fixes."
When I trace a recurring inconsistency to a structural gap, the right answer is a pipeline or governance model, not another round of manual correction.