I’ve spent my career tracing how decisions become systems, and how those systems shape the people working within them.

I began close to the implementation layer, designing and building front-end experiences. That work showed me how quickly good intent can get lost between a design file and production. It also exposed the cost of having every team solve the same problem differently.

As I moved through product design, Scrum facilitation, design leadership, product ownership, and design-system management, my focus widened. The interface still mattered, but so did the roadmap, contribution model, architecture, documentation, governance, release process, support system, and organizational trust around it.

That is the work I now describe as pattern architecture: seeing recurring conditions across product, design, engineering, operations, and organizations; translating them into understandable structures; and creating practical blueprints people can use.

My deepest professional body of work is the long-term stewardship and modernization of Paylocity’s Citrus Design System. I helped guide it through multiple generations—from a small shared effort into a more mature platform, and later through a generational change in architecture, foundations, and rollout.

I’m now applying those lessons to AI-enabled workflows and organizational operating systems. My focus is the layer between model capability and human work: the knowledge, guardrails, feedback, and decision rights that make a new capability useful and durable.