About

I work at the intersection of product strategy, engineering, and organizational decision-making. Over the past years, my work has consistently revolved around one central question:

How do teams make good decisions under complexity, uncertainty, and technical constraints?

My background spans product leadership, agency work, company building, and responsibility in complex product organizations. Across these contexts, I have repeatedly seen the same pattern:

• Implementation speed is rarely the real problem
• What limits outcomes is how problems are defined
• Which assumptions are made explicit
• And where responsibility is placed

This perspective has shaped how I approach product work today.

I focus on product practice as a decision system, not as a delivery pipeline. Product discovery, architecture, and engineering are not separate phases to be optimized in isolation. They are tightly coupled mechanisms that determine whether teams build the right things with the right level of confidence.

More recently, this has led me to work deeply on agentic and AI-assisted development practices. Not as a tooling topic.
But as a shift in how responsibility, guardrails, and collaboration need to be designed when code itself is no longer the primary bottleneck.

Faster implementation does not reduce the need for clarity. It increases it.