PRODUCT SYSTEMS DESIGNER
I build systems that get faster as they scale.
I help teams make better decisions by reducing complexity at the source: the way work is framed, decomposed, named, and carried forward.
PRACTICE
I work where product, operations, and decision-making start to blur. The visible output might be an interface, a workflow, a service model, or a design system. The real work is building the conditions that let teams move with less drag the next time the problem appears.
COMPONENT METHODOLOGY
A decision framework for ideas that need to survive scale.
Component Methodology borrows from the discipline of design systems, then applies it to decision-making. Instead of asking whether an idea is good or bad, it asks whether the idea is reusable, composable, and worth carrying forward.
01 / What is the smallest useful part?
02 / Where will this need to repeat?
03 / What does it make easier next?
THE TRIAD
In product teams the main stakeholders—product, engineering, and design—do the same work with different toolboxes. The Triad aims to align those goals to ensure each team member is helping to support the other two sides of the triangle. It is my belief that the line between product, engineer, and designer should be blurred to ensure a cooperative and effective team environment.
WORK
Evidence, not the main event.
PROCESS
Decompose
Break the problem down until the work stops looking like a request and starts looking like a system of decisions. Solutions are not a set of requirements, they are part of a system.
Find the Opportunity
Every solution has an opportunity, and it's on us to find that opportunity. Solve the problem directly, that's an expense. Solve the problem in a way that leads to solving another problem? That's an investment. In every idea we are looking for the opportunity.
Build for the next thing
Solving the problem directly in front of you is expensive. Instead, we always look ahead to see what is unlocked by our approach. The more that we unlock, the more valuable that solution becomes.
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 incentives, handoffs, naming, sequencing, governance, and the quiet decisions that make teams slow.
That is the work I am most interested in now: product systems that make people sharper, not busier. Component Methodology is how I explain that work without turning it into jargon.