The PM Philosophy

Product is not about features; it is about the integrity of the system. I believe in software that respects the user's focus and the developer's sanity.

How I think

I operate at the intersection of technical constraint and human desire. Every project starts as a note, becomes a prototype, and survives only if it solves a structural friction.

What I value

Clarity over cleverness. Long-term maintainability over short-term spectacle. Teams that trust each other over processes that compensate for distrust.

01

Systemic Simplicity

Complexity is a debt that must be paid daily. I believe in stripping back features until only the core utility remains, then refining that utility until it feels invisible. The best products do not impress users with density; they disappear into the workflow.

02

Evidence-Led Intuition

Data informs the baseline, but taste defines the ceiling. I use qualitative research to validate the 'why' and quantitative metrics to monitor the 'how'. Every strong opinion is held loosely until the evidence says otherwise.

03

Async-First Coordination

The highest-performing teams I have worked with treat meetings as a last resort. I design processes and tools that make asynchronous decision-making safe, fast, and humane.

04

Intentional Friction

Not all friction is bad. The right friction protects focus, encourages reflection, and prevents careless defaults. I am interested in products that respect the user's attention enough to slow them down when it matters.