Products first, screens second
I start from the business goal and the user's problem, then design backwards — so every screen exists for a reason.
7+ years in the game — designing products, then owning them. Still obsessed with turning messy problems into simple flows.
I love building products end to end, but even more, I love when the right thing ships
I start from the business goal and the user's problem, then design backwards — so every screen exists for a reason.
I turn ideas into clear specs, acceptance criteria, and scoped tickets developers can build from without guessing.
I take flows from first sketch to dev-ready UI — and stay hands-on with the details until it ships.
I run UAT against the requirements I wrote, so what reaches users matches what we promised.
Design and product ownership, in practice
Where product ownership meets design