About / working point of view
Product editor's eye. Frontend architect's discipline.
I work where frontend engineering, product systems, and interface direction overlap—especially when a product spans public web, operational tooling, and mobile experience.
I'm at my best when the product is real, the workflow is complicated, and design decisions need to survive contact with implementation. The work moves fluidly between framing the problem, shaping the interface, and shipping the system.
Hands-on leadership across product direction, interface craft, and frontend delivery.
Lab notes / operating principles
How I keep complex work moving.
Reduce ambiguity early
The highest-leverage interface decision is often clarifying the model before polishing the screen.
Design the whole loop
Public web, operational tooling, API contracts, and mobile behavior are one connected product experience.
Keep proof close
I prefer working code, realistic states, and product evidence over theoretical process theater.
Make systems feel human
A durable system should make the next decision easier for the people using and extending it.
Experience archive / 2016—Now
The work changed. The through-line got sharper.
A decade of building customer journeys, operational systems, design languages, and product platforms—each chapter adding a different kind of depth to the next.
Architecting a multi-tenant SaaS and mobile platform for destination-based experience programs, from campaign configuration to the product in someone’s hand.
System
Campaigns, versioned content, distribution channels, subscription gating, and multi-organization tenancy.
Interface
A shared design system and TypeScript contracts across the builder, public web, API, and mobile surfaces.
Through-line
Product direction, implementation, and monetization treated as one connected design problem.
- Multi-tenant SaaS
- Product systems
- Web + mobile