About Me
I've spent my career at the intersection of design, user experience, and engineering. What began as product design and UI work evolved into a deep focus on front-end architecture, design systems, and the challenge of delivering consistent experiences at scale.
My Path to Front-end Leadership
Most organizations don't struggle because of a lack of talent. They struggle because their front-end systems evolve without structure. Different teams build different patterns, components drift, and over time the user experience becomes inconsistent and harder to maintain. That's where I focus.
Over the years, I've found that my impact grows when I shift from building individual features to building systems that enable teams. This means creating component libraries that make good design cheap and accessible. It means establishing patterns that prevent technical debt from accumulating. It means helping teams understand not just what to build, but how and why.
What Drives Me
I believe that great user experiences are built on solid foundations. That foundation is the design system, the component architecture, the accessibility standards, the observability tooling, and the shared practices that teams rely on.
I'm motivated by problems that span products and teams. How do we make it easy for any engineer to build an accessible form? How do we ensure brand consistency across six applications without creating bottlenecks? How do we modernize legacy code while still shipping features?
These are the problems I work on. They require technical depth, cross-functional collaboration, and the ability to balance pragmatism with long-term thinking.
How I Work
I don't think in terms of features - I think in terms of systems. Features solve immediate problems. Systems prevent those problems from recurring. The goal is not just to ship faster today, but to make future work easier, more predictable, and more consistent.
I lead by influence as much as authority. Whether it's running a front-end community of practice, working through a complex architecture decision, or pairing with an engineer on a component implementation, my goal is to help teams succeed.
I believe in:
- Building consensus through collaboration, not mandates
- Creating shared ownership of quality and standards
- Making the right thing the easy thing
- Investing in enablement and documentation
- Balancing velocity with sustainability
Current Focus
Right now, I'm building the customer experience function at Milliman IntelliScript. This means leading a team of 10, driving design system adoption, modernizing front-end architecture, and establishing the patterns and practices that will scale as the organization grows.
I'm also deep in the AI space — running workshops for my CX team and engineering peers on the AI landscape, practical tooling strategies, and how to minimize cost while maximizing impact. I build agentic projects on the side to stay hands-on and bring real examples into those conversations.
Expertise
Architecture & Systems
- Design systems & component libraries
- Front-end architecture & modernization
- Micro-frontends & scalable application patterns
- Build tooling & developer experience
- Technical strategy & roadmapping
Modern Front-end
- React & React ecosystem
- TypeScript & JavaScript
- Next.js application architecture
- Modern CSS & styling approaches
- State management & data fetching
- Testing strategies & quality assurance
Design & UX
- User-centered design thinking
- Accessibility (WCAG, ARIA)
- Design systems governance
- Design tokens & theming
- Component API design
- Cross-functional UX collaboration
Leadership & Enablement
- Engineering team leadership
- Cross-team collaboration & influence
- Communities of practice
- Technical mentorship
- Standards & best practices definition
- Engineering enablement & documentation
- AI tooling advocacy & workshops
- Public speaking & technical presentations