Evidence over

How I work

I start with the problem, not the feature. That means talking to customers early, writing down what we believe and why, and putting the smallest testable slice in front of the team. In regulated markets that discipline matters twice over: every assumption you can retire with evidence is one you don't ship into a compliance review.

Once direction is set, my job is to remove ambiguity — clear specs, visible trade-offs, and a cadence the team can sustain without heroics. I run my own analysis in SQL and Amplitude rather than waiting on a dashboard, because the fastest way to settle an argument about users is to go and look.