Product / Experimentation / Systems
Product observations, written down.
This is where I share my thinking and perspective on product leadership, strategy, operations, and go-to-market, with a clear focus on experimentation and measurement. Everything here is drawn from building products and the operating systems behind them. I explore the principles, tradeoffs, and organizational mechanisms that help teams move more efficiently while making better-informed decisions.
Read the writing →
Latest writing
View all articles →- Opinion Your Customers Don't Need Another Platform. They Need Your Capabilities. Why composable capabilities and customer-centered delivery could redefine the future of product-led services. Article ·
- Systems Thinking & Orchestration The Whole Is Greater Than the Sum of the Systems A capability that works well on its own can still fail once it depends on another team, system, or process. Improving one component rarely improves the outcome if the relationships around it stay the same. Article ·
- Systems Thinking & Orchestration The Systems Behind the Experience What the customer sees is a list of products. What delivers it is identity, behavioral data, catalogs, models, and real-time decisioning. Discovery has to tell what looks simple from what actually is. Article ·
- Systems Thinking & Orchestration Understanding Where Value Comes From A reporting problem often starts in how the information was collected, and a launch delay often has more to do with handoffs than technology. Following the value chain, rather than the org chart, is what makes the difference visible. Article ·
Ideas & exploration
All ideas →Articles are expressions of ideas. These are the ideas they keep returning to.
- The Cost of AI The force reshaping organizations is not only what AI can do - it is what AI costs: a distributed, largely ungoverned expense that stays invisible until finance connects the dots.
- Structured Discovery Understanding a problem and understanding the environment that produced it are two different things. A user's friction often originates in a system, a dependency, or a decision made elsewhere, so discovery that stops at the user need routinely locates the problem in the wrong place.
- Experimentation That Compounds Experimentation only becomes an advantage when platform, program, and culture work together to turn individual test results into institutional knowledge - organizations that merely run tests do not compound.
About
More about me →
The experience behind the perspective.
I build the systems a product organization runs on: how it decides what to build, scales execution, and learns whether it worked. There is also a bowl of spaghetti involved, which takes some explaining.
Learn more →