Design
I design products that have a lot going on under the surface: complex workflows, rules, states, and data. My job is to make that complexity understandable without hiding what users actually need to know.
I work across interaction design, information architecture, and visual design, but I spend most of my time on how the product behaves across states and scenarios.
Design Highlights
  • Systems before screens: Define rules, states, and interaction models before polishing UI.
  • Clarity under constraint: Make complex workflows easier to use while working within technical, business, and organizational realities.
  • Behavior over decoration: Focus on how products work over time, not just how they look in a single moment.
  • Execution that holds up: Design with engineering, implementation, and scale in mind from the start.
How I Design

I usually start by understanding what the product needs to do, then shape the interaction and visual design around that.

Frame

Understand the system before designing the interface.

  • Clarify users, constraints, and decision points
  • Identify the behaviors the product must support
Structure

Create interaction models and information architecture that make complexity understandable.

  • Define states, flows, and relationships
  • Reduce ambiguity across screens and scenarios
Refine

Shape the experience so it feels clear, predictable, and usable in practice.

  • Make important moments easier to complete
  • Design for edge cases, not just happy paths
Deliver

Work closely with engineering so the design holds up in production.

  • Preserve intent through implementation
  • Build patterns that can scale over time
What My Design Work Includes

My design work often spans:

  • ‍Interaction design for complex workflows, tools, and decision paths
  • ‍Information architecture that helps users understand systems, not fight them
  • ‍Discovery-informed design, grounded in research insights and real constraints
  • ‍Edge-case and error-state design to prevent fragile or misleading experiences
  • ‍Design-to-engineering handoff, ensuring intent survives implementation

I prioritize clarity, predictability, and usability so experiences remain understandable even as products scale.

Designing With Research in Mind

I use research across design, product, and business questions. Depending on what we need to learn, that can mean understanding users, testing an experience, evaluating a product direction, or challenging assumptions before the team invests too far.

Collaboration & Execution

I stay close to product and engineering throughout the work, especially when technical constraints affect the interaction model. That helps us resolve questions earlier and keeps implementation closer to the design intent.

When Design Makes the Biggest Impact

I am most effective when design is used to:

  • Clarify complex workflows or rules
  • Make complex decisions easier to understand and act on
  • Align multiple disciplines around shared models
  • Support products expected to evolve, scale, or integrate over time

That is where design can make the biggest difference.

Colleague feedback
“He does an exceptional job of considering both the end user and the context in which the product is used.”
Caleb Godsey

Senior Product Designer at Transfix
Case Studies
These case studies show how design decisions translate complex systems, workflows, and constraints into clear, usable experiences.
View Case Studies
Let’s Connect
The easiest way to reach me is on LinkedIn. For more detailed inquiries, you can also use the contact form.
Connect on LinkedIn
Contact Me