I came to design from the technical side of software.

Early in my career—working in support, training, and QA—I saw the same pattern repeatedly: products met technical requirements but failed real people. Engineers built what was specified. Customers struggled to use it. The gap wasn't effort or intelligence. It was the absence of clear experience architecture.

That gap is where I've worked ever since.

Over the past 25+ years, I've operated at the intersection of product strategy, engineering systems, and human behavior—designing enterprise software that must be coherent, governable, and scalable. My focus is not surface aesthetics. It's structure: defining mental models, interaction patterns, and system logic that make complex platforms understandable and usable.

I think about software the way architects think about buildings. Engineering ensures structural integrity. Design defines purpose, flow, and human experience. Both are essential—but without deliberate experience architecture, systems drift toward entropy.

Design is not decoration. It is structured decision-making about how systems behave for the people who depend on them.

Great design:

• Clarifies intent before features are built
• Establishes durable interaction models
• Makes complexity navigable
• Balances innovation with reliability
• Holds up under real-world scale

Poor design is rarely malicious—it's usually the result of building first and rationalizing later.

In enterprise environments especially, design must lead early. Information architecture, workflow modeling, prototyping, and validation are far less expensive—and far more effective—before code hardens assumptions.

My approach blends systems thinking, research rigor, and pragmatic execution.

I operate comfortably inside complex, configuration-driven platforms. I design for state, versioning, permissions, governance, and data-rich environments. Increasingly, that includes AI-enabled workflows—where natural language interfaces, validation frameworks, and human oversight must coexist.

I rely heavily on executable prototypes, structured UX measurement, and collaborative iteration. I believe in Lean principles—test assumptions quickly, refine deliberately, and maintain tight feedback loops with engineering and product.

I also believe designers should understand the systems they shape. Fluency in development processes, architectural constraints, and implementation trade-offs is essential to meaningful collaboration.

When software becomes foundational to a business—or to someone's daily life—clarity is not optional.

At scale, experience architecture affects:

• Product adoption
• Operational efficiency
• Trust
• Brand confidence
• Long-term maintainability

The best design work is often invisible. It feels obvious. It reduces friction without drawing attention to itself. It aligns user needs, technical realities, and business goals into a coherent system.

That's the work I'm most interested in.