I build products.

I started in design, but over the last twenty years, that boundary naturally blurred. Today, I don’t treat product strategy, systems architecture, and interface design as separate jobs. They are just different stages of the same continuous loop.

A well-crafted interface is only as good as the system supporting it. If a design doesn’t account for an engineering bottleneck or map directly to a business outcome, it doesn’t add value. My focus is using design as a practical tool to clarify strategy, eliminate development friction, and accelerate shipping velocity.

My experience is split across complex enterprise environments, early startups, and consumer apps. That means balancing the massive, highly constrained logic of an internal enterprise configuration platform one week, and obsessing over the seamless micro-interactions of a consumer application the next. Both require the same fundamental skill: reducing complexity.

Here are three things I learned:

1. Systems over features. Isolated components don’t scale. I focus on building scalable frameworks where every design decision maps cleanly back to the broader technical architecture.

2. Prototyping as alignment. High-level strategy meetings only go so far. I prefer moving rapidly from abstract product problems into high-fidelity, interactive concepts. It’s the fastest, most effective way to align a team and stop guessing.

3. Product is risk management. Exceptional execution requires knowing when to obsess over absolute perfection and when to ruthlessly manage scope to get a live product into the hands of real users.

Right now, I’m focused on digital strategy, enterprise product architecture, and building systems that last.