DESIGN SYSTEMS THINKER
I Shape Systems That Get Faster as They Scale.
Product systems thinking, applied.
From business goals to shipped product, with less waste every time.
PRACTICE
I work where research, interaction, service, and systems thinking start to overlap. The visible output might be an interface, a workflow, a design system, or a shared decision model. The deeper work is giving teams clearer ways to understand, name, and evolve what they are making.
COMPONENT METHODOLOGY
A Design-Thinking Framework for Ideas That Need to Stay Useful over Time.
I created Component Methodology from the discipline of design systems, applying it to strategic thinking. Instead of asking whether an idea is simply good or bad, it asks whether the decision is reusable, legible, and worth carrying into future work.
01 / What is the smallest meaningful pattern?
02 / Where will this decision repeat?
03 / What does it clarify next?
THE TRIAD
Creating a Product Team with Shared Goals
The Triad is a model for balancing human intent, designed behavior, and organizational reality. This is less a framework and more a mindset; helping to ensure alignment and empathy across all disciplines inside a product organization. Instead of dictating what each role is responsible, I reframe the process in understanding the goals of the other two disciplines, and ensuring each person's work supports those initiatives.
WORK
Case Evidence, Not the Whole Argument.
PROCESS
Simplify
Break the problem down to its simplest parts to uncover the real goal.
Find the opportunity
Once simplified, we can view the problem and solution through a different lens. From here we are always looking for an oppotunity.
Build for the next thing
Solving the direct problem you face is expensive. Instead, I strive to always
Nothing is Thrown Away
An idea that may not make objective sense today might enable a new opportunity tomorrow. No ideas are bad, all are retained. Finding an opportunity requires the right idea at the right time.
ABOUT
I came up through UX, but the more complex the work became, the less useful it felt to think only in screens. Interfaces matter. So do research frames, interaction models, naming, sequencing, governance, and the quiet design decisions that shape how teams move.
That is the work I am most interested in now: design systems that make teams sharper, not busier. Component Methodology is how I explain that work without turning it into jargon.