A working philosophy

How I Think About Product

How I Think About Product

How I Think About Product

Impactful products emerge from the collision of customer needs, operational realities, and technological possibilities.

Impactful products emerge from the collision of customer needs, operational realities, and technological possibilities.

Impactful products emerge from the collision of customer needs, operational realities, and technological possibilities.

Notes on building

Customer needs. Operational reality. Technological possibility. The work lives in the space between all three.

Through my career I’ve spent time in operations, customer success, strategy, sales enablement, digital transformation, and product management. This broad experience shapes how I approach product development and helps me see customer needs, operational realities, and business outcomes. Features and well-designed UI don’t define successful products. Successful products are defined by the outcomes they create and support.


Technology is a tool to solve consequential problems. That could be through automation, artificial intelligence, or tried-and-true software development. Sometimes the right solution is a well-crafted Excel spreadsheet with macros. Other times it’s an enterprise platform, mobile application, or AI-powered workflow. The goal remains the same: help people make better decisions, work efficiently, and achieve better outcomes.


Product leaders shape outcomes, but our leadership starts well before requirements are documented. Product leaders create a shared understanding around a problem worth solving, who it impacts, and why the outcome matters.


Innovation is not an event. It’s not the adoption of a new tool. It is the discipline of continuously learning. Built on a deep understanding of customers, innovation encourages us to challenge assumptions, uncover new opportunities, and refine our approach based on what we learn.


Great products are more than their beautiful screens. The best products improve systems. They create better ways for people, teams, and organizations to achieve their goals.


At the end of the day, customers don’t buy roadmaps. They buy outcomes.

Through my career I’ve spent time in operations, customer success, strategy, sales enablement, digital transformation, and product management. This broad experience shapes how I approach product development and helps me see customer needs, operational realities, and business outcomes. Features and well-designed UI don’t define successful products. Successful products are defined by the outcomes they create and support.


Technology is a tool to solve consequential problems. That could be through automation, artificial intelligence, or tried-and-true software development. Sometimes the right solution is a well-crafted Excel spreadsheet with macros. Other times it’s an enterprise platform, mobile application, or AI-powered workflow. The goal remains the same: help people make better decisions, work efficiently, and achieve better outcomes.


Product leaders shape outcomes, but our leadership starts well before requirements are documented. Product leaders create a shared understanding around a problem worth solving, who it impacts, and why the outcome matters.


Innovation is not an event. It’s not the adoption of a new tool. It is the discipline of continuously learning. Built on a deep understanding of customers, innovation encourages us to challenge assumptions, uncover new opportunities, and refine our approach based on what we learn.


Great products are more than their beautiful screens. The best products improve systems. They create better ways for people, teams, and organizations to achieve their goals.


At the end of the day, customers don’t buy roadmaps. They buy outcomes.

Through my career I’ve spent time in operations, customer success, strategy, sales enablement, digital transformation, and product management. This broad experience shapes how I approach product development and helps me see customer needs, operational realities, and business outcomes. Features and well-designed UI don’t define successful products. Successful products are defined by the outcomes they create and support.


Technology is a tool to solve consequential problems. That could be through automation, artificial intelligence, or tried-and-true software development. Sometimes the right solution is a well-crafted Excel spreadsheet with macros. Other times it’s an enterprise platform, mobile application, or AI-powered workflow. The goal remains the same: help people make better decisions, work efficiently, and achieve better outcomes.


Product leaders shape outcomes, but our leadership starts well before requirements are documented. Product leaders create a shared understanding around a problem worth solving, who it impacts, and why the outcome matters.


Innovation is not an event. It’s not the adoption of a new tool. It is the discipline of continuously learning. Built on a deep understanding of customers, innovation encourages us to challenge assumptions, uncover new opportunities, and refine our approach based on what we learn.


Great products are more than their beautiful screens. The best products improve systems. They create better ways for people, teams, and organizations to achieve their goals.


At the end of the day, customers don’t buy roadmaps. They buy outcomes.