WHAT I BUILD

Products

I turn customer and business problems into products people can understand, use, and value.

My product experience includes SaaS, ecommerce, order management, enterprise software, APIs, integrations, digital commerce, specialty products and new product development.

My approach combines:

Discovery → Strategy → Design → Prioritization → Development → Launch → Learning

The goal isn't simply to ship.

The goal is to create something worth shipping.

Product Organizations

Good products require good product organizations.

I've built and refined product-management processes, established ways of working between product, UX, and engineering, and led teams through the transition from individual product decisions to a more disciplined product practice.

That includes:

• Product strategy and vision

• Roadmap development

• Product discovery

• Backlog and requirements management

• Prioritization frameworks

• Agile product development

• UX/product collaboration

• Stakeholder alignment

• Product-team structure and processes

• Customer feedback loops

I believe process should create clarity and momentum, not bureaucracy.

Businesses

Some of my most valuable product experiences happened when there wasn't a product organization to begin with.

I've helped create new businesses, launch new markets, develop commercial strategies, and turn technical capabilities into revenue-producing offerings.

That experience gives me a broader perspective on product:

A product exists to create value for both the customer and the organization building it.

Technology

I'm not a software engineer by trade, but I've spent much of my career working closely with engineers and technical teams.

I understand the architecture-level concepts and tradeoffs necessary to make good product decisions, including:

• SaaS platforms

• APIs

• System integrations

• Ecommerce technology

• Order management

• Data

• Enterprise software

• UX/UI

• Software development lifecycles

My job isn't to tell engineers how to write the code -- it's to make sure we're building the right thing for the right reason.

Customers

I've spent my career talking to customers.

Enterprise customers. Business users. Consumers. Sales teams. Operations teams. Technical users.

I've learned that customers rarely describe the solution you should build.

They describe the problem they're experiencing.

The product leader's job is to understand the difference.

Transformation

Some organizations need a new product.

Others need a new way of working.

Others need someone to look at a complicated situation and figure out where to start.

I've worked in all three environments.

Whether the challenge is a new product, a struggling operation, an immature product organization, or a business trying to enter a new market, I tend to approach it the same way:

Listen. Understand. Decide. Build. Measure. Learn.