About

Designing clarity for complex systems

With over a decade of experience across fintech, legal tech, performance marketing, and sales enablement, the core of my work involves making complex systems understandable. This applies both to users navigating dense, high-stakes workflows and to cross-functional teams making difficult product decisions.

My career has spanned hands-on design at Clio, Thinkific, and organizational leadership at Highspot, Later, and Lendesk. I'm extremely grateful for all these experiences and have learned that the most impactful design work happens at the intersection of product strategy and system architecture.

Staff-level focus

Today, my focus is on staff-level individual contribution:

Having spent several years in front-end development early on, I design with a deep understanding of technical constraints, system behavior, and the realities of shipping reliably at scale.

Technical fluency

Because I spent the early years of my career designing and writing front-end code, I bring a deep understanding of the underlying mechanics of modern software. This technical foundation allows me to partner effectively with engineering leadership to ensure that design vision is balanced with technical sustainability.

My technical lens includes:

• System Behavior and Constraints: Designing with an inherent understanding of state management, API limitations, and data structures to avoid "unbuildable" designs
• Performance as UX: Recognizing that latency and loading states are core interaction challenges, especially in data-heavy B2B environments
• Scalable Implementation: Working within modern front-end frameworks to ensure that components are modular, reusable, and accessible from the code level up
• Platform Logic: Partnering with engineers to define how data moves through the system, ensuring that the interface accurately represents the underlying logic

I believe that the best design decisions are made when I speak the same language as my engineering partners, allowing us to navigate complex technical tradeoffs without sacrificing the user experience.

Operational values

Collaborative leadership

Staff-level leadership is about leaving the system and the team better than I found them.

I operate by these values:

Design principles

These principles guide my decisions across projects and organizations:

• Validate Reality: Intuition starts the conversation, but user evidence must finish it
• Reduce Cognitive Load: The best systems allow users to focus on their work, not the interface
• Design for Evolution: Sustainable, incremental change consistently outperforms grand redesigns
• Make Structure Visible: Clear hierarchy and predictable patterns are the primary drivers of user trust
• Unify for Understanding: Consistency should serve user clarity, not just aesthetic sameness